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

CoralGame Hiding risky files

CoralGameCLAUDE.md

Claude-Code-Game-Studios

CoralGame/Claude-Code-Game-Studios/CLAUDE.md

Indie game development managed through 48 coordinated Claude Code subagents. Each agent owns a specific domain, enforcing separation of concerns and quality. Note: Engine-specialist agents exist for Godot, Unity, and Unreal with dedicated sub-specialists. Use the set matching your engine. @.claude/docs/directory-structure.md @docs/engine-reference/godot/VERSION.md @.claude/docs/technical-preferences.md @.claude/docs/coordination-rules.md User-driven collaboration, not autonomous execution. Every task follows: Question -> Options -> Decision -> Draft -> Approval See docs/COLLABORATIVE-DESIGN-PRINCIPLE.md for full protocol and examples. First session? If the project has no engine configured and no game…

197mo 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.