How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
affaan-mCLAUDE.mdaffaan-m/ECC/CLAUDE.md
related files: | File(s) | Skill | |---------|-------| | `README.md` | `/readme` | | `.github/workflows/*.yml` | `/ci-workflow` | | `*.tsx`, `*.jsx`, `components/**` | `react-patterns`, `react-testing` — for React-specific work invoke `/react-review`, `/react-build`, `/react-test` | When spawning subagents, always pass
nextlevelbuilderCLAUDE.mdnextlevelbuilder/ui-ux-pro-max-skill/CLAUDE.md
Best practices and anti-patterns - `icons` - Icon recommendations with import code (Phosphor, Heroicons, Lucide) - `react` - React/Next.js performance patterns - `web` - App interface guidelines (iOS/Android/React Native) - `google-fonts` - Individual Google Fonts lookup
nextlevelbuilderCLAUDE.mdnextlevelbuilder/ui-ux-pro-max-skill/stack/CLAUDE.md
tells you the exact command form. - Optional: 21st.dev **Magic** MCP (`@21st-dev/magic`) generates React components from a prompt but needs an API key — see `docs/SETUP.md`. It is intentionally left
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.
