🧠 Make Claude 10x Smarter in 60 Seconds

Drop this into your repo and Claude instantly understands your stack, rules, and conventions.

No more re-explaining your project every session.

What is CLAUDE.md?

CLAUDE.md is a project memory file that lives in your repository root.

Every time you start a Claude Code session, Claude reads this file first — giving it instant context about:

• Your tech stack
• Your coding conventions
• Your project structure
• Your rules

Think of it as onboarding documentation for your AI coding partner.

📂 Where To Place It

💡 Pro Tip: You can have multiple CLAUDE.md files.

Claude reads all relevant ones depending on which directory you're working in.

📋 The Template

Copy everything below and customize it for your project:

# CLAUDE.md

## Project Overview
This is [PROJECT NAME], a [brief description of what it does].
Built with [primary tech stack].

## Tech Stack
- Language: [e.g., TypeScript, Python, Go]
- Framework: [e.g., Next.js, FastAPI, Express]
- Database: [e.g., PostgreSQL, MongoDB, Supabase]
- Styling: [e.g., Tailwind CSS, styled-components]
- Testing: [e.g., Jest, Pytest, Vitest]
- Package Manager: [e.g., npm, pnpm, bun, uv]

## Project Structure
- src/ — Main application source code
- src/components/ — Reusable UI components
- src/lib/ — Utility functions and shared logic
- src/api/ — API routes and handlers
- tests/ — Test files
- docs/ — Documentation

## Commands
- Dev server: npm run dev
- Build: npm run build
- Test: npm test
- Lint: npm run lint
- Type check: npx tsc --noEmit

## Code Conventions
- Use [functional components / class-based] approach
- Prefer [named exports / default exports]
- File naming: [kebab-case / camelCase / PascalCase]
- Use [single quotes / double quotes] for strings

## Important Patterns
- Error handling: [describe your approach]
- State management: [describe your approach]
- API calls: [describe your approach]
- Authentication: [describe your approach]

## Things To Avoid
- Never modify [specific files or directories]
- Don't use [deprecated patterns or libraries]
- Avoid [anything specific to your project]

## Additional Context
- [Links to relevant docs]
- [Known issues or quirks]
- [Deployment process notes]