We split this CLAUDE.md into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  Distinctive · estimate

  This author's own choices. Worth a look.

• 5

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Before product, architecture, documentation, or workflow changes, read:

   line 5
2. Very specific:

   Keep root files as package/bootstrap/rules entrypoints.

   line 24
3. Very specific:

   Keep all installable or resident analyst skills under skills/.

   line 25
4. Very specific:

   Keep host-specific instructions under adapters/.

   line 26
5. Very specific:

   Keep generated workspace files under templates/workspace/.

   line 27
6. Very specific:

   Keep model repository templates under templates/model-repo/.

   line 28
7. Distinctive:

   Do not store secrets, raw private messages, raw transcript payloads, OAuth tokens, bearer headers, or personal contact data.

   line 29
8. Distinctive:

   Before finalizing, run the relevant unittest files and review git diff.

   line 33
9. Distinctive:

   Use dense, concrete writing.

   line 37

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.