wiki
requarks/wiki/CLAUDE.md
case that cannot occur is dead code that still has to be read, tested and reasoned about. This applies to db columns, API payloads, stored settings and config keys alike
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.
requarks/wiki/CLAUDE.md
case that cannot occur is dead code that still has to be read, tested and reasoned about. This applies to db columns, API payloads, stored settings and config keys alike
No other project uses it yet
yamadashy/repomix/browser/CLAUDE.md
styles for injected elements ├── dist/ # Built extension files (generated) ├── promo/ # Store promotional materials └── tests/ # Test files ``` ## Development Commands ```bash npm run dev chrome # Development mode for Chrome npm run build
Steady4 mentions in 2 weeks
No other project uses it yet
srbhr/Resume-Matcher/.claude/CLAUDE.md
Backend (from repo root) cd apps/backend uv sync --extra dev # Install Python deps (incl. test deps) uv run uvicorn app.main:app --reload --port 8000 # FastAPI on :8000 uv run pytest
No other project uses it yet
jarrodwatts/claude-hud/CLAUDE.md
lines for tools, agents, todos, and more. ## Commands ```bash npm ci npm test # node --test; there is no build npm test -- tests/auth.test.js # one file; plain `node --test` skips tests/clean-env.js
Steady8 mentions in 2 weeks
No other project uses it yet
swagger-api/swagger-ui/CLAUDE.md
Architecture](#project-architecture) 3. [Development Setup](#development-setup) 4. [Build System](#build-system) 5. [Testing Infrastructure](#testing-infrastructure) 6. [Code Style & Conventions](#code-style--conventions) 7. [Git Workflow](#git-workflow
No other project uses it yet
mlflow/mlflow/CLAUDE.md
level imports (only use lazy imports when necessary) - Only add docstrings in tests when they provide additional context - Only add comments that explain non-obvious logic or provide additional context
No other project uses it yet
manaflow-ai/cmux/CLAUDE.md
regression before its fix; record the same focused command's red and green results ([testing policy](skills/cmux-testing/SKILL.md#reproduce-and-repair)). A bug-fix PR body names that command, its failure
No other project uses it yet
Budibase/budibase/CLAUDE.md
Build/Test Commands - Build: `yarn build` - Lint: `yarn lint` (check) or `yarn lint:fix` (fix) - Test: `yarn test ` run inside of a packages/\* directory - Type check: `yarn check:types` - packages/server tests
No other project uses it yet
eyaltoledano/claude-task-master/CLAUDE.md
commands and guidelines, treat as if import is in the main CLAUDE.md file.** @./.taskmaster/CLAUDE.md ## Test Guidelines ### Test File Placement - **Package & tests**: Place in `packages/ /src/ / .spec.ts` or `apps/ /src/ / ` alongside
Coolinginterest down 83% this month
No other project uses it yet
eyaltoledano/claude-task-master/.taskmaster/CLAUDE.md
multiple Claude Code sessions: ```bash # Terminal 1: Main implementation cd project && claude # Terminal 2: Testing and validation cd project-test-worktree && claude # Terminal 3: Documentation updates cd project-docs-worktree
Coolinginterest down 83% this month
No other project uses it yet
phuryn/pm-skills/CLAUDE.md
Claude agents) ├── CONTRIBUTING.md <- contributor guidelines ├── README.md <- public documentation (GitHub) ├── LICENSE <- MIT ├── validate_plugins.py <- plugin validator ├── tests/ <- unit + docs-consistency tests (unittest) └── pm-{name}/ <- 9 plugin directories ├── .claude-plugin/plugin.json <- per-plugin
Steady4 mentions in 2 weeks
No other project uses it yet
Donchitos/Claude-Code-Game-Studios/src/CLAUDE.md
specialists` block of `project.yaml`. When in doubt, use `specialists.code` from `project.yaml`. ## Tests Tests live in `tests/` — not in `src/`. Run `/test-setup` to scaffold the test framework if it doesn
Steady19 mentions in 2 weeks
1 project uses a version of this
Donchitos/Claude-Code-Game-Studios/studio-tests/CLAUDE.md
Studio Tests — Claude Instructions This folder is the quality assurance layer for the Claude Code Game Studios skill/agent framework. It is self-contained and separate from any game project
Steady19 mentions in 2 weeks
No other project uses it yet
OpenZeppelin/openzeppelin-contracts/CLAUDE.md
source. Subdirectory layout (`token/ERC20/`, `access/`, `utils/`, …) mirrors the public API. | | `contracts/mocks/` | Mocks used by tests. Mirrors `contracts/`. Manual mocks only — see the `testing` skill. | | `contracts/interfaces/` | ERC interfaces in their pristine
1 project uses a version of this
OI-wiki/OI-wiki/CLAUDE.md
corresponding `images/` directories 3. Run format checking: `yarn run docs:format:check` 4. Test locally: `uv run mkdocs serve` 5. Build and verify: `uv run mkdocs build` ### Adding New Topics
No other project uses it yet
onlook-dev/onlook/CLAUDE.md
large assets. - Propose minimal diffs aligned with existing conventions; avoid wide refactors. ### Notes - Unit tests can be run with `bun test` - Run type checking with `bun run typecheck` - Apply database
Steady2 mentions in 2 weeks
No other project uses it yet
humanlayer/12-factor-agents/CLAUDE.md
This project uses: - **Language/Framework**: [Add your stack here] - **Build Tool**: [Add your build commands] - **Testing**: [Add your test commands] - **Architecture**: [Describe your project structure] ## Core Principles (All Personas) 1. **READ
No other project uses it yet
VoltAgent/awesome-claude-code-subagents/CLAUDE.md
Language/framework experts (TypeScript, Python, etc.) 03-infrastructure/ # DevOps, cloud, Kubernetes, etc. 04-quality-security/ # Testing, security auditing, code review 05-data-ai/ # ML, data engineering, AI specialists 06-developer-experience
Surging5 mentions in 2 weeks
1 project uses a version of this
apify/crawlee/.claude/CLAUDE.md
PATH issues in this environment. ## Pre-Commit Checks Always run `pnpm tsc-check-tests` (or the project's type-check command) before committing any TypeScript changes. Never assume type safety
No other project uses it yet
anomalyco/sst/CLAUDE.md
build:cli` - **Run CLI locally**: `cd examples/ && go run ../../cmd/sst ` - **Go tests**: `bun run test:cli` - **Typecheck**: `bun run typecheck` - **Generate docs**: `bun run docs:generate` - **Run docs locally
Steady10 mentions in 2 weeks
1 project uses a version of this
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.