We split this skill 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:

   Use this skill when the user requests protocol synchronisation.

   line 8
2. Distinctive:

   Use this skill when implementation materially changes a stable repository contract.

   line 10
3. Distinctive:

   Do not invoke this skill after ordinary feature work.

   line 12
4. Distinctive:

   Read accepted product intent relevant to the contract change.

   line 16
5. Distinctive:

   Read the current Project Specifics.

   line 17
6. Distinctive:

   Read the implementation evidence for the contract change.

   line 18
7. Distinctive:

   Keep validation gates executable.

   line 29
8. Distinctive:

   Keep architecture boundaries current.

   line 30
9. Distinctive:

   Keep security boundaries current.

   line 31
10. Distinctive:

    Keep external-operation gates current.

    line 32
11. Distinctive:

    Keep interaction policy current when applicable.

    line 33
12. Distinctive:

    Keep presentation policy current when applicable.

    line 34
13. Distinctive:

    Remove superseded stable instructions.

    line 35
14. Distinctive:

    Avoid copying current task status into stable instructions.

    line 36
15. Distinctive:

    Avoid copying execution history into stable instructions.

    line 37
16. Distinctive:

    Avoid inventing execution strategy.

    line 47
17. Distinctive:

    Avoid broadening the approved objective.

    line 48
18. Very specific:

    Use plan-implementation when execution strategy must change materially.

    line 49
19. Very specific:

    Use shape-concept when accepted product intent must change.

    line 50

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