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

GitHub 100k+ stars Hiding risky files

GitHubCLAUDE.md

spec-kit / integrations

github/spec-kit/docs/integrations/claude.md

Install Claude Code before setup. The integration key is claude. This integration is declared multi-install safe. See the shared multi-install rules. For an existing Spec Kit project, use specify integration install claude. See integration management for activation, upgrades, and removal. Skills are installed as .claude/skills/speckit-<command>/SKILL.md. Invoke them in Claude's chat, for example /speckit-specify or /speckit-bug-assess for the installed bug extension. By default every Spec Kit skill installed for Claude Code is model-invocable, so its description is always in Claude's context…

Steady+42 stars this week

No other project uses it yet

149k12d 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.