How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
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.
AnthropicCLAUDE.mdanthropics/defending-code-reference-harness/CLAUDE.md
each topic are in `docs/`; targets are in `targets/` (canary is the fast smoke test). The rest of this file is the pipeline operator guide. --- # vuln-pipeline Execution-verified vulnerability
0xGFCLAUDE.md0xGF/boneyard/CLAUDE.md
filter boneyard-js run build # Build docs pnpm --filter boneyard-docs run build # Run tests pnpm --filter boneyard-js run test ``` ## Publishing Package is published to npm as `boneyard
Steady2 mentions in 2 weeks
No other project uses it yet
VanilagyCLAUDE.mdVanilagy/mediabunny/CLAUDE.md
core code is contained in src/, extensions are in packages/*/, website is in docs/ - Tests: Prefer fewer, longer test files over many small ones. Test files should be named after
No other project uses it yet
enso-orgCLAUDE.mdenso-org/enso/app/CLAUDE.md
this; don't run individual package `tsc` calls before their deps have emitted `dist/`. ## Testing - Unit tests: `vitest` (each package has its own config). - Integration tests: Playwright. GUI integration tests
Steady3 mentions in 2 weeks
No other project uses it yet
enso-orgCLAUDE.mdenso-org/enso/build_tools/CLAUDE.md
bazel) ./run --help # enumerate commands ./run ide build # top-level IDE target ./run backend test # test the engine bundle ``` `run.cmd` / `run.ps1` are the Windows equivalents. See `README.md` for the target/subcommand
Steady3 mentions in 2 weeks
No other project uses it yet
enso-orgCLAUDE.mdenso-org/enso/CLAUDE.md
distribution/lib/Standard/`. - `std-bits/` — Java helpers that the Enso standard library calls via host interop. - `test/` — Enso-language test projects (one per standard library module). - `tools/` — Auxiliary dev tools (IGV plugin
Steady3 mentions in 2 weeks
No other project uses it yet
enso-orgCLAUDE.mdenso-org/enso/distribution/CLAUDE.md
lib/Standard/ /0.0.0-dev/src/` (Enso) paired with matching helpers in `std-bits/ /`. Always run the matching `test/ _Tests` suite. ## Do not commit - Built artifacts (`dist/` at repo root is for outputs). - Pinned
Steady3 mentions in 2 weeks
No other project uses it yet
enso-orgCLAUDE.mdenso-org/enso/engine/CLAUDE.md
Jupyter kernel, REPL). - `runtime-parser/`, `runtime-parser-dsl/`, `runtime-parser-processor/`, `runtime-parser-processor-tests/` — Java bindings to the Rust parser and annotation-processor pipeline that builds them. - `runtime-compiler
Steady3 mentions in 2 weeks
No other project uses it yet
enso-orgCLAUDE.mdenso-org/enso/std-bits/CLAUDE.md
OpenCV-backed image helpers (pair with `lib/java/opencv-wrapper`). - `benchmarks/` — Benchmark harness helpers used by `engine/runtime-benchmarks/`. - `tests/` — Shared test utilities reused by `test/*_Tests`. ## How Enso calls it The standard library uses
Steady3 mentions in 2 weeks
No other project uses it yet
enso-orgCLAUDE.mdenso-org/enso/test/CLAUDE.md
test/ Enso-language test suites. Each subdir is an **Enso project** (has its own `package.yaml`) that exercises a specific standard-library module or cross-cutting concern. ## Layout One directory
Steady3 mentions in 2 weeks
No other project uses it yet
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
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 Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
