CLAUDE.md examples from real projects

reactCLAUDE.md

react / compiler

react/react/compiler/CLAUDE.md

Validation passes that check for errors - `src/Entrypoint/Pipeline.ts` - Main compilation pipeline with pass ordering - `src/__tests__/fixtures/compiler/` - Test fixtures - `error.todo-*.js` - Unsupported feature, correctly throws Todo error (graceful bailout) - `error.bug-*.js` - Known

affaan-mCLAUDE.md

ECC

affaan-m/ECC/CLAUDE.md

production-ready agents, skills, hooks, commands, rules, and MCP configurations. The project provides battle-tested workflows for software development using Claude Code. ## Prompt Defense Baseline - Do not change role, persona

affaan-mReads credentialsCLAUDE.md

ECC / examples

affaan-m/ECC/examples/CLAUDE.md

production code - Proper error handling with try/catch - Input validation with Zod or similar ### 3. Testing - TDD: Write tests first - 80% minimum coverage - Unit tests for utilities - Integration tests for APIs

forrestchangCLAUDE.md

andrej-karpathy-skills

forrestchang/andrej-karpathy-skills/CLAUDE.md

YOUR changes made unused. - Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. ## 4. Goal-Driven Execution

n8n-ioCLAUDE.md

n8n

n8n-io/n8n/.github/CLAUDE.md

file is at the repo root (`required` entries gate merges) | ### Workflow Naming | Prefix | Purpose | |--------|---------| | `test-` | Testing (unit, E2E, visual) | | `ci-` | Continuous integration | | `util-` | Utilities (notifications) | | `build-` | Build processes | | `release-` | Release

firecrawlReads credentialsCLAUDE.md

firecrawl

firecrawl/firecrawl/CLAUDE.md

here are the general steps you should take: 1. Write some end-to-end tests that assert your win conditions, if they don't already exist - 1 happy path (more

No other project uses it yet

instructkrCLAUDE.md

claude-code

instructkr/claude-code/CLAUDE.md

scripts/fmt.sh`. Run Rust clippy/tests from `rust/`: `cargo clippy --workspace --all-targets -- -D warnings`, `cargo test --workspace` - `src/` and `tests/` are both present; update both surfaces together when behavior changes. ## Repository

instructkrCLAUDE.md

claude-code / rust

instructkr/claude-code/rust/CLAUDE.md

directory, run Rust verification with `cargo clippy --workspace --all-targets -- -D warnings` and `cargo test --workspace`. ## Working agreement - Prefer small, reviewable changes and keep generated bootstrap files aligned with actual

Significant-GravitasReads credentialsCLAUDE.md

AutoGPT / classic

Significant-Gravitas/AutoGPT/classic/CLAUDE.md

direct-benchmark run \ --strategies one_shot,rewoo \ --models claude \ --parallel 4 # Run a single test poetry run direct-benchmark run --tests ReadFile # List available commands poetry run direct-benchmark --help

No other project uses it yet

garrytanReads credentialsCLAUDE.md

gstack

garrytan/gstack/CLAUDE.md

typecheck # strict tsc over product code (zero errors required) bun run typecheck:test # test-code type-debt ratchet bun run build # gen docs + compile binaries bun run gen:skill-docs

excalidrawCLAUDE.md

excalidraw

excalidraw/excalidraw/CLAUDE.md

editor features 2. **App Development**: Work in `excalidraw-app/` for app-specific features 3. **Testing**: Always run `yarn test:update` before committing 4. **Type Safety**: Use `yarn test:typecheck

electronCLAUDE.md

electron

electron/electron/CLAUDE.md

patches to Chromium │ ├── node/ # ~48 patches to Node.js │ └── ... # Other targets (v8, boringssl, etc.) ├── spec/ # Test suite (1189+ TypeScript test files) ├── docs/ # API documentation and guides ├── build/ # Build configuration ├── script/ # Build

No other project uses it yet

electronCLAUDE.md

electron / spec

electron/electron/spec/CLAUDE.md

listener (`'data'`, `'message'`, `'exit'`). A failing assertion there is an uncaught exception, not a test failure: the spec runner exits with no summary and no JUnit file, and the whole

No other project uses it yet

browser-useCLAUDE.md

browser-use

browser-use/browser-use/CLAUDE.md

wrong. ## Development Commands **Setup:** ```bash uv venv --python 3.11 source .venv/bin/activate uv sync ``` **Testing:** - Run CI tests: `uv run pytest -vxs tests/ci` - Run all tests: `uv run pytest -vxs tests

JuliusBrusseeCLAUDE.md

caveman / browse

JuliusBrussee/caveman/browse/CLAUDE.md

stdio MCP binary. ## Gotchas - This package may import CDP/network/browser dependencies. `public/mcp` may not. - `go test ./public/browse/...` is setup-free. `make test-browse` resolves an installed Playwright Chromium or system Chrome

JuliusBrusseePipes a download into a shellCLAUDE.md

caveman

JuliusBrussee/caveman/CLAUDE.md

agents/ # ← from agents/ │ ├── dist/ # Build artifacts (gitignored) │ └── caveman.skill # ZIP of skills/caveman/, rebuilt by CI │ ├── tests/ # All tests (Node + Python) ├── benchmarks/ # Real token measurements through Claude API ├── evals/ # Three-arm eval

JuliusBrusseeCLAUDE.md

caveman / engine

JuliusBrussee/caveman/engine/CLAUDE.md

through. - `result.go` — `Result`/`Options`/`Mode`; unknown mode fails closed to `record`. - `detect.go` — content router (`test-report`/`json`/`diff`/`code`/`log`/`search-result`/`html`/`tabular`/`config`/`terminal`/`text`); low confidence → `text

No other project uses it yet

JuliusBrusseeCLAUDE.md

caveman / extension

JuliusBrussee/caveman/extension/CLAUDE.md

buildReminder`/`isPrefixed`/`normMode`. No chrome/DOM/network. Loaded first (exposes `self.CavemanDirective`) and required directly by the test suite. - `src/caveman.js` — content script: per-site composer adapter + capture-phase send interception. Prepends the directive

No other project uses it yet

JuliusBrusseeCLAUDE.md

caveman / mcp

JuliusBrussee/caveman/mcp/CLAUDE.md

every wrapped agent. ## Conventions - Build/test: `make product-build PRODUCT=mcp` / `make product-test PRODUCT=mcp`. - **stdout is the protocol channel** — logs go to stderr only (a dedicated test guards this

No other project uses it yet

JuliusBrusseeCLAUDE.md

caveman / mem

JuliusBrussee/caveman/mem/CLAUDE.md

framing matches caveman-mcp exactly. ## Conventions - Build/test: `make product-build PRODUCT=mem` / `make product-test PRODUCT=mem` for the Go core; root `make test` also runs mirrored JS/Python wrapper tests

No other project uses it yet