One set of files the whole team uses
Each person starts their own instructions and scorecards. The ones that work belong in one team library, so anyone can run a job to the same standard and nothing is lost when someone leaves. Point to it from each case instead of copying it.
A few weeks into a programme, each person has started their own instructions and scorecards. Now the ones that work go in one place, so anyone can run a job to the same standard, and nothing is lost when someone leaves.
One team library
Put a folder called team-library on the shared drive you already use (Google Drive or SharePoint) and sync it to everyone's computer. It holds how you do the work. Client documents stay in the case folders, and the library never holds them.
One team library, pointed to from every case
team-library/README.md who looks after whatVOICE.md how you writedesign-system/jobs/report-review/INSTRUCTIONS.mdSCORECARD.mdLOG.md what changed, whyexamples/
The case folders point to the library. The library never holds client documents.
There's one folder under jobs/ for each job you repeat, such as report review, translation or interview reports. Each holds the standing brief, the scorecard and a log of what changed and why, plus a good past report as text, redacted.
Each job has one owner who looks after its files. Anyone can use them.
Point to it, don't copy it
When you copy the files into each case, you end up with ten versions and nobody knows which is right.
Copy it, or point to it
Copy into every case
A fix made in one case never reaches the others.
Point to the library
Fix it once and every case gets the fix.
There are two ways to point.
Add it to your workspace
Open the case folder in VS Code, drag team-library into the side panel and choose Add Folder to Workspace. Save the workspace when you close. The workspaces guide has a screenshot for every step.
One line in CLAUDE.md
In the case folder's CLAUDE.md, write @ and the full path to the library file. Claude reads it every time, as if it were in the folder. Get the path with right-click, Copy Path, because it's different on each computer.
This case is a report review.
Follow @/Users/<you>/Google Drive/team-library/jobs/report-review/INSTRUCTIONS.md
Check every draft against @/Users/<you>/Google Drive/team-library/jobs/report-review/SCORECARD.md
Write the way @/Users/<you>/Google Drive/team-library/VOICE.md describes.
The first time, Claude asks whether it may read files from outside the folder. Say yes.
Don't use a Mac alias or a Windows shortcut. Claude sees it as a small file of its own and can't see inside the folder it points to. That's the most likely reason it didn't work when you tried.
Keep it up to date
The files only get better if your corrections go back into them. When you make the last small changes by hand in a final report, they need to go into the instructions so the next report has them too.
- The owner makes the changes. Anyone else adds a note to LOG.md or tells the owner.
- Watch for conflict copies. Two people editing the same file at once on a shared drive makes a second copy. Give both to Claude and ask it to merge them.
- Tidy every couple of months. Ask Claude to make the files shorter and easier to read.
My final version is <paste the path>. Compare it with your draft and list what I changed. Then update INSTRUCTIONS.md in the team library so the next draft has these changes without me making them. Add a line to LOG.md with today's date, what changed and why.
Before someone leaves
When a colleague who built instructions and prompts that work is moving on, their files go into the library before they leave, so the team keeps them.
List every instructions file, prompt, scorecard and example I've made in this folder. For the ones another person could use, copy them into team-library/jobs/<job name>/ and write a short README.md: what the job is, how to start it and what to watch out for. Leave out anything with client names or personal details.
When several people start editing the library at once, the next step is a GitHub repository, which keeps every version and who changed what.