agentleFS
BlockKnown publisherblock/builderbot/apps/penpal/CLAUDE.md

builderbot / penpal

CLAUDE.md105 starsChanged 7 months agoApache-2.0View on GitHub

This repo uses ANCHORS for requirements-driven development. You MUST load the anchors skill (/anchors) before making any code changes. When adding or modifying features, you must update ALL THREE documents before writing code: 1. PRODUCT.md — Add a P-* requirement (user-facing behavior only) 2. ERD.md — Add an E-* requirement with ← backlink to the P-* ID 3. TESTING.md — Add or update the coverage mapping table so every new/changed requirement has a test-layer assignment. Always verify the table reflects…

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    When adding or modifying features, you must update ALL THREE documents before writing code:

    line 5

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

ANCHORS — REQUIRED FOR ALL CHANGES

This repo uses ANCHORS for requirements-driven development. You MUST load the anchors skill (/anchors) before making any code changes.

When adding or modifying features, you must update ALL THREE documents before writing code:

  1. PRODUCT.md — Add a P-* requirement (user-facing behavior only)
  2. ERD.md — Add an E-* requirement with ← backlink to the P-* ID
  3. TESTING.md — Add or update the coverage mapping table so every new/changed requirement has a test-layer assignment. Always verify the table reflects the current scope — even if a row already exists, it may need updating.

Implementation and test code must include inline requirement ID comments (e.g., // E-PENPAL-FEATURE-NAME).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.