Claude Md Examples

CLAUDE.md Examples

n[](https://github.com/Samarth0211/claude-md-examples) [](https://clskills.in)

Real-world CLAUDE.md files for popular tech stacks. Drop any of these into your project root and Claude Code instantly understands your codebase.

**Generate a custom CLAUDE.md for YOUR project (free): [clskills.in/claude-md-generator](https://clskills.in/claude-md-generator)**

What is CLAUDE.md?

A `CLAUDE.md` file tells Claude Code how to work with your specific project — your commands, conventions, architecture, and rules. Without it, Claude guesses. With it, Claude follows your exact standards.

Examples

Next.js + TypeScript + Tailwind

# Project: My SaaS App

## Commands
- `npm run dev` — start development server
- `npm run build` — production build
- `npm test` — run tests with Vitest
- `npm run lint` — ESLint + Prettier check

## Architecture
- `/src/app` — Next.js App Router pages
- `/src/components` — React components (PascalCase)
- `/src/lib` — Utilities and helpers
- `/src/hooks` — Custom React hooks (use* prefix)
- `/prisma` — Database schema and migrations

## Code Style
- TypeScript strict mode, no `any` types
- Functional components only, no class components
- Use Zustand for state management, not Redux
- Tailwind CSS for styling, no CSS modules
- Named exports, not default exports (except pages)

## Conventions
- Components: PascalCase (e.g., `UserProfile.tsx`)
- Hooks: camelCase with `use` prefix (e.g., `useAuth.ts`)
- Utils: camelCase (e.g., `formatDate.ts`)
- API routes: kebab-case (e.g., `/api/user-profile`)

## Testing
- Vitest for unit tests, Playwright for E2E
- Test files: `*.test.ts` co-located with source
- Mock external APIs, never hit real endpoints in tests

## Do NOT
- Don't add comments to obvious code
- Don't use `var`, always