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

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈3

  Distinctive · estimate

  This author's own choices. Worth a look.

• 3

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Read AGENTS.md for the project contract and workflow.

   line 3
2. Very specific:

   Use canonical content from skills/ when Skills are introduced.

   line 5
3. Very specific:

   Treat arks as an external executable boundary, not an importable Skill runtime.

   line 6
4. Distinctive:

   Ask before installing CLI tools, packages, or changing user-level configuration.

   line 7
5. Distinctive:

   Do not create Claude-specific copies of Skill bodies.

   line 8
6. Very specific:

   Follow the plugin release boundary in docs/maintenance.md.

   line 10

≈ “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.