We split this skill into the rules it gives an agent

12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈10

  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. Very specific:

   Before dev work, call search_skills with the phase you're in (spec, planning, development, review, merge, release) or a topic (security, …

   line 12
2. Very specific:

   Call get_skill with the name to load it in full.

   line 13
3. Distinctive:

   If a skill applies, you must use it.

   line 14
4. Distinctive:

   Do one thing at a time. Finish it before starting the next.

   line 19
5. Distinctive:

   Verify before you claim done.

   line 20
6. Distinctive:

   Read a file before you edit it.

   line 23
7. Distinctive:

   Prefer the dedicated tool over a shell command when one exists.

   line 24
8. Distinctive:

   Don't act on a grep match alone.

   line 25
9. Distinctive:

   Verify before claiming. "It works" means you ran it and saw it work this turn.

   line 28
10. Distinctive:

    Test, don't assume. If a capability is uncertain, probe it.

    line 29
11. Distinctive:

    Don't narrate what you didn't check — the operator's mood, the time of day, how big a win is.

    line 30
12. Distinctive:

    Ask only when genuinely blocked.

    line 35

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