agentleFS
Sign inStart free
mhlagharimhlaghari/stuntman/CLAUDE.md

stuntman

CLAUDE.md16 starsChanged 2 months agoMITView on GitHub

These are living documents — read them first, keep them current. Read this first — start of every session (or just run /handoff): 1. HANDOFF.md — the session baton: what the last session changed, the next step, gotchas. Assume zero memory of prior sessions. 2. STATUS.md — the board: built / in progress / planned. 3. SPEC.md — the contract: what this is, the load-bearing principles, where it's going. Build to it. 4. STRATEGY.md — the honest why / direction.…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

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

    Always update HANDOFF.md (what changed, next step, gotchas) and STATUS.md (refresh the board).

    line 16
  2. Very specific:

    Update SPEC.md, STRATEGY.md, or README.md whenever the change touched what they cover — and add a dated changelog line.

    line 17
  3. Distinctive:

    Never commit without explicit user authorization.

    line 18

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

<!-- stuntman:scaffold:start -->

Project memory protocol

These are living documents — read them first, keep them current.

Read this first — start of every session (or just run /handoff):

  1. HANDOFF.md — the session baton: what the last session changed, the next step, gotchas. Assume zero memory of prior sessions.
  2. STATUS.md — the board: built / in progress / planned.
  3. SPEC.md — the contract: what this is, the load-bearing principles, where it's going. Build to it.
  4. STRATEGY.md — the honest why / direction. Read before any big call.
  5. README.md — what the project is and how to run it.

Before you stop — end of every session:

  • Always update HANDOFF.md (what changed, next step, gotchas) and STATUS.md (refresh the board).
  • Update SPEC.md, STRATEGY.md, or README.md whenever the change touched what they cover — and add a dated changelog line.
  • Never commit without explicit user authorization.

A task isn't "done" until the docs its change touched reflect it.

<!-- stuntman:scaffold:end -->

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