agentleFS
Sign inStart free
jpantsjohajpantsjoha/ai-native-developer-experience/CLAUDE.md

ai-native-developer-experience

CLAUDE.md13 starsChanged 27 days agoApache-2.0View on GitHub

AGENTS.md, CLAUDE.md and GEMINI.md carry the same portable instructions. Before taking delivery work, read docs/STATUS.md, then the relevant slice of docs/ROADMAP.md; inspect open issues, PRs and worktrees and coordinate with the active owner before starting a competing lane. Ground changed intent in docs/VISION.md and the relevant versioned requirement. Use skills/delivery-orchestrator/SKILL.md to maintain the golden thread through GitHub Issues, acceptance checks, review and release. Load only the role, skill and artifact sections needed for the current task; do not preload the…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before taking delivery work, read docs/STATUS.md, then the relevant slice of docs/ROADMAP.md.

    line 5
  2. Very specific:

    Use skills/delivery-orchestrator/SKILL.md to maintain the golden thread through GitHub Issues, acceptance checks, review and release.

    line 10
  3. Very specific:

    Before delegation read docs/MODEL-ROUTING.md.

    line 16

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

Shared agent contract

AGENTS.md, CLAUDE.md and GEMINI.md carry the same portable instructions.

Before taking delivery work, read docs/STATUS.md, then the relevant slice of docs/ROADMAP.md; inspect open issues, PRs and worktrees and coordinate with the active owner before starting a competing lane.

Ground changed intent in docs/VISION.md and the relevant versioned requirement. Use skills/delivery-orchestrator/SKILL.md to maintain the golden thread through GitHub Issues, acceptance checks, review and release. Load only the role, skill and artifact sections needed for the current task; do not preload the whole library.

For repository changes read docs/REPOSITORY-CONTRACT.md. Run make check and fresh, read-only independent adversarial review of the exact candidate before merge. Before delegation read docs/MODEL-ROUTING.md. Explicit user authority and project controls govern external actions; skill installation grants no authority.

Reconcile affected requirements, decisions, status, roadmap and changelog as work changes. After an authorised merge, verify integration and safely clean up only this lane's merged branches and clean worktrees. Never overwrite another lane.

Canonical skills live in skills/; .agents/skills/ is a discovery alias.

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.

Check your setup, free