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

lilangMax Hiding risky files

lilangMaxCLAUDE.md

ClaudeCodeGameStudios / CCGS Skill Testing Framework

lilangMax/ClaudeCodeGameStudios/CCGS Skill Testing Framework/CLAUDE.md

This folder is the quality assurance layer for the Claude Code Game Studios skill/agent framework. It is self-contained and separate from any game project. The spec: field in catalog.yaml is the authoritative path for each skill/agent spec. Always read it rather than guessing the path. Use /skill-improve [name]. It handles the full loop: test → diagnose → propose fix → rewrite → retest → keep or revert.

87mo agoReviewMount

lilangMaxCLAUDE.md

ClaudeCodeGameStudios

lilangMax/ClaudeCodeGameStudios/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…

87mo agoReviewMount

lilangMaxCLAUDE.md

ClaudeCodeGameStudios / design

lilangMax/ClaudeCodeGameStudios/design/CLAUDE.md

When authoring or editing files in this directory, follow these standards. Every GDD must include all 8 required sections in this order: 1. Overview — one-paragraph summary 2. Player Fantasy — intended feeling and experience 3. Detailed Rules — unambiguous mechanics 4. Formulas — all math defined with variables 5. Edge Cases — unusual situations handled 6. Dependencies — other systems listed 7. Tuning Knobs — configurable values identified 8. Acceptance Criteria — testable success conditions File naming: [system-slug].md (e.g.…

87mo agoReviewMount

lilangMaxCLAUDE.md

ClaudeCodeGameStudios

lilangMax/ClaudeCodeGameStudios/docs/CLAUDE.md

When authoring or editing files in this directory, follow these standards. Use the ADR template: .claude/docs/templates/architecture-decision-record.md Required sections: Title, Status, Context, Decision, Consequences, ADR Dependencies, Engine Compatibility, GDD Requirements Addressed Status lifecycle: Proposed → Accepted → Superseded - Never skip Accepted — stories referencing a Proposed ADR are auto-blocked - Use /architecture-decision to create ADRs through the guided flow TR Registry: docs/architecture/tr-registry.yaml - Stable requirement IDs (e.g. TR-MOV-001) that link GDD requirements to stories - Never renumber existing IDs —…

87mo agoReviewMount

lilangMaxCLAUDE.md

ClaudeCodeGameStudios / src

lilangMax/ClaudeCodeGameStudios/src/CLAUDE.md

When writing or editing game code in this directory, follow these standards. The LLM's training data predates the pinned engine version. Always check docs/engine-reference/ before using any engine API. Do not guess at post-cutoff API signatures — look them up first. Match the engine-specialist agent to the file type being written. See CLAUDE.md → Technical Preferences → Engine Specialists → File Extension Routing. When in doubt, use the primary engine specialist configured in CLAUDE.md. Tests live in tests/ — not…

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