agentleFS
Sign inStart free
extra-orgextra-org/extra/CLAUDE.md

extra

CLAUDE.md119 starsChanged 5 months agoMITView on GitHub

Declarative platform for building AI agent systems. See docs/ for architecture details and tasks/ for current work. The product/brand name is Extra (matches the GitHub repo, docs site, and docs.json). agent-engine is only the PyPI/package name of the core engine; agentctl and agent-manager are the CLI/console scripts. Don't call the product "Agent Engine" in user-facing copy (README, docs landing page) — use "Extra". Skills, roles, and workflows live in .ai/ — the single source of truth. .claude/skills/ is generated from…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not skip tests or hardcode secrets.

    line 26
  2. Distinctive:

    Do not change architecture decisions without explicit approval.

    line 27
  3. Very specific:

    Do not edit .claude/skills/, .claude/agents/, or .claude/workflows/ directly.

    line 28

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

Declarative platform for building AI agent systems. See docs/ for architecture details and tasks/ for current work.

Naming

The product/brand name is Extra (matches the GitHub repo, docs site, and docs.json). agent-engine is only the PyPI/package name of the core engine; agentctl and agent-manager are the CLI/console scripts. Don't call the product "Agent Engine" in user-facing copy (README, docs landing page) — use "Extra".

Skills

Skills, roles, and workflows live in .ai/ — the single source of truth. .claude/skills/ is generated from there (make generate-ai). Do not edit generated files directly.

Commands

make generate-ai   # regenerate .claude/, .codex/ from .ai/
make format        # ruff format
make lint          # ruff check
make typecheck     # mypy
make test          # pytest
make check         # format-check + lint + typecheck + test + generated-stub check

Guardrails

  • Do not skip tests or hardcode secrets.
  • Do not change architecture decisions without explicit approval.
  • Do not edit .claude/skills/, .claude/agents/, or .claude/workflows/ directly.

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