CLAUDE.md examples from real projects

rust-langCLAUDE.md

rust-analyzer

rust-lang/rust-analyzer/CLAUDE.md

required by the policy. ## Repository Guides - Architecture and crate ownership: `docs/book/src/contributing/architecture.md` - Rust style: `docs/book/src/contributing/style.md` - Testing conventions and fixture syntax: `docs/book/src/contributing/testing.md` - Contributor workflows: `docs/book/src/contributing/README.md` - AI restrictions: `AI_POLICY.md` Read the relevant sections

No other project uses it yet

weaviateCLAUDE.md

weaviate

weaviate/weaviate/CLAUDE.md

ways: 1. **Reproduce and fix it**, with a regression test that fails without the fix and passes with it. 2. **Reproduce it, commit a failing (red) test that pins

No other project uses it yet

diegomuraCLAUDE.md

react-pdf

diegomura/react-pdf/CLAUDE.md

packages (lerna run build) yarn watch # Watch mode - rebuilds on changes (for development) yarn test # Run all tests (vitest) yarn test packages/layout # Run tests for a specific package yarn lint

No other project uses it yet

Olow304CLAUDE.md

memvid

Olow304/memvid/CLAUDE.md

HNSW) │ ├────────────────────────────┤ │ Time Index │ ├────────────────────────────┤ │ TOC (Footer) │ └────────────────────────────┘ ``` ## Development Commands ```bash # Build cargo build cargo build --release # Test cargo test cargo test --test lifecycle cargo test -- --nocapture # Lint cargo clippy cargo

dagster-ioCLAUDE.md

dagster

dagster-io/dagster/CLAUDE.md

Type checking (slow first run) just quick-ty # Type check only changed files # Testing pytest path/to/tests/ # Run specific tests pytest python_modules/dagster/dagster_tests/ # Run core tests tox -e py39-pytest # Test

No other project uses it yet

dagster-ioCLAUDE.md

dagster / js_modules

dagster-io/dagster/js_modules/claude.md

using the `.oss.tsx` files. In cloud we build the app using `.cloud.tsx` files. # Testing Dagster UI The packages contained within are part of a yarn workspace. Check the respective package.json

No other project uses it yet

iamgioCLAUDE.md

quarkdown

iamgio/quarkdown/CLAUDE.md

