How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
nextlevelbuilderCLAUDE.mdnextlevelbuilder/ui-ux-pro-max-skill/stack/CLAUDE.md
source of truth for tokens (color, type, spacing). 2. **COMMIT to an aesthetic — `frontend-design`.** Do not sample the safe center of the training distribution. Answer four questions first — *purpose
Steady13 mentions in 2 weeks
1 project uses a version of this
addyosmaniCLAUDE.mdaddyosmani/agent-skills/CLAUDE.md
Build:** incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, frontend-ui-engineering, api-and-interface-design **Verify:** browser-testing-with-devtools, debugging-and-error-recovery
Steady37 mentions in 2 weeks
1 project uses a version of this
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
