CLAUDE.md Generator
Answer six questions, get a ready-to-commit CLAUDE.md for your repo. The most-requested artifact from Course 01, as a tool.
The app — live, try it
CLAUDE.md
# my-app
## Stack
Next.js 15 (App Router), TypeScript, Tailwind
## Commands
- Install: `pnpm install`
- Dev server: `pnpm dev`
- Tests: `pnpm test`
Run the tests after every change to logic. If a command fails, paste the full
error before attempting a fix.
## House rules
- Prefer small, focused diffs. If a change touches more than ~5 files, stop and propose a plan first.
- For new behavior, write or update the failing test first, show it failing, then implement.
- Match the file's existing style and naming; do not introduce new patterns without asking.
## Working agreement
State your plan in 2–3 bullets before multi-file changes. When unsure about
intent, ask one precise question instead of guessing.
The build log — every prompt
Press Play to replay this transcript step-by-step.
0 / 8
Condensed from the real build session: every user prompt is shown; repetitive tool turns are trimmed. Scrub through it — the corrections are the curriculum.
What to notice
- Templates + a form beat a blank page: the generator encodes the CLAUDE.md structure taught in Course 01 (stack → commands → house rules → gotchas → working agreement).
- One real subtlety the agent caught only when told: `npm` needs `npm run dev` while pnpm/yarn/bun accept `pnpm dev` — template logic, not styling, is where review attention pays.
- Live output with useMemo means the document is always in sync — no "generate" button to forget.
Remix it — one prompt
Paste this into Claude Code (or Codex, or Cursor) and compare what you get with the live version above. Changing one requirement and seeing what moves is the fastest way to learn the loop.
Build a "CLAUDE.md generator" React component (TypeScript). Left side: a form —
project name, one-line description, stack, package manager (pnpm/npm/yarn/bun),
dev and test script names, six house-rule checkboxes (small diffs, tests first,
no drive-by refactors, conventional commits, ask before migrations, match style),
and a multiline "project gotchas" field. Right side: the generated CLAUDE.md,
regenerating live via useMemo, with a copy button. npm needs "run" before script
names; the others don't — get that right.Go deeper
This demo is a two-minute taste of the loop. Course 01: project memory, from lesson 1 teaches it properly — free, no signup. Prompt logs and source live in the open-source repo — ★ star it if these demos help.