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.
MicrosoftCLAUDE.mdmicrosoft/bobpgdemos/caldovalogistics/demo4-foundry-agent/caldova-logistics-agent/CLAUDE.md
This project uses AGENTS.md as the single source of truth for coding agent instructions. The import below loads it into Claude Code's context.
MicrosoftCLAUDE.mdmicrosoft/m365-copilot-studio-what-to-build-where/CLAUDE.md
Static Astro + strict TypeScript. Read README.md before source changes. Use npm run check, npm test, and targeted Playwright tests. Do not publish or create a GitHub repository without the user's request. This is a folder-backed app session with a local Git repository. - State guidance and caveats directly. Avoid rhetorical "this is X, not Y" phrasing; retain explicit factual limitations where they affect a decision. - Use informative, formal headings and labels. Avoid slogans, clever phrasing, and marketing-style copy…
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.
