agentleFS
Sign inStart free
vadimvitvickiyvadimvitvickiy/vv-agent-kit/templates/CLAUDE.md

vv-agent-kit / templates

CLAUDE.md0 starsChanged 50 days agoMITView on GitHub

{{PROJECT_SUMMARY}} 1. Never commit or stage without an explicit request. 2. Present a plan before multi-step changes and wait for approval. 3. Fix the root cause, not the symptom. No leaky flags, one-off special cases, or guards that mask bad state. A genuinely unavoidable workaround is labelled as one, with the real cause named. 4. Never hand-edit generated files. Regenerate them. One line: .claude/ is committed and reusable; .agents/ is gitignored and disposable. Because .agents/ is disposable by construction, anything…

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Fix the root cause, not the symptom: No leaky flags, one-off special cases, or guards that mask bad state.

    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

{{PROJECT_NAME}}

{{PROJECT_SUMMARY}}

Critical rules

  1. Never commit or stage without an explicit request.
  2. Present a plan before multi-step changes and wait for approval.
  3. Fix the root cause, not the symptom. No leaky flags, one-off special cases, or guards that mask bad state. A genuinely unavoidable workaround is labelled as one, with the real cause named.
  4. Never hand-edit generated files. Regenerate them.

Where agent content lives

One line: .claude/ is committed and reusable; .agents/ is gitignored and disposable.

The question being askedLocation
What is always true here?this file (AGENTS.md symlinks to it)
What's true when I touch these files?.claude/rules/*.md — auto-loads on a paths: match
What are this repo's facts?.claude/context/
What did we decide, and why?.claude/context/decisions.md
What was the design?.claude/context/specs/
Plans and todos for work in flight.agents/plans/
Continuation and resume state.agents/state/
Scratch, subagent reports, transcripts.agents/scratch/

Because .agents/ is disposable by construction, anything that must outlive the session is promoted into .claude/context/. See vvkit:capturing-decisions.

Commands

{{BUILD_CMD}}   # build
{{TEST_CMD}}    # test
{{LINT_CMD}}    # lint

Reference

DocRead when
.claude/context/architecture.mdConstraints that cannot be derived by reading code
.agents/state/map.xmlBefore fanning out searches. Generated by scripts/map.sh; never hand-edited
.claude/context/decisions.mdA choice looks arbitrary and you need the reasoning

Git

Working branch {{WORKING_BRANCH}}; release branch {{MAIN_BRANCH}}.

Known debt

Recorded so it is not rediscovered, not scheduled.

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