We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈6

  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:

   Prefer small focused files with one clear responsibility.

   line 12
2. Distinctive:

   Use typed contracts and schema validation at external boundaries.

   line 13
3. Distinctive:

   Prefer clear names and simple control flow over clever abstractions.

   line 14
4. Distinctive:

   Avoid god files, vague helpers, dead code, and duplicated logic.

   line 15
5. Distinctive:

   Keep error handling explicit and useful without leaking secrets.

   line 16
6. Distinctive:

   Test coverage for changed behavior.

   line 23

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