Stop repeating the same rules to every AI tool

The problem

You explain the same writing rules every time someone changes AI tools. One teammate pastes an old copy into Claude Code. Another asks which version to use in Cursor. Before the work starts, you are already answering questions about the rules. Later, you still have to spot which instructions the draft missed.

Separate copies make a small change hard to follow. You fix the date format in one prompt, but another tool keeps using the old format. Your reviewer has to check the request, find the latest rules, and explain the correction again. The team needs a shared place to agree on those rules.

How onemind helps

A Mind holds your team's shared rules for AI tools. A Project is a folder of work, like one client or one product. You approve a rule, then onemind sends it to connected tools in the Project's chosen folder. Safe Check, an automatic check, looks at proposed rules before you decide.

An example

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

Your small product team needs a help page for an export feature. You want invented records in every example. Dates must use YYYY-MM-DD. The page must explain that requesting an export does not mean the download has finished. These rules should also apply to later help pages.
You write the rules in the product's Mind. A teammate reads them and checks what each sentence means. Safe Check runs before you approve the wording. You clear up anything confusing first, including when the page can say a file is ready. The approved version becomes the rule for future work.
You connect Codex, Claude Code, and Cursor to the product's local folder. You turn on sync for the tools you need. Each tool keeps its own way of reading instructions. onemind sends the same approved rules through those instructions, so you do not edit three separate copies.
After each tool shows Delivered for the new version, you open a new chat with Cursor in that folder. You ask for an export help page with an example and the steps after a request. You describe the current task without pasting the standing rules again.
You read the draft before using it. Check the invented records, the date, and the difference between requesting an export and finishing a download. If a rule is missing, correct the draft. Then check which rules reached Cursor, rather than assuming that a successful sync guarantees a correct answer.
A teammate later opens a new chat with Claude Code in the same folder. They ask it to update the export questions and answers. The approved rules should guide that task too. They still read the result and check the same details before the changes go into use.

How to know it worked

The rule shows as approved in onemind.
Each tool shows the new version as Delivered for the right Project.
In a new chat, the draft follows the example, date, and download rules.
You read the result before you use it.

What onemind doesn't do yet

Sync needs the right tools, settings, and an available device. The browser can request sync; the local app writes the files. Open chats may keep older rules.
A Mind does not move a tool's full chat history. Different tools can still answer differently. Project rules stay in that folder.
Automatic learning from finished tasks is coming. Keep private details out of shared rules and review every result yourself.

Common questions

Do all tools read one file?

Each tool reads the shared rules through its own instructions. You keep one approved set of rules in onemind.

Does Delivered mean the tool followed the rule?

It means the new version reached that tool. Open a new chat and check the result too.

Do I still need to explain each task?

Yes. Tell the tool what you want, give it the needed material, and explain what a good result looks like.

Learn more

Start with Minds and review and Mind Sync. Choose one rule, then check whether a new chat follows it.