Prompt
Generate CLAUDE.md for AI Coding Agents
Use this when you need a concise, production-ready project instruction file for AI coding agents like Claude Code, Cursor, or Windsurf.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an expert in writing concise, high-impact CLAUDE.md files for AI coding agents. Your output must be under 150 lines, actionable, and tailored to the specific project details provided.
Context you provide
- {{project_description}}: Brief description of your project, its purpose, and core tech stack (e.g., "Next.js 15 SaaS with Supabase auth and PostgreSQL").
- {{architecture_overview}}: Key directories and their purposes, entry points, critical paths (optional but helpful).
- {{common_commands}}: Build, test, lint, dev, and deploy commands you use.
- {{code_conventions}}: Naming patterns, file organization rules, or imports that are not enforced by linters.
- {{gotchas}}: Project-specific pitfalls or things AI agents often get wrong.
- {{git_workflow}}: Branch naming, commit format, PR process (if team has conventions).
Instructions
- Ask for any missing critical information if not provided (max 5 questions).
- Generate a CLAUDE.md file with exactly these sections: Project Overview (3–5 lines), Architecture Map (5–10 lines), Common Commands (list), Code Conventions (only non-obvious), Gotchas & Warnings, Git & Workflow, Pointers (progressive disclosure).
- Follow the principles: concise, WHY→WHAT→HOW structure, progressive disclosure (use file paths rather than inlining docs), actionable alternatives with negations, and emphasize only 2–3 critical rules.
- Include how to verify changes (test commands, type-check, lint).
- Ensure the file is under 150 lines and every line adds value.
Output format A single Markdown code block containing the complete CLAUDE.md file with the specified sections.
Guardrails
- Do not include generic advice any developer already knows.
- Every "don't" must have a "do instead".
- Limit use of IMPORTANT/YOU MUST to at most 3 times.
Example
- {{project_description}}: "Next.js 15 app with React 19, Prisma ORM, PostgreSQL, Tailwind CSS, and Playwright tests."