agentleFS
Sign inStart free
holon-runholon-run/holon/CLAUDE.md

holon

CLAUDE.md194 starsChanged 4 days agoApache-2.0View on GitHub

This file is read by Claude Code and other agent tooling. Repository-specific guidance (layout, commands, coding conventions, constraints) is maintained in AGENTS.md and should be treated as the source of truth. For deeper contributor references (debugging, contracts), see docs/development.md. Additional docs (non-authoritative, deeper dives): - CONTRIBUTING.md - docs/ (architecture, modes, skills, GitHub/CI integrations) - rfc/ (design notes and proposals)

The file

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

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md before making changes.

    line 7
  2. Distinctive:

    If you discover outdated guidance, update AGENTS.md (not this file).

    line 8
  3. Distinctive:

    If you work in a subdirectory, also check for nested AGENTS.md files with more specific rules.

    line 9

≈ “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

CLAUDE.md

This file is read by Claude Code and other agent tooling.

Repository-specific guidance (layout, commands, coding conventions, constraints) is maintained in AGENTS.md and should be treated as the source of truth.

  • Read AGENTS.md before making changes.
  • If you discover outdated guidance, update AGENTS.md (not this file).
  • If you work in a subdirectory, also check for nested AGENTS.md files with more specific rules.

For deeper contributor references (debugging, contracts), see docs/development.md.

Additional docs (non-authoritative, deeper dives):

  • CONTRIBUTING.md
  • docs/ (architecture, modes, skills, GitHub/CI integrations)
  • rfc/ (design notes and proposals)

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.

Check your setup, free