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

19 rules. About 0 are common, 17 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈17

  Distinctive · estimate

  This author's own choices. Worth a look.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   When you read this file, you must always refer to files under skills/ when performing tasks.

   line 3
2. Very specific:

   Never skip referencing them even if not explicitly instructed.

   line 4
3. Distinctive:

   Always refer to this skill when understanding the basic policy and philosophy of acting as an AI agent.

   line 10
4. Distinctive:

   Always refer to this skill when generating Nix code, editing flakes, or operating home-manager.

   line 14
5. Distinctive:

   Always refer to this skill when committing or pushing Git file changes.

   line 18
6. Distinctive:

   Always refer to this skill when generating or modifying TypeScript/JavaScript project code.

   line 22
7. Distinctive:

   Always refer to this skill when performing file operations in an Arch Linux environment.

   line 26
8. Distinctive:

   Always refer to this skill when conducting a Pull Request code review.

   line 30
9. Distinctive:

   Always refer to this skill when creating a Pull Request with gh cli.

   line 34
10. Distinctive:

    Always refer to this skill when searching the web for latest information or error solutions.

    line 38
11. Distinctive:

    Always refer to this skill when creating or updating skills under the skills/ directory.

    line 42
12. Distinctive:

    Always refer to this skill when editing Neovim config, adding plugins, or optimizing startup time.

    line 46
13. Distinctive:

    Always refer to this skill when creating, editing, or debugging GitHub Actions workflow YAML files.

    line 50
14. Distinctive:

    Always refer to this skill when generating or writing code in any language.

    line 54
15. Distinctive:

    Always refer to this skill when writing fish shell scripts, functions, abbreviations, or editing shell configuration.

    line 58
16. Very specific:

    Always refer to this skill when creating Node.js/TypeScript CLI tools.

    line 62
17. Distinctive:

    Always refer to this skill when creating flake.nix for project-level development environments or shared devShells.

    line 66
18. Distinctive:

    Always refer to this skill at the START of every conversation to retrieve relevant memories, and when saving reusable patterns, user …

    line 70
19. Distinctive:

    Always refer to this skill when merging main branch into current branch.

    line 74

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