How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
gtappsCLAUDE.mdgtapps/skills/skills/review-to-pr/references/claude.md
Claude Code workflow for review-to-pr. Verifies finished work, commits it locally, runs /code-review --fix in a fresh-context subagent on a chosen model, re-verifies, and opens or updates the PR, so no /clear or second session is needed.
gtappsCLAUDE.mdgtapps/skills/skills/task-report/references/claude.md
Publish a completed task's debrief as a claude.ai Artifact — outcome verdict, decisions made, verification evidence, review-priority file map, mechanically-rendered diffs, and copy-as-prompt follow-ups. Trigger on /task-report or when the user asks to summarize what you did, show what changed in this task/session, make a report/debrief/recap/handoff of the work, or review completed work — even phrased casually ("show me what you changed", "wrap this up as a report"). Do NOT use for a quick factual question about one file or change (answer in prose), for reviewing code for bugs (that's code review), or for plans awaiting approval (that's plan-to-artifact).
jaccenCLAUDE.mdjaccen/Awesome-Gaussian-Skills/CLAUDE.md
3D Spatial Intelligence Open-Source Toolbox for 3D Gaussian Splatting Research. 872 methods knowledge base, 15 research-grade skills (3 Router architecture), interactive explorer. Covers 3DGS paper reading, method comparison, code review, experiment planning, CAD/Mesh bridge, visualization, NeRF migration, engineering deployment, CG paper writing, IP generation, spatial intelligence, MCP rendering (spec-first sculpting + code-first export), articulated reasoning, compression & deployment, training debugging. SLAT unified representation framework for conversion skills.
Stewie-pixelCLAUDE.mdStewie-pixel/claude-with-leetcode/CLAUDE.md
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
idolamanCLAUDE.mdidolaman/galactic/CLAUDE.md
Enforces client coding conventions. Use when writing, reviewing, or modifying React/TypeScript code in the client/ directory. Ensures proper use of Tailwind/shadcn UI components, path aliases, TypeScript interfaces, icon usage, platform-safe storage/git logic, and consistent design system rules.
launchapp-devCLAUDE.mdlaunchapp-dev/animus-cli/.agents/skills/rust-skills/CLAUDE.md
Comprehensive Rust coding guidelines with 179 rules across 14 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Invoke with /rust-skills.
chasebuildCLAUDE.mdchasebuild/fuelcheck-cli/.agents/skills/rust-skills/CLAUDE.md
Comprehensive Rust coding guidelines with 179 rules across 14 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, API design, memory optimization, performance, testing, and common anti-patterns. Invoke with /rust-skills.
affaan-mCLAUDE.mdaffaan-m/ECC/CLAUDE.md
project is organized into several core components: - **agents/** - Specialized subagents for delegation (planner, code-reviewer, tdd-guide, etc.) - **skills/** - Workflow definitions and domain knowledge (coding standards, patterns, testing) - **commands/** - Slash
affaan-mCLAUDE.mdaffaan-m/ECC/examples/CLAUDE.md
DEBUG=false ``` ## Available Commands - `/tdd` - Test-driven development workflow - `/plan` - Create implementation plan - `/code-review` - Review code quality - `/build-fix` - Fix build errors ## Git Workflow - Conventional commits: `feat:`, `fix:`, `refactor:`, `docs:`, `test
garrytanCLAUDE.mdgarrytan/gstack/CLAUDE.md
required selected evaluations, then run the full free suite once on the final integrated code. During repairs, focused checks replace a full-suite run before every commit. `bun run test
nextlevelbuilderCLAUDE.mdnextlevelbuilder/ui-ux-pro-max-skill/stack/CLAUDE.md
primitives. 4. **SEE IT — Playwright / Chrome DevTools MCP.** You are not done when the code compiles. Open the page in a real browser, screenshot it, read the console, exercise interactive
JuliusBrusseeCLAUDE.mdJuliusBrussee/caveman/CLAUDE.md
bin/install.js` and `src/tools/caveman-init.js`. | | `skills/caveman-commit/SKILL.md` | Caveman commit message behavior. Fully independent skill. | | `skills/caveman-review/SKILL.md` | Caveman code review behavior. Fully independent skill. | | `skills/caveman-help/SKILL.md` | Quick-reference card. One-shot display, not a persistent mode
addyosmaniCLAUDE.mdaddyosmani/agent-skills/CLAUDE.md
skills/`. ## Project Structure ``` skills/ → Core skills (SKILL.md per directory) agents/ → Reusable agent personas (code-reviewer, test-engineer, security-auditor, web-performance-auditor) hooks/ → Session lifecycle hooks .claude/commands/ → Slash commands (/spec
MicrosoftCLAUDE.mdmicrosoft/playwright/CLAUDE.md
commit message: commit messages, PR titles and bodies, PR and issue comments, review comments, and code comments. There is no scope in which the footer is permitted — if you find
ruvnetCLAUDE.mdruvnet/RuView/CLAUDE.md
wasm node harness/homecore/bin/cli.js verify --repo . --profile wasm node harness/homecore/bin/cli.js agent run \ --host claude-code --repo . --prompt "Review the plugin trust boundary" node harness/homecore/bin/cli.js mcp start ``` The package requests the metaharness
Model Context ProtocolCLAUDE.mdmodelcontextprotocol/servers/CLAUDE.md
server `.python-version` file) - Type checking: **pyright** (enforced in CI) - Linting: **ruff** ## Code Style ### TypeScript - ES modules with `.js` extension in import paths - Strict TypeScript typing for all functions
Egonex-AICLAUDE.mdEgonex-AI/Understand-Anything/CLAUDE.md
Architecture - **Monorepo** with pnpm workspaces - **understand-anything-plugin/** — Claude Code plugin containing all source code: - **packages/core** — Shared analysis engine (types, persistence, tree-sitter, search, schema, tours, plugins) - **packages/dashboard** — React + TypeScript
ruvnetCLAUDE.mdruvnet/ruflo/CLAUDE.md
platforms cross-validating | | Limited reasoning styles | Complementary strengths | | No external verification | Built-in code review | | Sequential workflows | Parallel execution | ### Dual-Mode Swarm Protocol For complex tasks, spawn both Claude
shanraisshanCLAUDE.mdshanraisshan/claude-code-best-practice/CLAUDE.md
individual hooks in `hooks-config.json`. ## Answering Best Practice Questions When the user asks a Claude Code best practice question, **always search this repo first** (`best-practice/`, `reports/`, `tips/`, `implementation/`, and `README.md
AnthropicCLAUDE.mdanthropics/claude-cookbooks/claude_agent_sdk/chief_of_staff_agent/CLAUDE.md
Hiring**: Add 10 engineers to accelerate product development 2. **Product**: Launch AI code review feature by end of Q2 3. **Sales**: Expand into European market 4. **Fundraising**: Begin Series
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.
