Free CLAUDE.md Generator — Build Your Claude Code Config File

Pick your stack, add your preferences, hit generate. Get a CLAUDE.md file that makes Claude Code work the way you actually code.

Project name Project description (1-2 sentences)

Stack

Target platform

Where the code runs. Adds platform-specific constraints (memory limits, OS APIs, etc.).

Communication style

Direct, no fluff Always explain WHY for non-obvious decisions If ambiguous, ask ONE question — don't guess No hedging or "I think maybe" Never use em dashes Never use emoji

Code style

No comments unless the "why" is non-obvious Prefer strict typing Never use any in TypeScript Prefer functional over OOP Small, focused diffs Prefer named exports Never ship a feature without at least one test

Constraints

Ask before adding new dependencies Ask before deleting files Don't refactor unrelated code Match existing code style, don't reformat For changes touching more than 3 files, explain plan first Fix root causes, not symptoms. Don't bypass with --no-verify. Token-efficient editing (grep + line slices, not full-file reads) Maintain PROJECT_STATE.md checkpoint file

Verification / closed-loop feedback

Force the AI to actually run typecheck / lint / tests and iterate on the output instead of declaring "done" while the code doesn't compile.

After any change, run `./verify.sh` and iterate until exit 0 Always run typecheck after edits and read the output Always run linter after edits and fix reported issues Always run the relevant test file after touching prod code Never mark a task complete until typecheck + lint + tests are green On failures, fix the FIRST error only, then re-run Never silence errors to pass

Negative constraints (anti-hallucination, anti-bloat)

Do-NOT rules. Often 2x more effective than positive instructions.

Never invent packages or CLI flags without verifying Do not rewrite 400-line files for 2-line changes No comments explaining self-explanatory code Never fix bugs outside the current task silently Never guess an API signature — read the file first Never generate tests that always pass (`assert(true)`) Never swallow exceptions to make code "work" Do not add abstractions for one caller

Testing

Common commands (run/build/test) Additional rules (one per line)

Your CLAUDE.md

What is a CLAUDE.md file?

Claude Code reads CLAUDE.md at the root of your project and injects it as context into every session. It's how you make Claude Code stop being annoying about comments, testing, dependencies, and style. Same idea as .cursorrules, but for Claude Code (see our .cursorrules generator).

CLAUDE.md Generator

Your CLAUDE.md

What is a CLAUDE.md file?

How to use the file

Related