In plain English
- A shared rulebook: one document or folder that holds how your team works (formats, brand guidelines, house rules), which every person's AI reads before it starts.
- A project or a skill: a place for your team's instructions and files that you can share. Claude and ChatGPT call it a project; Gemini calls it a skill, or a Gem on Workspace business accounts until March 2027.
- Claude Cowork: the part of the Claude app that works through longer, multi-step tasks for you.
- Claude Code: Claude's tool for working directly with files and code.
- A README: a short file that tells whoever opens a folder, person or AI, what it's for and how to use it.
You open the team folder on Monday morning and find the same piece of work twice. Two people answered the same request without knowing the other had: one saved a Markdown file, the other a Word document full of links to the wiki. A third person's AI has summed up the week in a Teams chat, in another format again. Each of you pasted the team's standards into your own AI, and only one of you has the latest copy. How do you get everyone's AI working to the same standard, without pasting the same rules into each person's chat?
I've seen this happen in the past with teams who weren't in communication with each other. They were doubling up on requests without planning and communicating properly, and driving up costs for a different unit. That's basic communication 101, and it applies to AI too. Unless you all agree what good looks like, everyone's going to make different decisions, and then there's no point asking one AI to analyse and summarise work that comes in three different formats.
So plan first. Agree your ways of working, your brand guidelines and the format everyone saves their work in, then have the AI there ready to accept the plan and help you with it. AI just helps enhance what should be there already.
Once you've agreed, write it all into one shared document and put it where every AI on the team reads it first. On Claude's business plans (Team and Enterprise), that's a shared Claude Project, and projects in Claude Cowork, the part of the Claude app for longer tasks, can be shared the same way on those plans. ChatGPT lets you share a project on any plan, including Free. In Gemini, the shared version is a skill: reusable instructions, with their files, that you can use in any Gemini chat. On personal Google accounts, Gems turn into skills from 17 November, and Google moves your Gems across for you, along with who you'd shared them with. Workspace business accounts keep Gems until March 2027. Everyone then starts their chats in that project, or uses that skill or Gem, so the rulebook is there in every chat.
In Claude: open the project, click Share to the right of the project name, and add people by name or email.
In ChatGPT: open the project, click Share, invite people by email, and choose Chat or Edit access.
In Gemini: on gemini.google.com, click Customize, then Skills, hover over the skill, click More, then Share skill, enter email addresses and choose Viewer or Editor. On a Workspace business account, share the Gem instead: open the sidebar, click Gems, then Share next to the Gem.
Check it works: ask a teammate to start a new chat in the shared project, or with the skill or Gem, and send this question. The answer should come from your rulebook.
What format does the team save its work in?
On personal accounts the old Gems stay visible but read only until Google removes them on 17 December.
If your team works in Claude Code, Claude's tool for working with files and code, the same idea works with a shared folder instead of a shared document. Everyone's Claude Code reads and writes to it, and the standards live there, so nobody keeps their own copy. One person asks their Claude to write a README and a CLAUDE.md file, the instructions Claude Code reads when it opens a folder, saying what the folder is for and how to work in it. If that Claude is connected to the team's chat, it can post a message telling everyone what to set up, so nobody has to double up the onboarding for everybody else.
Everyone keeps working in their own setup, and the standards sit at the top of the shared folder as separate files: this is how we write Excel files, this is how we check a report before it goes out. When you've finished something, you ask your own AI to check it against those standards and leave its analysis in the shared folder. One central location for everything to live.
Whichever way you share it, the rulebook needs house rules. Two of the house rules in the builder below are ones I'd add: the AI makes notes where things are unclear, and if it can't understand something, it could tag a teammate, so that things go out verified, because humans will make mistakes. You wouldn't want to send garbage up to something to be analysed and summarised if it wasn't correct to begin with. Untick any rule that doesn't fit your team, add your own, and pick the format everyone saves their work in:
InteractiveHouse rules builder
Signal Over Noise · House rules for our AI
Your rulebook
Put it where every AI on the team reads it: a shared Claude Project (Team and Enterprise plans), a shared ChatGPT project or a shared Gemini skill (a Gem on Workspace business accounts until March 2027). Add your ways of working and brand guidelines to the same document.
Members can get a starter rulebook from the Members Library: a README for a shared folder, plus where to share the rulebook in Claude, ChatGPT and Gemini.
With one rulebook in place, an AI can also read the whole team's work at the end of the week. Each person keeps a daily log of what was on their list, what got done, what's blocking them and what's been added to the pile. From those logs it can see how long the work took and how long the blockers have been standing, which would help the Monday stand-up go a lot faster.
So agree your rulebook as a team first, and put it where every AI on the team reads it, so everyone's work comes back in the format you agreed.