CLAUDE.md generator

Answer five fields, get a CLAUDE.md sized to stay under your context budget. It carries your stack, your commands and the rules the code cannot tell Claude — nothing else. Free, no account, it runs in your browser.

Runs in your browser · no upload, no account

Most generators pad. This one subtracts.

Paste "generate a CLAUDE.md" into a chat and you get back a role-play preamble ("You are an expert senior developer…"), a paragraph on writing clean code, and a copy of your package.json as a bullet list. None of it changes a single line Claude Code writes. All of it is loaded into context on every session, competing with the two rules that actually matter.

CLAUDE.md is memory, not a system prompt. Claude already tries to write clean code and handle errors. What it cannot know is that your money is stored in cents, that src/legacy/* is scheduled for deletion, or that pnpm dev runs on port 3001. That is the whole job of this file, and it is all this generator writes. If you leave a field empty, its section does not appear — there is no filler to hit a word count.

The same logic runs in reverse in our CLAUDE.md audit: paste a file you already have and it flags the lines to cut. This tool just starts you at the trimmed end.

What goes in each field

The five inputs and why they earn a place in an always-loaded file
FieldPut inLeave out
Stack Framework and the two or three choices an agent would otherwise guess: ORM, CSS approach, payment provider. Exact patch versions. The lockfile has those and it stays current; a pinned number here goes stale.
Commands The ones with a surprise: a non-default port, a seed step before tests, a build flag. npm install, npm run build — anything the agent would type correctly on the first try.
Project rules The "do not" lines that burned you: a banned import, a data invariant, a staging gotcha. "Write readable code", "follow best practices" — default behaviour dressed as a rule.

Frequently asked questions

What is CLAUDE.md and why keep it short?

It is the memory file Claude Code loads at the start of every session, so its cost is paid on every task. A long file still works, but the model has to find your two real rules inside it. Concise is not a style choice here — it is how the file is used.

Is my input uploaded?

No. The generator is a JavaScript file the browser downloads once and runs locally. There is no request, no account and no logging. Check the network tab in devtools.

Why does the output skip a role-play preamble and a "best practices" section?

Because CLAUDE.md is project memory, not a system prompt. "You are an expert developer" and "write clean code" cost tokens and change nothing about the code produced. The generator only writes lines Claude Code cannot infer from your repo.

Should I paste my file tree or database schema in?

No, and there is no field for it. The repo already holds both, and a pasted copy drifts after the first refactor or migration. Reference the real files with @path/to/file so they load when a task needs them.

What is the single most useful field?

Project rules. The stack and commands help, but the lines that earn their place are the "never do X" constraints that come from a bug you already hit — a banned import, a data invariant, a staging trap. Nothing in the code says these out loud.

How is this different from the audit tool?

The audit reacts to a file you already have and tells you what to cut. This generator starts you at the trimmed end from a blank slate. Same philosophy, opposite direction.

What does the paid generator do that this does not?

This assumes you already know your stack and conventions. The paid generator asks 117 questions and writes the specification behind the rules file — schema, auth flows, security, legal, file structure. Two generations are free with an account; unlimited is $19/month or $99 once.

This carries your rules. The full spec writes what is behind them.

The generator above needs you to already know your stack and conventions. The paid generator asks 117 questions and writes the specification itself — database schema, auth flows, security and legal sections, file structure — then hands you the CLAUDE.md on top. 2 free prompts with an account, no card.

Generate the full spec, free