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

PaulKinlan

PaulKinlanCLAUDE.md

Co-do

PaulKinlan/Co-do/CLAUDE.md

Guidance for Claude Code working in this repository. Co-do is a Cowork-like browser experience using the File System Access API for collaborative coding with native filesystem integration. IMPORTANT: Always run npm test after code changes. Tests must pass before committing. Exception: Not required for documentation-only changes (.md files, comments). IMPORTANT: Never modify version in package.json. Version bumping is automatic via GitHub Action on PR merge. Target: Latest Chrome (Chrome 140+) — File System Access API is the core dependency.

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