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

saffron-health

saffron-healthCLAUDE.md

libretto

saffron-health/libretto/CLAUDE.md

Never manually edit packages/libretto/package.json version. Use the release script: This bumps the version, updates all SKILL.md files, syncs mirrors, validates parity, commits, pushes a release-v* branch, and opens a PR. The release CI workflow triggers automatically when the PR merges to main. Temporarily set a pre-release version in packages/libretto/package.json and replace its workspace: and catalog: dependency ranges with published ranges. Then run: Approve npm's browser passkey prompt and verify the exact version installs in a clean project. Do not commit…

8833mo agoReviewMount

saffron-healthCLAUDE.md

libretto

saffron-health/libretto/docs/CLAUDE.md

See AGENTS.md for documentation-site conventions, including the rule that sidebar group headers must match the URL path segment.

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