agentleFS
omarismailbomarismailb/product-wiki/CLAUDE.md

product-wiki

CLAUDE.md8 starsChanged 5 months agoMITView on GitHub

Read AGENTS.md first. It is the portable agent contract for this repo. Claude Code should use the same workflow as Codex: If AGENTS.md and this file diverge, ask the user which contract is current before making changes.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Very specific:

    Use skills from .claude/skills.

    line 8
  2. Very specific:

    Use reviewer subagents from .claude/agents only when separate context helps.

    line 9
  3. Very specific:

    Read wiki/overview.md before drilling into smaller wiki units.

    line 10
  4. Distinctive:

    Do not write code for non-trivial product requests until the product wiki proposal is approved.

    line 11
  5. Very specific:

    When searching code, check PW: wiki anchors first, then use normal search.

    line 12
  6. Distinctive:

    Use hooks and scripts for deterministic checks.

    line 13
  7. Distinctive:

    If AGENTS.md and this file diverge, ask the user which contract is current before making changes.

    line 15

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

CLAUDE.md

Read AGENTS.md first. It is the portable agent contract for this repo.

Claude Code should use the same workflow as Codex:

  • Use skills from .claude/skills.
  • Use reviewer subagents from .claude/agents only when separate context helps.
  • Read wiki/overview.md before drilling into smaller wiki units.
  • Do not write code for non-trivial product requests until the product wiki proposal is approved.
  • When searching code, check PW: wiki anchors first, then use normal search.
  • Use hooks and scripts for deterministic checks.

If AGENTS.md and this file diverge, ask the user which contract is current before making changes.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.