Where do I put the file?
Project root for project-wide rules. Place additional ones in subdirectories (e.g., src/CLAUDE.md) for module-specific rules — Claude Code merges them.
Generate a production-ready CLAUDE.md for your project in seconds. Stack-aware templates for Next.js, Python, Go, React Native, and more. Customize, copy, or download as a file. Save 30 minutes of setup per project.
# MyProject ## Stack - Next.js 15 App Router - TypeScript strict mode - Tailwind CSS - Prisma + PostgreSQL - Package manager: bun ## Rules - Run `bun run typecheck` after every code change - Use server components by default; mark client components with 'use client' only when needed - API routes go in app/api/*; use Route Handlers, not Pages API - Database access only from server components or API routes - Conventional commits for messages (feat:, fix:, chore:, docs:) ## Forbidden patterns - No `any` type - No `@ts-ignore` without an inline comment explaining why - No `useEffect` for data fetching — use Server Components or React Query - No raw SQL except in well-scoped repository functions ## Build & test ```bash # Build bun run build # Test bun run test ``` ## Session start checklist 1. `git status && git log --oneline -5` — see current state 2. Read relevant CLAUDE.md (this file) and any nested ones 3. Identify the smallest task that moves the goal forward ## Session end checklist 1. Commit changes (`git commit`) 2. Note next action in TODOS.md or plan file 3. Verify deployed environment if shipped ## Plan mode preference For non-trivial features, propose 2-3 approaches with trade-offs (complexity, perf, future flexibility) before writing code. Wait for explicit approval. ## Notes - This CLAUDE.md was scaffolded at https://claudeguide.io/claude-md-generator - Customize freely — Claude reads this on every session
300개의 검증된 Claude Code 프롬프트 + slash command 템플릿이 필요하다면:
Power Prompts 300 — ₩38,000 →생성된 CLAUDE.md를 프로젝트 루트에 저장하면 Claude Code가 매 세션 시작 시 자동으로 읽습니다. 하위 디렉토리(예: src/CLAUDE.md)에 두면 해당 디렉토리에서만 적용 / 병합됩니다.
CLAUDE.md is a project-specific instructions file Claude Code reads at the start of every session. Think of it as a persistent system prompt that lives in your repo and gets merged with your team's shared context. Without one, Claude re-discovers your stack every session. With one, every session knows your build commands, naming conventions, forbidden patterns, and architectural constraints from the start.
For deeper guidance, see CLAUDE.md effective patterns and Claude Code memory system.
Project root for project-wide rules. Place additional ones in subdirectories (e.g., src/CLAUDE.md) for module-specific rules — Claude Code merges them.
CLAUDE.md is automatic — Claude Code reads it without you pasting it. It's also project-versioned (commit it to git) so the whole team shares the same context.
Never. CLAUDE.md gets committed to git. Use .env for secrets and reference them by name (e.g., "DATABASE_URL is set in .env.local").
Under 100 lines. Long CLAUDE.md files burn context window on every session. Use nested CLAUDE.md files for module-specific rules rather than one giant file.
A good CLAUDE.md sets the rules. Power Prompts 300 gives you 300 production-tested prompts to actually USE — debugging, refactoring, testing, architecture, security. Plus 40 slash command templates and JSONL for direct Claude Code import.
Get Power Prompts 300 — $29 / ₩38,000 →Get more Claude Code patterns weekly
CLAUDE.md examples, slash commands, MCP picks. Korean and English.
No spam. Unsubscribe any time.