CLAUDE.md
CLAUDE.md for Next.js
CLAUDE.md is the project memory file Claude Code reads from the repository root. It is the right place for stack rules you do not want to repeat in every chat. This copy is written for a Next.js project. This repository is a Next.js app on the App Router with TypeScript. Server Components are the default. Add a client component only for state, effects, or browser APIs.
The example uses a balanced, readable style, pragmatic tests, and comments only where the intent is not obvious. Open the generator to make the agent stricter, switch to test-first, quiet the comments, or pick a different file.
The example assumes the App Router, TypeScript, and React Server Components. It does not assume the Pages Router, a database, or an auth library. If the repo already picked one, follow that instead of adding a second.
Example file
Balanced strictness, readable style, pragmatic tests. Download name: CLAUDE.md
# CLAUDE.md
Project memory for Claude Code in this Next.js repository. Read it before editing. Other agents can follow the same rules.
## Stack
This repository is a Next.js app on the App Router with TypeScript. Server Components are the default. Add a client component only for state, effects, or browser APIs.
## Layout
- Routes, layouts, and server code live in `app/`.
- Shared UI lives in `components/`. Shared logic lives in `lib/`.
- Keep route files thin. Move non-trivial logic into functions that can be tested without rendering a page.
## Commands
- Dev server: `npm run dev`
- Production build: `npm run build`
- Lint: `npm run lint`
- Tests: `npm test`
Use the script the repo already defines when it differs from the command above.
## Conventions
- Fetch data on the server. Do not fetch in `useEffect` for data the server can already load.
- Use `next/link`, `next/image`, and `next/font`. Do not add another image or font pipeline.
- Mutations go through the Server Actions or route handlers the repo already uses.
- Validate input at the boundary with the validator the repo already uses.
- Keep client components small and at the leaves of the tree.
- Match the existing styling system. Do not introduce a second CSS framework.
## Testing
Add or update tests when behavior changes.
Use the runner already in the repo (Vitest, Jest, or Playwright). Cover the behavior you changed, not every component.
## Style
- Optimize for the next reader over the shortest diff.
- Comment only when the why is non-obvious.
- Name things the way neighboring files already do.
- Do not reformat code you did not change.
## Errors
- Fail at the boundary. Do not swallow errors.
- Return a clear error from server actions and route handlers. Do not send stack traces to the client.
## Scope
- Do the requested task. Do not refactor unrelated code.
- Match the rigor already in the repo. Fix what you touch.
- Ask one clarifying question only when the task cannot be finished without it. Otherwise state the assumption and continue.
## Avoid
- Do not import server-only modules into a client component.
- Do not put secrets in `NEXT_PUBLIC_` variables or client bundles.
- Do not mark a whole tree as a client component to silence one hook error.
- Do not add `pages/` routes to an App Router project.
## Done when
- The requested behavior works.
- `npm run lint` and `npm test` pass, or you name the command you could not run.
- The diff stays inside the task.
- You list anything you could not run.
Add it to the project
01
Copy a starting file
Copy the example CLAUDE.md on this page, or open the generator if you want different testing, strictness, or comment rules.
02
Save it at CLAUDE.md
Save it as `CLAUDE.md` at the root of the Next.js repo. Claude Code loads it when a session starts. A nested CLAUDE.md applies to that directory.
03
Start a fresh agent session
Rules files are read when a session starts. A chat that is already open may still be using the old instructions.
04
Give it one small task
Ask for one change a Next.js agent often gets wrong, such as a page that loads data on the server instead of in useEffect. If it ignores the file, confirm the path and start a new session.
Questions about this file
Where do I put CLAUDE.md in a Next.js repo?
Save it as `CLAUDE.md` at the root of the Next.js repo. Claude Code loads it when a session starts. A nested CLAUDE.md applies to that directory.
Which tools read this CLAUDE.md?
Claude Code reads CLAUDE.md as project memory. Other agents can follow the same markdown if you point them at it, but Claude Code is the tool that loads it automatically.
What does the Next.js example assume?
The example assumes the App Router, TypeScript, and React Server Components. It does not assume the Pages Router, a database, or an auth library. If the repo already picked one, follow that instead of adding a second.
Does VibeSpell upload my repository?
No. Recipe pages are static, and the generator builds the file in your browser from the options you pick. Your source code never leaves the machine.
Other files for Next.js
Cursor rules
.cursor/rules/project.mdc
AGENTS.md
AGENTS.md
system prompt
system-prompt.md
Copilot instructions
.github/copilot-instructions.md
Windsurf rules
.windsurf/rules/project.md
Cline rules
.clinerules
GEMINI.md
GEMINI.md
Cursor testing rule
.cursor/rules/testing.mdc
Cursor security rule
.cursor/rules/security.mdc
CLAUDE.md for other stacks
- CLAUDE.md for React
- CLAUDE.md for Vue
- CLAUDE.md for SvelteKit
- CLAUDE.md for Node.js
- CLAUDE.md for FastAPI
- CLAUDE.md for Django
- CLAUDE.md for Go
- CLAUDE.md for Rust
- CLAUDE.md for Unity
- CLAUDE.md for Godot
- CLAUDE.md for Laravel
- CLAUDE.md for Rails
- CLAUDE.md for Flutter
- CLAUDE.md for Swift
- CLAUDE.md for Kotlin
- CLAUDE.md for Unreal
- CLAUDE.md for Next.js + Supabase
- CLAUDE.md for T3
- CLAUDE.md for Astro
- CLAUDE.md for Remix
- CLAUDE.md for Nuxt
- CLAUDE.md for Electron
- CLAUDE.md for Tauri
- CLAUDE.md for Expo
- CLAUDE.md for Spring Boot
- CLAUDE.md for .NET
- CLAUDE.md for Phaser
- CLAUDE.md for Bevy
- CLAUDE.md for Roblox
- CLAUDE.md for Python ML
- CLAUDE.md for LangChain