CLAUDE.md examples from real projects

phanCLAUDE.md

phan

phan/phan/CLAUDE.md

file paths in `.expected` files - **Line numbers**: Critical for matching expected warnings to actual code lines - **Issue types**: Must match exactly (e.g., `PhanTypeInvalidCallableMethodName`) - **Error messages**: Complete message text must match

No other project uses it yet

weave-osCLAUDE.md

router

weave-os/router/CLAUDE.md

write. - **Non-tautological tests** — every test must assert behavior that breaks if prod code deleted. ## Layer model and import rules Three concentric layers. Imports flow inward only. ``` +-------------------------------------------------------------------+ | cmd/router/main.go (composition root

aaddrickDeletes or force-pushesCLAUDE.md

claude-desktop-debian

aaddrick/claude-desktop-debian/CLAUDE.md

summary and link to the PR ### Investigating Issues For older issues, review the state of the code when the issue was raised - it may have already been addressed: ```bash

unkeyedCLAUDE.md

unkey

unkeyed/unkey/CLAUDE.md

reasoning from the code alone. - When debugging a failure, start from the incident or issue Polylane recorded: it carries the evidence an investigation already gathered. - Polylane reviews pull requests

SaladDayReads credentialsCLAUDE.md

cc-switch-cli

SaladDay/cc-switch-cli/CLAUDE.md

issues. - Validate every finding against the code. Make minimal fixes for confirmed issues within scope, run the relevant checks, then start another blind review with a new subagent under

No other project uses it yet

CloudflareCLAUDE.md

vibesdk

cloudflare/vibesdk/CLAUDE.md

this repository. ## Communication Style - Be professional, concise, and direct - Do NOT use emojis in code reviews, changelogs, or any generated content. You may use professional visual indicators or favor markdown

breaking-brakeCLAUDE.md

cc-wf-studio

breaking-brake/cc-wf-studio/CLAUDE.md

becomes the CHANGELOG entry) ``` This writes a `.changeset/ .md` file — commit it alongside your code. **You never hand-edit `CHANGELOG.md`; Changesets generates it.** If a PR genuinely needs no release

No other project uses it yet

lukevellaReads credentialsCLAUDE.md

rallly

lukevella/rallly/CLAUDE.md

spaces?") — `features/instance-policy/` (`deriveInstancePolicy` in `utils.ts` is the inventory; `getInstancePolicy` from `data.ts` for server code, `loadInstancePolicy` from `loaders.ts` for pages, `useInstancePolicy` from `client.tsx`). When the organization layer lands this becomes

No other project uses it yet

streamyfinCLAUDE.md

streamyfin

streamyfin/streamyfin/CLAUDE.md

writing code in that area. | Document | Read it when | | --- | --- | | [docs/conventions/constants.md](docs/conventions/constants.md) | Adding a threshold, interval, ratio, storage key, or any value used twice | | [docs/conventions/contributing-flow.md](docs/conventions/contributing-flow.md) | Opening, describing, or reviewing

entireioCLAUDE.md

cli

entireio/cli/CLAUDE.md

protocol](docs/architecture/external-agent-protocol.md) | | Security, privacy, scanners | [Security and privacy](docs/security-and-privacy.md), [implementation contracts](docs/development/checkpoint-implementation.md) | | Review command | [Review architecture](docs/architecture/review-command.md) | | Release artifacts, install scripts, version-check origins | [Release origins](docs/architecture/release-origins.md) | | E2E tests

No other project uses it yet

umbracoCLAUDE.md

Umbraco-CMS

umbraco/Umbraco-CMS/CLAUDE.md

dotnet format) - No build warnings - **Merge Strategy**: Squash and merge (via GitHub UI) - **Reviews**: Required from code owners #### PR Naming Convention Use the format: `Area: Description (closes #IssueID)` **Examples**: | Area

InternLMCLAUDE.md

xtuner

InternLM/xtuner/.claude/CLAUDE.md

requesting review. 3. Resolve all review comments before merging — do not dismiss without explanation. --- ## Code Review Standards ### What to Check 1. **Correctness**: Does the code do what it claims

Jeric-XCLAUDE.md

SyncClipboard

Jeric-X/SyncClipboard/CLAUDE.md

operations; categories alone do not skip tests when running the full suite locally. ### Code Style ```bash # Check formatting (from src/ directory) dotnet format --verify-no-changes --severity info --no-restore

tixl3dCLAUDE.md

tixl

tixl3d/tixl/.claude/CLAUDE.md

turn of the current conversation, you may skip; across sessions, always re-read. - `.agentic/AGENT_INSTRUCTIONS.md` -- coding conventions, performance rules, operator guidelines, style and formatting. - `.agentic/SOLUTION_OVERVIEW.md` -- architecture map, dependency flow, task-oriented

No other project uses it yet

pytorchCLAUDE.md

executorch

pytorch/executorch/CLAUDE.md

bullet lists of changes; explain review order for large PRs, or omit for small ones - Disclose PR was authored with AI, include tool name. ## Code Style - Minimal comments; code should

No other project uses it yet

rstudioCLAUDE.md

rstudio

rstudio/rstudio/.claude/CLAUDE.md

spanning open-source and pro-only code is made in rstudio-pro first: the whole change is opened as a PR there, reviewed, and approved, but not merged. An "open

clideyCLAUDE.md

whodb

clidey/whodb/CLAUDE.md

AGENTS.md ## Claude Code - Use plan mode for multi-file, risky, architectural, or ambiguous changes. - Use subagents only for bounded sidecar work: exploration, review, test triage, or documentation lookup. - Prefer separate

No other project uses it yet

langwatchReads credentialsCLAUDE.md

langwatch

langwatch/langwatch/CLAUDE.md

secret**; values resolve through `@langwatch/secrets` (ADR-132) and `haven env` masks them. Module code never reads `process.env`. ## Git and GitHub - Other changes in the checkout belong to someone else. Stage

No other project uses it yet

pdfmeDeletes or force-pushesCLAUDE.md

pdfme

pdfme/pdfme/CLAUDE.md

snapshots if UI changes are intentional: `npm run test -w packages/ui -- -u` 4. **Claude Code Review After PR Creation**: - After creating a PR, run `npm run claude:review` - The command

No other project uses it yet

campfireinReads credentialsCLAUDE.md

byterover-cli

campfirein/byterover-cli/CLAUDE.md

mocking must be implemented. **Feature Development (Outside-In Approach — applies to ALL work: planning, reviewing, coding, and auditing)**: - This is a foundational principle, not just a coding guideline. Apply