Keep each Project’s AI rules separate

The problem

You open an internal report and find wording meant for a client's booking product. Both products use AI tools, but their terms and screens differ. A useful rule was copied into someone's general tool settings. Now you have to find where it came from and check the rest of the work.

Switching folders should not mean rebuilding every instruction from memory. Yet your team keeps removing client names, changing screen references, and explaining exceptions. Shared rules also get lost along the way. You need a clear home for product rules and a separate place for rules that everyone follows.

How onemind helps

A Project is a folder of work, like one client or one product. A Mind holds your team's shared rules for AI tools. onemind combines approved team rules with the rules for your chosen Project and sends them to its folder. Safe Check, an automatic check, looks at proposed changes before you approve them.

An example

This is a made-up example to show how it works, not a real customer.

1. Your team maintains a client's booking product and an internal reporting product. Each has a separate local folder and Project. You need to add a message when someone leaves the booking date empty. The reporting product has different terms and uses different screen parts.

2. Your team Mind says to keep keyboard access, reuse existing screen parts, and review text that people will read. The booking Mind adds three rules. Use the word “booking,” use the existing field-error display, and keep anything the person entered when a form reports an error.

3. You check where those rules belong before approving them. Keyboard access matters to both products, so that stays with the team rules. Booking terms stay with the booking Project. You settle unclear or conflicting wording during review. Then you check that each Project points to its own folder and that the tools show Delivered.

4. You open a new chat with Claude Code in the booking folder. You ask for the missing-date message, the existing error display, and a keyboard check. You review the change yourself. The form should keep entered text, say “booking,” and make the error clear when someone uses only the keyboard.

5. The review reveals one missing detail. The form must also keep a selected date range, not just typed text. You propose that change to the booking Mind. Safe Check runs, a person reviews it, and you approve the wording. After it reaches the tools, you check it in a new chat.

6. Your next task uses Codex in the reporting folder. It should follow the team keyboard and reuse rules, plus the reporting product's own rules. Check its terms and screen parts. Updating the booking Project should leave the reporting Project's folder and rules as they were.

How to know it worked

• Each Project shows its own correct folder in onemind.
• The rules show as approved, and each needed tool shows Delivered for the right version.
• In a new chat, the tool preserves booking form entries and uses booking terms.
• A new chat in the reporting folder uses reporting terms, and you review both results.

What onemind doesn't do yet

• Choosing a folder does not send the rules by itself. A chat already open may keep older rules; check a new chat.
• Project rules stay in that Project's folder, outside general personal tool settings. Someone can still paste the wrong rules by hand.
• Automatic learning from finished tasks is coming. You still choose where a rule belongs and review the work yourself.

Read next

Read Stop repeating the same rules to every AI tool, Fix an AI mistake once, for every tool, and Hand off AI tasks without losing the details. For setup, see Projects and folders, Minds and review, and Mind Sync.

Learn more

Use Projects and folders, Minds and review, and Mind Sync to set up one Project. Check its next task before adding more.