CLAUDE.md examples from real projects

alirezarezvaniCLAUDE.md

claude-skills / templates

alirezarezvani/claude-skills/templates/CLAUDE.md

agents/domain/cs-new-agent.md # 2. Customize for your agent vim agents/domain/cs-new-agent.md # 3. Follow template structure exactly # 4. Test relative paths and integrations # 5. Commit with conventional commit git commit -m "feat(agents): implement

swagger-apiCLAUDE.md

swagger-ui

swagger-api/swagger-ui/CLAUDE.md

Architecture](#project-architecture) 3. [Development Setup](#development-setup) 4. [Build System](#build-system) 5. [Testing Infrastructure](#testing-infrastructure) 6. [Code Style & Conventions](#code-style--conventions) 7. [Git Workflow](#git-workflow

jarrodwattsCLAUDE.md

claude-hud

jarrodwatts/claude-hud/CLAUDE.md

lines for tools, agents, todos, and more. ## Commands ```bash npm ci npm test # builds dist/, then runs node --test npm run test:update-snapshots # regenerate tests/golden/expected.txt after an intended output

srbhrCLAUDE.md

Resume-Matcher

srbhr/Resume-Matcher/.claude/CLAUDE.md

Backend (from repo root) cd apps/backend uv sync --extra dev # Install Python deps (incl. test deps) uv run uvicorn app.main:app --reload --port 8000 # FastAPI on :8000 uv run pytest

No other project uses it yet

manaflow-aiCLAUDE.md

cmux

manaflow-ai/cmux/CLAUDE.md

regression before its fix; record the same focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)). A bug-fix PR body names that command, its failure

No other project uses it yet

mlflowCLAUDE.md

mlflow

mlflow/mlflow/CLAUDE.md

level imports (only use lazy imports when necessary) - Only add docstrings in tests when they provide additional context - Only add comments that explain non-obvious logic or provide additional context

BudibaseReads credentialsCLAUDE.md

budibase

Budibase/budibase/CLAUDE.md

Build/Test Commands - Build: `yarn build` - Lint: `yarn lint` (check) or `yarn lint:fix` (fix) - Test: `yarn test ` run inside of a packages/\* directory - Type check: `yarn check:types` - packages/server tests

No other project uses it yet

eyaltoledanoCLAUDE.md

claude-task-master

eyaltoledano/claude-task-master/CLAUDE.md

commands and guidelines, treat as if import is in the main CLAUDE.md file.** @./.taskmaster/CLAUDE.md ## Test Guidelines ### Test File Placement - **Package & tests**: Place in `packages/ /src/ / .spec.ts` or `apps/ /src/ / ` alongside

No other project uses it yet

eyaltoledanoReads credentialsCLAUDE.md

claude-task-master

eyaltoledano/claude-task-master/.taskmaster/CLAUDE.md

multiple Claude Code sessions: ```bash # Terminal 1: Main implementation cd project && claude # Terminal 2: Testing and validation cd project-test-worktree && claude # Terminal 3: Documentation updates cd project-docs-worktree

No other project uses it yet

phurynCLAUDE.md

pm-skills

phuryn/pm-skills/CLAUDE.md

Claude agents) ├── CONTRIBUTING.md <- contributor guidelines ├── README.md <- public documentation (GitHub) ├── LICENSE <- MIT ├── validate_plugins.py <- plugin validator ├── tests/ <- unit + docs-consistency tests (unittest) └── pm-{name}/ <- 9 plugin directories ├── .claude-plugin/plugin.json <- per-plugin

DonchitosCLAUDE.md

Claude-Code-Game-Studios / src

Donchitos/Claude-Code-Game-Studios/src/CLAUDE.md

specialists` block of `project.yaml`. When in doubt, use `specialists.code` from `project.yaml`. ## Tests Tests live in `tests/` — not in `src/`. Run `/test-setup` to scaffold the test framework if it doesn

DonchitosCLAUDE.md

Claude-Code-Game-Studios / studio-tests

Donchitos/Claude-Code-Game-Studios/studio-tests/CLAUDE.md

Studio Tests — Claude Instructions 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

No other project uses it yet

OpenZeppelinCLAUDE.md

openzeppelin-contracts

OpenZeppelin/openzeppelin-contracts/CLAUDE.md

source. Subdirectory layout (`token/ERC20/`, `access/`, `utils/`, …) mirrors the public API. | | `contracts/mocks/` | Mocks used by tests. Mirrors `contracts/`. Manual mocks only — see the `testing` skill. | | `contracts/interfaces/` | ERC interfaces in their pristine

OI-wikiReads credentialsCLAUDE.md

OI-wiki

OI-wiki/OI-wiki/CLAUDE.md

corresponding `images/` directories 3. Run format checking: `yarn run docs:format:check` 4. Test locally: `uv run mkdocs serve` 5. Build and verify: `uv run mkdocs build` ### Adding New Topics

No other project uses it yet

onlook-devReads credentialsCLAUDE.md

onlook

onlook-dev/onlook/CLAUDE.md

large assets. - Propose minimal diffs aligned with existing conventions; avoid wide refactors. ### Notes - Unit tests can be run with `bun test` - Run type checking with `bun run typecheck` - Apply database

No other project uses it yet

humanlayerCLAUDE.md

12-factor-agents

humanlayer/12-factor-agents/CLAUDE.md

This project uses: - **Language/Framework**: [Add your stack here] - **Build Tool**: [Add your build commands] - **Testing**: [Add your test commands] - **Architecture**: [Describe your project structure] ## Core Principles (All Personas) 1. **READ

No other project uses it yet

anomalycoCLAUDE.md

sst

anomalyco/sst/CLAUDE.md

build:cli` - **Run CLI locally**: `cd examples/ && go run ../../cmd/sst ` - **Go tests**: `bun run test:cli` - **Typecheck**: `bun run typecheck` - **Generate docs**: `bun run docs:generate` - **Run docs locally

apifyCLAUDE.md

crawlee

apify/crawlee/.claude/CLAUDE.md

PATH issues in this environment. ## Pre-Commit Checks Always run `pnpm tsc-check-tests` (or the project's type-check command) before committing any TypeScript changes. Never assume type safety

No other project uses it yet

VoltAgentCLAUDE.md

awesome-claude-code-subagents

VoltAgent/awesome-claude-code-subagents/CLAUDE.md

Language/framework experts (TypeScript, Python, etc.) 03-infrastructure/ # DevOps, cloud, Kubernetes, etc. 04-quality-security/ # Testing, security auditing, code review 05-data-ai/ # ML, data engineering, AI specialists 06-developer-experience

homebridgeCLAUDE.md

homebridge

homebridge/homebridge/CLAUDE.md

/bin/homebridge.js -D -P example-plugins/` (expects an `example-plugins/` checkout next to plugins under test). - `npm run lint` / `npm run lint:fix` — ESLint via `@antfu/eslint-config` (flat config in `eslint.config.js

No other project uses it yet