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.
photoprismCLAUDE.mdphotoprism/photoprism/.claude/CLAUDE.md
environment (app at http://localhost:2342/) - `make terminal` — open shell in dev container ## Testing **Run all tests:** - `make test` — runs the JS and Go tests on SQLite and the shell
Steady3 mentions in 2 weeks
No other project uses it yet
koalamanCLAUDE.mdkoalaman/shellcheck/.claude/CLAUDE.md
Claude Code (claude.ai/code) when working with code in this repository. ## Build and test commands ```sh cabal build # compile cabal test # run unit tests (source of truth) cabal run shellcheck
No other project uses it yet
mindsdbReads credentialsCLAUDE.mdmindsdb/mindsdb/CLAUDE.md
state, returning the machine to a pre-install condition. Use it to test the from-scratch install flow or to recover from a broken/half-installed environment. ```bash make flush # prompts before
1 project uses a version of this
spacedriveappCLAUDE.mdspacedriveapp/spacedrive/CLAUDE.md
just cli # Run the CLI (binary is sd-cli, not spacedrive) just test # cargo test --workspace cargo test # Run a single test just check # cargo fmt --check + cargo clippy --workspace
No other project uses it yet
spacedriveappCLAUDE.mdspacedriveapp/spacedrive/.tasks/Claude.md
task (they're usually listed in an "Implementation Files" section) - **Check core/tests/** for integration tests that validate the feature (for core tasks) - **Check packages/interface/src/** for interface implementations (for interface tasks
No other project uses it yet
MicrosoftCLAUDE.mdmicrosoft/playwright-mcp/CLAUDE.md
Build and test The MCP server source lives in `microsoft/playwright`, in `packages/playwright-core/src/tools/`. This repo ships `@playwright/mcp`: `cli.js` and `index.js` run the server from the `playwright-core` alpha that `package.json` pins
Steady9 mentions in 2 weeks
No other project uses it yet
ant-designCLAUDE.mdant-design/ant-design-pro/CLAUDE.md
mock), `npm run build` (utoopack), `npm run lint` (Biome+tsc), `npm run test` (Jest), `npx antd lint ./src` (antd-specific checks). Other: `npm run openapi` (regenerate `src/services/`), `npm run simple
No other project uses it yet
portainerCLAUDE.mdportainer/portainer/CLAUDE.md
theming - [docs/guidelines/typescript-conventions.md](../../docs/guidelines/typescript-conventions.md) — types, anti-patterns, union types, named constants - [docs/guidelines/frontend-unit-testing.md](../../docs/guidelines/frontend-unit-testing.md) — Vitest, React Testing Library ## Backend Guidelines - [docs/guidelines/go-conventions.md](../../docs/guidelines/go-conventions.md) — error handling, naming, testing, code style - [docs/guidelines/server-architecture.md](../../docs/guidelines/server-architecture.md) — Clean Architecture
No other project uses it yet
TriliumNextReads credentialsCLAUDE.mdTriliumNext/Trilium/CLAUDE.md
start # standalone (in-browser) client pnpm client:build | server:build | desktop:build pnpm --filter test # e.g. pnpm --filter server test spec/etapi/search.spec.ts pnpm --filter coverage # per-package coverage (client, server, standalone
Steady2 mentions in 2 weeks
No other project uses it yet
CopilotKitCLAUDE.mdCopilotKit/CopilotKit/CLAUDE.md
General Guidelines for working with Nx - When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many
No other project uses it yet
CopilotKitCLAUDE.mdCopilotKit/CopilotKit/showcase/CLAUDE.md
single-source symlink mechanism, and the preflight/value-test checklist). Read it before touching any integration, test, fixture, or frontend under `showcase
No other project uses it yet
lernaCLAUDE.mdlerna/lerna/CLAUDE.md
multiple packages. Lerna uses Nx as the task runner and monorepo manager for building, testing, and managing the various Lerna commands and core functionality. ## Package Manager This project uses
No other project uses it yet
filebrowserCLAUDE.mdfilebrowser/filebrowser/.claude/CLAUDE.md
frontend/`. - The project is in **maintenance-only mode** (see `SECURITY.md`). Prefer small, surgical, well-tested changes. - Version scheme: `v2.63.x`. Conventional-commit messages (`fix(scope): …`, `feat: …`, `chore: …`). - Verify with `go build
qdrantCLAUDE.mdqdrant/qdrant/CLAUDE.md
published crate `qdrant-edge` is assembled from these sources by `publish/amalgamate.py`. ## Build, lint, test - Format: `cargo +nightly fmt --all` (needs nightly). - Lint: `cargo clippy --workspace --all-targets -- -D warnings`. When
No other project uses it yet
motiondivisionCLAUDE.mdmotiondivision/motion/CLAUDE.md
build # or: make build # Watch mode for development yarn watch # or: make watch # Run tests yarn test # Unit tests (Jest) for all packages, then type-checks src + tests yarn test
No other project uses it yet
pcottleCLAUDE.mdpcottle/learnGitBranching/CLAUDE.md
Checked production build in ./build yarn generate # Regenerate level + locale manifests (also pre-hooked) ``` ### Testing & Linting ```bash yarn test # Run Jasmine test suite yarn test:coverage # Run tests with
No other project uses it yet
nicolargoCLAUDE.mdnicolargo/glances/CLAUDE.md
YOUR changes made unused. - Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. ## 4. Goal-Driven Execution
No other project uses it yet
k1tbyteCLAUDE.mdk1tbyte/Wemod-Patcher/CLAUDE.md
Vite, bridge bundle, `verify:dist` - `cd web-panel; pnpm exec vitest run ` - one web test - `build.cmd -EnableUpdateNotifications` - the opt-in update-check variant ## Rules `.claude/rules/` holds the working rules. Claude
1 project uses a version of this
surrealdbCLAUDE.mdsurrealdb/surrealdb/CLAUDE.md
code (REQUIRED before commits) cargo make fmt # Run clippy lints cargo make ci-clippy ``` ## Testing Conventions Language tests, upgrade tests, and benchmarks: `language-tests/CLAUDE.md`. Parser tests: `surrealdb/parser-next/CLAUDE.md`. ### Keep
No other project uses it yet
surrealdbCLAUDE.mdsurrealdb/surrealdb/language-tests/CLAUDE.md
CLAUDE.md Conventions for the SurrealQL test suite in `language-tests/`. ## Commands ```bash # Run language tests cd language-tests && cargo run run # Run specific language test # Note: all paths are relative
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.
