We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈11

  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:

   create new evidence rows

   line 25
2. Distinctive:

   update canonical understanding/matrix

   line 28
3. Distinctive:

   update hypotheses/open questions

   line 29
4. Distinctive:

   Only PROMOTED VERIFIED claims enter:

   line 34
5. Distinctive:

   Never delete contradictory history without trace.

   line 40
6. Distinctive:

   Every canonical claim must:

   line 47
7. Distinctive:

   When a verified change affects architecture, runtime flow, integration selection, configuration behavior, state ownership, or lifecycle:

   line 55
8. Distinctive:

   update the relevant model artifact.

   line 57
9. Distinctive:

   update the affected Mermaid diagram when relationships changed.

   line 58
10. Distinctive:

    keep the readiness/adversarial audit separate from the TDD.

    line 60
11. Distinctive:

    Do not leave canonical evidence updated while the consumer-facing architecture model remains stale.

    line 62

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