agentleFS
Sign inStart free
usibuildsusibuilds/claude-context-zones/claude-code/CLAUDE.md

claude-context-zones / claude-code

CLAUDE.md0 starsChanged 12 days agoMITView on GitHub

The file

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

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the files the current step needs.

    line 6
  2. Very specific:

    When a feature passes its tests: tick it in PLAN.md, update HANDOFF.md, tell the user to /clear.

    line 7
  3. Distinctive:

    If the Context Guardian says yellow: finish the current task, start nothing new.

    line 10
  4. Very specific:

    If it says red: write the handoff, then ask the user to /clear and /resume.

    line 11

≈ “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 — project rules (keep this file SHORT; it loads every turn)

Workflow: top-down plan, bottom-up build

  • Source of truth: docs/PLAN.md (what to build) + docs/HANDOFF.md (where we stopped).
  • One feature per session. Start with /resume or /feature F<n>.
  • Read only the files the current step needs. Never read the whole project "to understand it".
  • When a feature passes its tests: tick it in PLAN.md, update HANDOFF.md, tell the user to /clear.

Context hygiene

  • If the Context Guardian says yellow: finish the current task, start nothing new.
  • If it says red: write the handoff, then ask the user to /clear and /resume.
  • Large docs (PDF/DOCX/XLSX): convert to Markdown first (markitdown file.pdf -o file.md) and read the .md.
  • Logs: read only the last ~80 lines, never the whole file.

Communication

  • <your language preference, e.g. "Explain in English; keep code and file names in English">
  • Short answers; explain the "why" in one line when you change something important.

Project basics

  • <stack, how to run, how to test — 3 to 6 lines>

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