keep it consistent with the style used in the project. Aim for a test-driven development (TDD) approach when possible. Tests play an important role. See [Testing](#testing) below. When

No other project uses it yet

javascript-obfuscatorCLAUDE.md

javascript-obfuscator

javascript-obfuscator/javascript-obfuscator/CLAUDE.md

javascript-obfuscator/escodegen 2.3.0 - **AST Traversal**: @javascript-obfuscator/estraverse 5.4.0 - **DI Framework**: InversifyJS 7.10.8 - **Testing**: Mocha 10.4.0 + Chai 4.3.7 - **Build System**: Webpack 5.75.0 ### Project Structure ``` javascript-obfuscator/ ├── src/ # Source code

No other project uses it yet

alshedivatCLAUDE.md

al-folio

alshedivat/al-folio/CLAUDE.md

jekyll build --baseurl /al-folio # production-style build to _site/ bash test/integration_distill.sh # run ONE integration test (any of the seven in test/) npm run test:visual:update # refresh playwright snapshots after

No other project uses it yet

chenhg5CLAUDE.md

cc-connect

chenhg5/cc-connect/CLAUDE.md

exceeds ~80 lines - Naming: `New()` for constructors, `Get/Set` for accessors, avoid stuttering (`feishu.FeishuPlatform` → `feishu.Platform`) ## Testing ### Requirements - All new features must include unit tests - All bug fixes should include a regression

shadowsocksCLAUDE.md

shadowsocks-libev

shadowsocks/shadowsocks-libev/CLAUDE.md

Linux netfilter features - `-DENABLE_SANITIZERS=ON`, `-DENABLE_COVERAGE=ON`, `-DDISABLE_SSP=ON`, `-DBUILD_TESTING=OFF` ## Testing ### Unit Tests (CTest) ```bash ctest --test-dir build -LE memcheck --output-on-failure ``` Unit

No other project uses it yet

bagistoCLAUDE.md

opensource-ecommerce-mobile-app

bagisto/opensource-ecommerce-mobile-app/CLAUDE.md

example: - new feature or behavior change: `superpowers:brainstorming`, then `superpowers:writing-plans` - bug, test failure, unexpected behavior: `superpowers:systematic-debugging` - writing code: `superpowers:test-driven-development` - before claiming "done

No other project uses it yet

quarkusioCLAUDE.md

quarkus

quarkusio/quarkus/CLAUDE.md

steps** — Read `.agents/skills/writing-build-steps/SKILL.md` when creating or modifying `@BuildStep` methods, build items, or recorders. - **Writing tests** — Read `.agents/skills/writing-tests/SKILL.md` when creating or modifying tests for Quarkus extensions. - **Working with config** — Read `.agents/skills/working-with-config/SKILL.md

No other project uses it yet

explodinggradientsCLAUDE.md

ragas

explodinggradients/ragas/CLAUDE.md

Large Language Model (LLM) applications. It provides objective metrics for evaluating LLM applications, test data generation capabilities, and integrations with popular LLM frameworks. The repository contains: 1. **Ragas Library

rjsf-teamCLAUDE.md

react-jsonschema-form

rjsf-team/react-jsonschema-form/CLAUDE.md

packages (sequential, use if parallel causes issues) pnpm run build-serial # Run all tests pnpm test # Lint (oxlint, type-aware) pnpm run lint # Typecheck every package and its tests pnpm

No other project uses it yet

aaPanelCLAUDE.md

BillionMail

aaPanel/BillionMail/CLAUDE.md

routes → `core/api/`, one dir per domain - Frontend views → `core/frontend/src/views/`, one dir per feature - Tests → next to source files (`*_test.go`, `*.test.ts`) - Single responsibility per file, descriptive names ## Code Quality After editing

organicmapsCLAUDE.md

organicmaps / android

organicmaps/organicmaps/android/CLAUDE.md

CarAppSessionBase` -- service and session lifecycle - Separate manifest for car permissions (`NAVIGATION_TEMPLATES`, `ACCESS_SURFACE`) ## Testing - JUnit 4 with Mockito - Unit tests: `app/src/test/java/`, `sdk/src/test/java/` - Instrumentation tests: `sdk/src/androidTest/java/` - If applicable, test

No other project uses it yet

organicmapsCLAUDE.md

organicmaps

organicmaps/organicmaps/CLAUDE.md

Standard library: in angle brackets #include #include <boost/noncopyable.hpp> // Third-party: in angle brackets ``` ### C++ testing patterns ```cpp namespace test_file_name { // Unit tests use custom macros from testing/testing.hpp, not Google

No other project uses it yet

organicmapsCLAUDE.md

organicmaps / data

organicmaps/organicmaps/data/CLAUDE.md

checksums - `countries_meta.txt` -- country/region languages and driving sides - `borders/` -- country/region border polygons - `minsk-pass.mwm` -- small test map ## Adding a new map feature / search category 1. Add to `mapcss-mapping.csv` (OSM tag -> OM type

No other project uses it yet

organicmapsCLAUDE.md

organicmaps / generator

organicmaps/organicmaps/generator/CLAUDE.md

data/mapcss-mapping.csv` to `OsmElement` - `GeneratorTool` (`generator_tool/generator_tool.cpp`) -- CLI entry point with flag-based stage selection ## Testing - Tests: `generator_tests/` (unit), `generator_integration_tests/` (integration) - Most-edited test file: `generator_tests/osm_type_test.cpp