Fabler Labs

Guides · Free tool · runs in your browser · no signup

CLAUDE.md generator

Answer a few questions about your project and get a clean, copy-paste CLAUDE.md for Claude Code — structured the way the current docs recommend. Everything runs locally; nothing you type is uploaded or stored.

Fill every field and the file this produces scores 100/100 on our own CLAUDE.md checker — measured 29 July 2026. Leave the architecture or guardrail notes blank and it scores lower, because those are the parts an agent actually needs. Generate one, paste it into the checker, and see for yourself.

Commands (leave blank to omit a line)

Conventions

Your CLAUDE.md 

          
Save it as CLAUDE.md at your repo root and commit it. Want it read by Cursor and Copilot too? Save the same content as AGENTS.md.

        

      


      

        
Want more than a starting point?

        
This gives you a solid, tailored CLAUDE.md. The AI Coding Workflow Pack ($24) goes further — 26 senior-level assets: ready-to-use subagents, slash commands, rules templates, and prompts for Claude Code, Cursor, and Copilot. Encode your standards once and stop re-explaining them.

        

          See what's inside →
          See the project timeline
        

      


      
What is a CLAUDE.md file?

      
CLAUDE.md is a plain-Markdown file that Claude Code reads at the start of every session in a project. It carries the context you'd otherwise repeat every time: the commands to run, where code lives, your conventions, and what not to touch. A project CLAUDE.md lives at your repository root and is checked into version control, so your whole team — and their agents — share the same instructions.

      
Already have one? Run it through the free CLAUDE.md checker to score it 0–100 and get specific fixes.

      
For a fuller walkthrough — the exact load order (managed → user → project → local), @imports, how it relates to AGENTS.md, and what to leave out — see the annotated CLAUDE.md example. Setting up reusable agents or commands next? The guide library covers subagents, skills, slash commands, hooks, and MCP.


      
Tips for a CLAUDE.md that actually helps

      
    
        
  • Be specific and testable. "Run pnpm test before every commit" beats "write good tests." The agent can act on the first.
    • 
        
  • Keep it short. Aim for under ~200 lines. It's loaded in full every session, so every line costs tokens and dilutes the important rules.
    • 
        
  • Only durable facts. Put project-wide truths here; move path-specific guidance into .claude/rules/ and one-off notes into CLAUDE.local.md (git-ignored).
    • 
        
  • Say what not to do. A short "Do not" list (generated files, migrations, direct commits to main) prevents the most common mistakes.
    • 
      


      
Also from Fabler Labs: AI Coding Workflow Pack ($24) · Autonomous Agent Starter Kit ($29) · AI Coding Security Pack ($29) · Claude Knowledge-Work Pack (free) · Mainspring (open source) · Blog

    

  


    

      
FAQ

        

          What is a CLAUDE.md file?
          
CLAUDE.md is a plain-Markdown file Claude Code reads at the start of every session in a project. It tells the agent how your project is built — the commands to run, where code lives, your conventions, and what not to touch — so you don't re-explain it each time. A project CLAUDE.md lives at your repo root and is checked into version control so your team shares it.

        

        

          Is this CLAUDE.md generator free?
          
Yes. It is completely free and needs no signup. It runs entirely in your browser — your project details are never sent to a server or stored.

        

        

          Where do I put the generated CLAUDE.md?
          
Save it as CLAUDE.md at the root of your repository (./CLAUDE.md) and commit it. Personal, all-project instructions go in ~/.claude/CLAUDE.md; private per-project notes go in ./CLAUDE.local.md, which you add to .gitignore.

        

        

          Does this work for Cursor or other AI editors?
          
The structure works well as an AGENTS.md too, which Cursor, GitHub Copilot, and other tools read. Save the same content as AGENTS.md, or create a CLAUDE.md that imports it with a single @AGENTS.md line so both tools share one source of truth.

        

        

          How long should a CLAUDE.md be?
          
Keep it under about 200 lines. CLAUDE.md is loaded in full into every session and consumes tokens, and longer files are followed less reliably. Put only durable, project-wide facts in it; move path-specific guidance into .claude/rules/ or split it out with @imports.