CLAUDE.md Writer
Writes a complete CLAUDE.md file for your project based on your tech stack and team conventions.
What it does
A CLAUDE.md file gives Claude Code persistent context about a project — its architecture, conventions, commands, and preferences. Claude reads this file at the start of every session and uses it to ground every response. Without one, Claude starts from zero every time: it does not know your commands, your folder structure, your lint rules, or your team's conventions.
Why every Claude Code project needs one
Teams that use Claude Code without a CLAUDE.md end up repeating themselves. Every session starts with 'we use pnpm, not npm', 'our API lives in app/api', 'do not create new components, extend existing ones'. A good CLAUDE.md kills those ten repeated lines at the top of every chat and gives you a more predictable assistant from the first message.
What this prompt generates
This prompt produces a CLAUDE.md with ten numbered sections: overview, tech stack, folder structure, commands, code style, state management, testing, always-do, never-do, and common tasks. Each section is specific to the project details you paste in — never generic boilerplate. The output is ready to drop at the root of your repo and commit.
Who should use it
Anyone starting a new project with Claude Code, anyone adopting Claude Code on an existing codebase, and team leads who want consistent behavior across everyone's sessions. The prompt is also a great companion to the Flutter Development, Next.js Full Stack, and React Native skills — the skills handle language-level conventions while CLAUDE.md handles project-level ones.
How to install
Which tool are you using?
Not sure? Claude.ai is the website. Claude Code is the command-line tool you install separately. Cursor is a code editor that reads .cursorrules.
- 01
Open Claude.ai
Go to claude.ai in your browser and click 'New conversation' to start a fresh chat.
You need a free Claude account. If you don't have one, sign up at claude.ai — it's free.
- 02
Copy the prompt
Scroll down to the prompt file section below and click the 'Copy' button. The entire prompt will be copied to your clipboard.
Make sure you copy the FULL prompt — it may be long. The copy button gets everything.
- 03
Paste into Claude
Click inside the chat input box at the bottom of the screen. Press Ctrl+V (Windows) or Cmd+V (Mac) to paste the prompt.
The prompt will appear in the input box. Don't press Enter yet.
- 04
Add your task
After the pasted prompt, add a line break and then describe what you need. For example: 'My project is a Flutter e-commerce app using Riverpod and Firebase.'
The prompt sets up Claude as an expert. Your task tells it what to actually do.
- 05
Press Enter and get your result
Press Enter or click the send button. Claude will respond as a specialized expert using the instructions in the prompt.
Save this conversation! You can continue in the same chat and Claude will remember the context from the prompt.
The claude prompt file
Copy the full contents below, or download the file directly.
You are an expert at writing CLAUDE.md files for software projects. A CLAUDE.md file gives Claude Code persistent context about a project — its architecture, conventions, commands, and preferences. Claude reads this file at the start of every session. I will give you information about my project. Generate a complete CLAUDE.md file that includes: 1. Project overview (2-3 sentences)2. Tech stack with versions3. Project structure explanation4. Key commands (dev, build, test, deploy)5. Code style and conventions6. State management approach7. Testing approach8. Things Claude should always do9. Things Claude should never do10. Common tasks and how to approach them My project details:[PASTE YOUR PROJECT DETAILS HERE] Generate a CLAUDE.md that is specific, actionable, and written in a way that helps Claude give better responses for this exact project.Example output
What Claude does before and after you install this claude prompt.
Claude writes a generic CLAUDE.md template with placeholder sections like "describe your testing approach here". You end up writing the whole thing yourself.
Claude writes a concrete CLAUDE.md: "Run pnpm dev for local, pnpm test:watch for tests, db lives in Supabase with RLS on, never call service_role key from client, always prefer Server Actions over API routes." Specific and ready to commit.
Customization tips
Edit section 6 (state management) if your team does not use a single approach — it helps to say 'Redux for cart flow, Zustand for UI state, no global context providers'. If you have a monorepo, run the prompt per package and keep each CLAUDE.md scoped. For very large projects, add an extra section for 'Local testing setup' covering seed scripts and environment toggles.
Related resources
CLAUDE.md Generator Skill
Generates a project-specific CLAUDE.md file by scanning your codebase structure and conventions.
Next.js Full Stack Skill
App router patterns, server components, API routes, and Next.js 14+ conventions baked into every response.
Flutter Development Skill
Teaches Claude Flutter best practices, widget patterns, state management conventions, and your team's coding style.
Frequently asked questions
What is a CLAUDE.md file and why do I need one?
CLAUDE.md is a special file that Claude Code reads at the start of every session. It tells Claude about your project — your tech stack, folder structure, coding conventions. Without it, Claude gives generic answers. With it, Claude gives answers specific to your project.
I don't use Claude Code — is CLAUDE.md useful for me?
CLAUDE.md is mainly for Claude Code users. If you use Claude.ai in the browser, you can still paste your project context at the start of each conversation — but you'll need to do it every time since Claude.ai doesn't remember between sessions.
How long should my CLAUDE.md be?
100-300 lines is ideal. Long enough to capture your key conventions, short enough that Claude reads it efficiently. Focus on: tech stack, folder structure, code style rules, things Claude should never do.
Can I use this prompt to update an existing CLAUDE.md?
Yes. Paste your existing CLAUDE.md into the conversation along with the prompt and ask Claude to improve it. It will keep what's working and fill in gaps.
Should every developer on my team have the same CLAUDE.md?
Yes — commit CLAUDE.md to your git repo so everyone gets it automatically. It lives in the project root alongside package.json.
Want more like this?
Browse the full RohanKit library — free resources for Claude and Cursor.