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
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.
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
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
Steady4 mentions in 2 weeks
No other project uses it yet
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
1 project uses a version of this
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
Steady11 mentions in 2 weeks
No other project uses it yet
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
Steady11 mentions in 2 weeks
No other project uses it yet
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
Steady3 mentions in 2 weeks
No other project uses it yet
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
Steady3 mentions in 2 weeks
No other project uses it yet
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
Steady2 mentions in 2 weeks
No other project uses it yet
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
Surging9 mentions in 2 weeks
1 project uses a version of this
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
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
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
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
1 project uses a version of this
GLips/Figma-Context-MCP/CLAUDE.md
Development mode with watch + auto-restart (HTTP) pnpm dev:cli # Development mode (stdio) pnpm test # Run Vitest tests pnpm type-check # TypeScript type checking only pnpm lint # ESLint pnpm format
No other project uses it yet
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
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
1 project uses a version of this
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
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
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
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
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.