# CLAUDE.md — Starter Template

Drop this in your project root. Claude Code reads it every time it starts a session.

The point: Claude shouldn't have to guess your conventions. Tell it what you care about. Delete sections that don't apply to your project.

## Project Overview

- **Name:** [your-project-name]
- **Type:** [web app | CLI tool | library | API | mobile app]
- **Stack:** [e.g., Next.js 14, TypeScript, PostgreSQL, Tailwind]

## Architecture

```
src/
├── app/          # [describe what lives here]
├── lib/          # Business logic, utilities
├── types/        # Type definitions
└── tests/        # Mirror src/ structure
```

## Commands

```bash
npm run dev          # Start dev server
npm run build        # Production build
npm run test         # Run all tests
npm run lint         # Lint check
```

## Code Style

Put your actual rules here. Not "follow best practices." Real rules like:

- Use named exports, not default exports
- All functions get return types
- No `any` — use `unknown` or write a proper type
- Components go in PascalCase, utilities in camelCase

## Don't Touch

List files that should never be auto-edited:

- `.env` files
- `package-lock.json`
- Database migrations
- That one config file that breaks everything if you look at it wrong

---

**The premium version** adds: architecture patterns, testing conventions, a gotchas section (things that bite new contributors), CI/CD integration rules, and 10+ more sections. [Get it here →](#)