pi-public / pi

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

16 rules. About 0 are common, 14 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈14

  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:

   Keep implementation ownership with the main agent or the developer.

   line 5
2. Distinctive:

   Keep architecture decisions and product trade-offs under direct control.

   line 6
3. Distinctive:

   Check the current branch before editing.

   line 11
4. Distinctive:

   Do not work directly on main.

   line 12
5. Distinctive:

   Verify unfamiliar APIs in docs, skills, Context7, or installed source.

   line 13
6. Distinctive:

   Prefer source-backed implementation over memory.

   line 14
7. Very specific:

   Do not keep old code as legacy unless explicitly requested.

   line 16
8. Distinctive:

   Always take some time to explore the code and understand the architecture before implementing anything.

   line 17
9. Distinctive:

   Use subagents for focused research, review, verification, or when the work is boring and you don't want to do it yourself.

   line 21
10. Distinctive:

    After each completed phase, plan, or significant change, request an appropriate review.

    line 25
11. Distinctive:

    Never leak personal information in output, code, tests, docs, or commit messages.

    line 29
12. Distinctive:

    Use generic placeholders for paths, names, emails, and other personal details.

    line 30
13. Distinctive:

    Always sign the commits or the tags.

    line 34
14. Very specific:

    Avoid review-process commit messages like fixing review comments.

    line 36
15. Distinctive:

    Keep documentation concise and focused on the key points.

    line 38
16. Distinctive:

    Write documentation, README files, Markdown guides, and user-facing prose from the present product state.

    line 39

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

• Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

  Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

• In this repository22 other files it gives its agents.

  • agent-workflowsSkill
  • architecture-securitySkill
  • code-review-releaseSkill
  • documentation-passSkill
  • exploring-codebasesSkill
  • find-skillsSkill
  • frontend-webSkill
  • githubSkill
  • grill-meSkill
  • grill-with-docsSkill
  • improve-codebase-architectureSkill
  • improveSkill
  • product-design-writingSkill
  • project-backlogSkill
  • prototypeSkill
  • red-teaming-decisionsSkill
  • systems-backendSkill
  • tddSkill
  • testing-debugging-verificationSkill
  • to-issuesSkill
  • to-prdSkill
  • triageSkill