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.
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/c-level-advisor/CLAUDE.md
board-prep` | Board meeting preparation | | `/executive-mentor:hard-call` | Framework for hard decisions | | `/executive-mentor:stress-test` | Stress-test any assumption | | `/executive-mentor:postmortem` | Honest retrospective | ## Key Design Decisions - **Two-layer memory
Steady28 mentions in 2 weeks
No other project uses it yet
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/engineering-team/CLAUDE.md
zones - **gcp-cloud-architect** — GCP infrastructure design, Terraform modules, cloud-native patterns - **security-pen-testing** — Penetration testing methodology, vulnerability assessment, exploit analysis - **snowflake-development** — Snowflake data warehouse development, SQL optimization
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/finance/CLAUDE.md
preferred equity, hard money / bridge funds, and private credit, pasted from any source. Stress-tests returns against public benchmarks plus an illiquidity premium, converts the fee stack to gross
Steady28 mentions in 2 weeks
No other project uses it yet
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/product-team/CLAUDE.md
Sample Size Calculator (`experiment-designer/scripts/sample_size_calculator.py`) **Purpose:** Statistical sample size planning for A/B tests and experiments **Features:** - Minimum detectable effect (MDE) calculation - Absolute and relative effect size modes - Power analysis
Steady28 mentions in 2 weeks
No other project uses it yet
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/standards/CLAUDE.md
standards/` **Available Standards:** 1. **communication/** - Communication principles and response protocols 2. **quality/** - Code quality, testing, and validation standards 3. **git/** - Git workflow, conventional commits, branching strategy 4. **documentation/** - Markdown quality
alirezarezvaniCLAUDE.mdalirezarezvani/claude-skills/templates/CLAUDE.md
agents/domain/cs-new-agent.md # 2. Customize for your agent vim agents/domain/cs-new-agent.md # 3. Follow template structure exactly # 4. Test relative paths and integrations # 5. Commit with conventional commit git commit -m "feat(agents): implement
chroma-coreCLAUDE.mdchroma-core/chroma/CLAUDE.md
rust-client): Fix connection timeout on retry [TST](gc): Add MCMR hard delete integration test [DOC](api): Update embeddings endpoint docs [CHORE](deps): Bump reqwest to 0.13 ``` Common types
No other project uses it yet
AgriciDanielReads credentialsCLAUDE.mdAgriciDaniel/claude-seo/CLAUDE.md
/scripts/claude-seo" run`; plugin state uses `CLAUDE_PLUGIN_DATA` - Manual Python dependencies install into `~/.claude/skills/seo/.venv/` - Test with `python3 -m pytest tests/` after changes (if applicable) ## Security Rules - **Never commit credentials
nrwlCLAUDE.mdnrwl/nx/CLAUDE.md
make multiple commits so that the changes are easier to review. 4. Run appropriate tests and validation 5. If the tests, are not passing, please fix the issues and continue
No other project uses it yet
yamadashyCLAUDE.mdyamadashy/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
Steady8 mentions in 2 weeks
No other project uses it yet
pmndrsCLAUDE.mdpmndrs/react-spring/CLAUDE.md
Node**: `.nvmrc` is `24.16.0`; `engines.node` in root `package.json` is `>=24.16.0`; CI runs the unit-test matrix on Node `22.x` and `24.x` and every other job off `.nvmrc`. - **Monorepo
Steady3 mentions in 2 weeks
No other project uses it yet
requarksCLAUDE.mdrequarks/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
jarrodwattsCLAUDE.mdjarrodwatts/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
Steady5 mentions in 2 weeks
No other project uses it yet
srbhrCLAUDE.mdsrbhr/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
swagger-apiCLAUDE.mdswagger-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
mlflowCLAUDE.mdmlflow/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-aiCLAUDE.mdmanaflow-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
BudibaseReads credentialsCLAUDE.mdBudibase/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
eyaltoledanoCLAUDE.mdeyaltoledano/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 69% this month
No other project uses it yet
eyaltoledanoReads credentialsCLAUDE.mdeyaltoledano/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 69% this month
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.
