fiddle
electron/fiddle/CLAUDE.md
through Electron's `dialog` module, so the driver can script them. - `shell`, protocol, recent-document, notification and `Menu.popup` calls through Electron as usual. Test mode records and stubs them. - `win.show
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.
electron/fiddle/CLAUDE.md
through Electron's `dialog` module, so the driver can script them. - `shell`, protocol, recent-document, notification and `Menu.popup` calls through Electron as usual. Test mode records and stubs them. - `win.show
evrone/go-clean-template/CLAUDE.md
common regression in this repo. Update all three whenever a change touches what they document: | Change | What to update in every README | | --- | --- | | New or changed REST / gRPC endpoint | the domain
deanpeters/Product-Manager-Skills/CLAUDE.md
every Component and Workflow skill ships `template.md` + two-domain worked examples. Three documented carve-outs: `finance-metrics-quickref` (definitionally SaaS, template only), `skill-authoring-workflow` (meta-skill, one example), `product
Steady6 mentions in 2 weeks
No other project uses it yet
mnfst/manifest/CLAUDE.md
cannot load Better Auth's ESM. - **Discovery**: `mcp-discovery.ts` (mounted in `main.ts`) serves the OAuth documents at the well-known **root** paths (`/.well-known/oauth-authorization-server`, `/.well-known/oauth-protected-resource[/api/v1/mcp]`) in addition to Better Auth
imaNNeo/fl_chart/CLAUDE.md
lines_longer_than_80_chars` is disabled - Generated `*.mocks.dart` files are excluded from analysis ## Documentation - The dartdoc comments (`///`) of the data classes in `lib/` are the single source of truth
Steady24 mentions in 2 weeks
No other project uses it yet
arkime/arkime/.claude/CLAUDE.md
appropriate service 2. Add route in main service file (viewer.js, cont3xt.js, etc.) 3. Document with JSDoc (METHOD, @name, @param, @returns) 4. Add test in tests/*.t file
FastLED/FastLED/CLAUDE.md
datasheets / user manuals | Prefer https://github.com/FastLED/datasheets when available, then vendor primary documentation | | Creating an API wrapper type | `agents/docs/cpp-standards.md` → "API Object Pattern" | | Adding a global setting / configuration knob | `agents/docs/cpp-standards.md` → "Public
h2oai/h2o-3/CLAUDE.md
verbose logging: `-Dlog.level=DEBUG` or `-Dlog.level=TRACE` - Use `Log.info()`, `Log.warn()`, `Log.err()` (not `System.out`) ### Building Documentation ```bash ./gradlew clean && ./gradlew build -x test && (export DO_FAST=1; ./gradlew dist) open target/docs-website/h2o-docs/index.html
anthropics/defending-code-reference-harness/CLAUDE.md
real-world CVE demo targets — pinned to vulnerable commits, with per-target READMEs documenting the CVEs and expected find times. htslib is the harder of the set (CRAM container format
No other project uses it yet
enso-org/enso/app/CLAUDE.md
lezer/markdown` with Enso-specific extensions. - `lang-markdown/` — CodeMirror language package wrapping the markdown grammar (documentation editor). - `table-expression/` — Lezer grammar for the table-expression mini-language shown in the node
No other project uses it yet
enso-org/enso/CLAUDE.md
tools (IGV plugin, http test helper, CI scripts, benchmark analysis). - `docs/` — Extensive developer documentation (RFCs, style guides, runtime internals, LSP protocol). Start at `docs/README.md`. - `project/` — SBT plugins and build helpers
No other project uses it yet
enso-org/enso/docs/CLAUDE.md
docs/ Developer documentation for the Enso Engine, not user docs. (User docs live at https://help.enso.org.) Read `README.md` for the top-level index. ## High-value entry points - `CONTRIBUTING.md` — Build prerequisites
No other project uses it yet
enso-org/enso/engine/CLAUDE.md
test/` (Enso code) run via `sbt 'runEngineDistribution --run test/…'`. - See `docs/runtime-guide.md` §"Code & Internal Documentation Map" for the map of entry points. ## Gotchas - Building the runtime is slow (native-image stages
No other project uses it yet
modelcontextprotocol/registry/CLAUDE.md
docs/modelcontextprotocol-io/quickstart.mdx` for instructions. Pull requests here are for changes to the registry's code, documentation, and development fixtures
Ripple-TS/ripple/CLAUDE.md
templates/`: Ripple scaffolding - `playground/ripple/`, `benchmarks/`, `website/`, and `website-new/`: Ripple examples, performance work, and documentation Shared `@tsrx/*` packages are registry dependencies. Do not recreate moved compiler, formatter, linter, language-server
1 project uses a version of this
projectcalico/calico/charts/CLAUDE.md
between charts, adding or removing a manual step, renaming a chart, and changing a documented values key or example command. See [`.github/instructions/helm-charts.instructions.md`](../.github/instructions/helm-charts.instructions.md). ## AI-assisted contribution policy Contributions written with
projectcalico/calico/.claude/CLAUDE.md
with methods if tightly coupled with particular methods. - Larger secondary structs at the bottom. ## Documentation map This repo carries an extensive corpus of architecture and review guidance. **Consult it first
projectcalico/calico/felix/CLAUDE.md
SAFE_` convention for shared FV tests, and the harness conventions for `bpf/ut/` are documented in [`design/bpf-tests.md`](./design/bpf-tests.md). **Name a new FV test that needs BPF mode `_BPF-SAFE
projectcalico/calico/operator/CLAUDE.md
files`, verify the scope of existing resources wasn't changed to "Namespaced". ## Design Principles & Documentation Map Read the relevant doc before working in these areas: | Task | Read | |------|------| | Architecture & design rationale
kyegomez/swarms/CLAUDE.md
with the **Swarms** framework. Read it before writing any code in this repo. ## Live documentation This file can lag the code. For current signatures and pages, query the docs
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.