We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈14

  Distinctive · estimate

  This author's own choices. Worth a look.

• 0

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Keep complexity and code to a minimum.

   line 11
2. Distinctive:

   Only invest in additional abstraction, flexibility, or optimization when it provides a concrete benefit.

   line 16
3. Distinctive:

   If you can simplify existing logic or remove code without affecting the desired behavior or outcome, do it.

   line 20
4. Distinctive:

   Follow the repository's conventions by default, but do not follow them blindly.

   line 23
5. Distinctive:

   If another approach improves simplicity, clarity, or maintainability, take that approach.

   line 24
6. Distinctive:

   Leave the area you touch cleaner than you found it.

   line 27
7. Distinctive:

   Write code clearly enough that comments are usually unnecessary.

   line 32
8. Distinctive:

   Prefer self-explanatory code and only add comments when something important cannot be expressed through structure and naming.

   line 33
9. Distinctive:

   Treat public interfaces, however, like the API of a published package.

   line 36
10. Distinctive:

    Document exports from deeper modules so that their contract, usage, and relevant constraints are understandable without knowing the …

    line 37
11. Distinctive:

    Test changed behavior and interfaces, not implementation internals.

    line 40
12. Distinctive:

    If testing requires stubbing or mocking internal details, reconsider how responsibilities and dependencies are separated.

    line 41
13. Distinctive:

    Keep testing proportional to the change.

    line 44
14. Distinctive:

    Add unit tests where isolated logic provides clear value, such as for complex calculations or algorithms.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.