# Claude Code Project Memory Use this file as durable project memory for Claude Code. ## Project Context - Project type: Next.js - Tech stack: Next.js, TypeScript, React, CSS modules - Coding style: Prefer small components, explicit types, accessible UI, and existing project patterns. - AI tool target: CLAUDE.md ## Project Commands - Package manager: npm - Test: `npm test` - Build: `npm run build` - Lint: `npm run lint` ## Working Agreement - Read nearby files and reuse established project patterns. - Make small, reviewable changes. - Do not introduce new dependencies unless they clearly reduce complexity. - Keep user-facing text concise and accessible. - Preserve unrelated user changes in the working tree. ## Validation 1. Run `npm run lint` for style and static checks. 2. Run `npm test` for behavior. 3. Run `npm run build` before release or handoff. ## Extra Instructions Before handoff, summarize changed files and mention any checks that could not be run.
Use the CLAUDE.md generator to turn a repo tree, README notes, package scripts, and scattered project habits into a durable instruction file for Claude Code. The best output explains how to install the project, which commands validate changes, what coding patterns the agent should preserve, and what private context must stay out of the file.
What To Include In CLAUDE.md
A useful CLAUDE.md should focus on stable project context rather than temporary task notes. Include the stack, package manager, test commands, build commands, architecture boundaries, and review expectations.
Repo Tree And README To CLAUDE.md
Start from the files a new coding agent would inspect first: package.json, README, app or src folders, test directories, and deployment config. Summarize the structure into a short operating guide instead of pasting the whole tree.
Template And Examples
A practical CLAUDE.md template should include commands, repository map, coding style, validation expectations, MCP usage rules, and a short handoff format. Keep examples specific enough that Claude Code can reuse local patterns without reading every file first.
When To Regenerate The File
Regenerate or update the file when the repo changes package managers, adds a major framework, changes test commands, or introduces new rules for database, API, or frontend work.
FAQ
Should CLAUDE.md be committed?
Yes, if the instructions are useful for the whole team and do not contain secrets.
How long should CLAUDE.md be?
Keep it concise enough to scan, but specific enough to name commands, directories, and review expectations.
Can I generate CLAUDE.md from a README?
Yes. Use the README as source material, then add missing agent-specific details such as validation commands, forbidden shortcuts, and handoff expectations.
Is CLAUDE.md the same as local agent memory?
No. CLAUDE.md is reviewed repo guidance. Local memory tools such as PMB-style setups can store personal or evolving context outside the committed repo.