Here is what I do myself.
My entire company lives in one folder. The website, the course material, the accounts and the podcast transcripts. At the root sits an instruction file with the house rules: the tone, the design rules and the things that must never happen. All my agents read it when they start.
Yesterday I reconciled two months of accounts with an agent. It fetched nine invoices, corrected two amounts to what the bank actually charged, and booked the lot. It already knew how my accounts fit together, because another agent wrote it down in a file six weeks ago. That is how my agents share knowledge: through files in the same folder.
It is absurdly efficient. Reach out if you’d like me to show you, or sign up for my webinar (in Danish) on 21 October.
Size makes a big difference
The more of you there are, the harder it gets.
A few people
One shared folder is enough. A git repo or a shared folder in Drive, Dropbox or OneDrive. One instruction file at the root, AGENTS.md or CLAUDE.md. A new colleague onboards by opening the folder, and then their agent knows what yours knows. If you’d rather avoid a terminal, open the folder in the Claude app on your computer, either in the Code tab or in Cowork. If the folder lives in Drive, Dropbox or OneDrive, everyone works in the same files. If you use Codex or Gemini, have a look at Palette, which does the same thing in a shared Drive folder.
A couple of product teams
One folder per team and a shared core that every team reads: house rules, design rules, glossary. Skills, meaning recipes the agent picks up when the task fits, go in a shared library. At this point someone has to own the files, so the rules only exist in one version.
A large organization
Here knowledge lives in Confluence, Jira, SharePoint and Figma, and IT controls who can see what. So the agents have to be connected to the systems you already have, typically via MCP, and they have to inherit the access the user has. That takes longer. My suggestion is to start in one team and let the rest follow. But get started!
What you can share
Whatever your size, I think the most important things to share are your decisions, meaning what you chose and what you said no to, your way of working and your design system. In each phase I would write this down:
If you want to try it: create a file called decisions.md wherever your team already works. Write three lines per decision: date, what you chose, what you said no to. Ask your agent to read it before it suggests anything.
I’d like to hear how you do it. Especially if there are many of you. And if you’re about to get started yourselves, write to me. I’m happy to help.
