CLAUDE.md examples from real projects

How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.

Your trail

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.

Worked for most · soon

Microsoft Azure 1k+ stars

Microsoft AzureCLAUDE.md

Azure-Sentinel

Azure/Azure-Sentinel/CLAUDE.md

For Microsoft Sentinel-to-Defender-XDR migration or authoring work, first read: Tools\SentinelToXDRMigration\agent-workflows\end-to-end-migration.md Follow that canonical workflow and use the repository CLI and PowerShell entry points directly. Do not replace deterministic conversion, validation, packaging, deployment, or parity logic with model-generated approximations. Default to authoring. Ask before optional lab qualification; it is not required for ISV publishing. Use V3.1 through package-v3-1 for Sentinel and XDR solution packages. Resume from workflow-state.json, preserve disabled detections, and request explicit approval before writes.

6.2k16d agoReviewMount

CLAUDE.md vs AGENTS.md

About CLAUDE.md

What is CLAUDE.md?

A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.

Where does it go?

At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.

What should it contain?

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.md or AGENTS.md?

Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.