agentleFS
Sign inStart free
MarkuysaMarkuysa/vibe-coding-template/CLAUDE.md

vibe-coding-template

CLAUDE.md1 starsChanged 4 months agoMITView on GitHub

The file

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

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never touch {{PROTECTED_PATHS}} without explicit permission.

    line 16
  2. Distinctive:

    When compacting, preserve: the full list of changed files, test commands, and decisions with their reasoning.

    line 25

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

Stack

{{STACK}} <!-- e.g. Next.js 15, TypeScript strict, Tailwind, Supabase -->

Commands

  • dev: {{DEV_CMD}}
  • test: {{TEST_CMD}}
  • lint: {{LINT_CMD}}
  • build: {{BUILD_CMD}}

Rules

  • Non-trivial changes go through a plan first: propose, then write code.
  • Tests are mandatory for business logic.
  • Design tokens come only from {{TOKENS_FILE}}.
  • Never touch {{PROTECTED_PATHS}} without explicit permission.

References (read on demand, do not hold in context)

  • Spec: docs/PRD.md
  • Architecture: docs/ARCHITECTURE.md
  • Cheat sheet: docs/QUICK_REF.md
  • Decisions (ADR): docs/decisions/

Compaction policy

When compacting, preserve: the full list of changed files, test commands, and decisions with their reasoning. Condense research findings aggressively.

<!-- Keep this file under 200 lines. Procedures belong in .claude/skills/, where they cost nothing until invoked; this file is loaded into context every session. -->

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