We split this AGENTS.md into the rules it gives an agent

16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈12

  Distinctive · estimate

  This author's own choices. Worth a look.

• 4

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Run from repository root:

   line 13
2. Distinctive:

   Prefer deterministic scripts over interactive/manual steps.

   line 24
3. Very specific:

   Keep command names stable (smoke, check, test, ci).

   line 25
4. Distinctive:

   Update docs and scripts in the same change when workflow behavior changes.

   line 26
5. Distinctive:

   Avoid side effects outside the repo unless explicitly required.

   line 27
6. Distinctive:

   Keep internal data models typed and normalized.

   line 32
7. Distinctive:

   Keep each module focused on one responsibility.

   line 33
8. Very specific:

   Document boundary ownership in docs/ARCHITECTURE.md.

   line 34
9. Distinctive:

   Keep event fields stable for querying and alerting.

   line 40
10. Distinctive:

    Update status checkpoints during execution and after major decisions.

    line 47
11. Very specific:

    Run make check before make test.

    line 51
12. Very specific:

    Run make ci before pushing large refactors.

    line 52
13. Distinctive:

    Treat lint/type failures as blocking.

    line 53
14. Distinctive:

    Remove stale scripts/docs quickly.

    line 57
15. Distinctive:

    Keep templates and real workflows in sync.

    line 58
16. Distinctive:

    Run periodic harness audits:

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.