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.
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-master/CLAUDE.md
used for unsafe scripting (e.g. conditional branch expressions). Upgrading the dep is sensitive — test the condition/switch task flows. - **Scheduler integration via `SchedulerApi`** (from `dolphinscheduler-scheduler-plugin`). The only current impl
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-meter/CLAUDE.md
health,info,metrics` in their `application.yaml`. This module does not ship its own YAML. ## Tests Minimal — mostly auto-config wiring. ## Related modules - `dolphinscheduler-common` — compile dep. - `dolphinscheduler-actuator-authentication
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-microbench/CLAUDE.md
warmup + 10 measurement iterations by default. Runs JMH via `Runner` from a JUnit `@Test` method (so the JMH launch is triggered by `mvn test` when you opt in). - `microbench.rpc.RpcBenchMarkTest` — Netty
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-registry/CLAUDE.md
main DolphinScheduler DB; useful when Zookeeper/Etcd aren't available) - `dolphinscheduler-registry-it` (integration tests exercising all three) - **`dolphinscheduler-registry-all`** — uber module that bundles every implementation; depended
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-scheduler-plugin/CLAUDE.md
SchedulerApi`; (3) register via Spring Boot `spring.factories` / `AutoConfiguration.imports`; (4) add itself to `scheduler-all`. ## Tests Inside `-quartz/src/test/java`. ## Related modules - `dolphinscheduler-master` — consumes `scheduler-all`. - `dolphinscheduler-service` — uses `CronService` for next
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-service/CLAUDE.md
contract change visible to every task. ## Configuration None shipped; consumers pass standard Spring profiles. ## Tests Standard `src/test/java`. Some tests mock `curator-test` for registry; most are pure unit. ## Related modules
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-spi/CLAUDE.md
modules of the plugin families (`task-api`, `datasource-api`, `dao-api`, etc.). ## Tests Standard `src/test/java`. ## Related modules - `dolphinscheduler-common` — consumed `provided` only. - `dolphinscheduler-task-plugin` / `dolphinscheduler-datasource-plugin` / `dolphinscheduler-storage
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-standalone-server/CLAUDE.md
process with an **H2 in-memory** database. Intended for local development, smoke tests, and lightweight demos — **not** for production. ## Entry point `StandaloneServer` — a thin `@SpringBootApplication` whose only
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-storage-plugin/CLAUDE.md
task artifact handling (not only as the resource store). This is the most battle-tested code path. - **OBS listStorageEntity** had a bug where subdirectories were not returned — fixed recently
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-task-executor/CLAUDE.md
lifecycle event that was never published from the executor here. - **Module has no tests** — coverage comes from `dolphinscheduler-worker` integration tests. Changes here need worker-side verification. ## Related modules - `dolphinscheduler
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-task-plugin/CLAUDE.md
versions shared with the core; large client libraries (Spark, Flink, Hadoop) are plugin-local. ## Tests Each plugin has `src/test/java` with mocked clients (e.g., mocked `SparkSubmit`, mocked `HttpClient
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-tools/CLAUDE.md
JDBC URL is exported. ## Configuration `application.yaml` — primarily datasource config so the tool can connect. ## Tests `src/test/java` uses Testcontainers (MySQL + PostgreSQL) to run end-to-end schema init + upgrade against
No other project uses it yet
apacheReads credentialsCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-ui/CLAUDE.md
Language toggle stored in the `language` cookie (`js-cookie`). ## Gotchas - **No unit tests** are configured (no `*.spec.ts` / `*.test.ts` found). End-to-end coverage comes from `dolphinscheduler-e2e`. - **Node version drift
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-worker/CLAUDE.md
resource limits, executor thread pools, task-type enable list, load-protection thresholds. - `logback-spring.xml`, `banner.txt`. ## Tests `src/test/java` — unit tests for registry, RPC, load protection, connection-state handling. End-to-end workflows
No other project uses it yet
apacheCLAUDE.mdapache/dolphinscheduler/dolphinscheduler-yarn-aop/CLAUDE.md
AspectJ version is pinned in `dolphinscheduler-bom`** (`aspectj.version`, currently 1.9.7). Upgrading AspectJ is sensitive — test every YARN-based task plugin. - **Tests use AspectJ syntax to mock YARN**. `YarnClientMoc`, `YarnClientAspectMoc`, `YarnClientMocTest
No other project uses it yet
coturnDeletes or force-pushesCLAUDE.mdcoturn/coturn/CLAUDE.md
TYPE=Debug|Release` — defaults to `Release` (`-O3 -DNDEBUG`) when unset, so benchmark and load-test builds are optimized without opting in. `-DFUZZER=ON` builds are exempt: they take their
Steady5 mentions in 2 weeks
No other project uses it yet
fathahCLAUDE.mdfathah/hermes-desktop/CLAUDE.md
responding to the user: - [ ] Update `lat.md/` if you added or changed any functionality, architecture, tests, or behavior - [ ] Run `lat check` — all wiki links and code refs must pass
jackcReads credentialsCLAUDE.mdjackc/pgx/CLAUDE.md
database/sql` compatible driver. Requires Go 1.25+ and supports PostgreSQL 14+ and CockroachDB. ## Build & Test Commands Every checkout has its own PostgreSQL 14-18 and CockroachDB instances, supervised by process-compose
semaphoreuiCLAUDE.mdsemaphoreui/semaphore/.claude/CLAUDE.md
research Use MCP server `research` if your asks you to research something. ## Writing Tests Use `github.com/stretchr/testify/assert` (and `require` when a failure should stop the test immediately). ### Run tests ```bash
No other project uses it yet
idankReads credentialsCLAUDE.mdidank/explainshell/CLAUDE.md
SQLite, bashlex, OpenAI SDK, Google Gemini SDK, LiteLLM (fallback) - Linting: ruff (Python), biome (JS) - Testing: pytest (unit + doctests), JS Playwright Test (e2e) - Dependencies: `requirements.txt` (web serving), `requirements-extraction.txt` (LLM SDKs, offline
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.
