slang
shader-slang/slang/CLAUDE.md
this layer owns the logic, with a code trace from producer to consumer. ### Code Style and Review Conventions Recurring review feedback distilled into rules — following them avoids review round-trips
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.
shader-slang/slang/CLAUDE.md
this layer owns the logic, with a code trace from producer to consumer. ### Code Style and Review Conventions Recurring review feedback distilled into rules — following them avoids review round-trips
shader-slang/slang/extras/claude.md
Amend A fresh agent reviews the commit as if it were a real code reviewer: checks correctness, style, edge cases, test coverage, and regressions. It also reviews all documentation changes
coleam00/ottomator-agents/claude-agent-sdk-demos/CLAUDE.md
Research** → Use knowledge base (see RAG workflow below) 4. **Implement** → Write code based on research 5. **Review** → `manage_task("update", task_id="...", status="review")` 6. **Next Task** → `find_tasks(filter
ethanplusai/harvey/CLAUDE.md
drafts" / the user is about to approve Outbox emails** → Offer to review them, since Sellbird runs on Claude Code and you can do what a scan can't. A draft
zenml-io/zenml/CLAUDE.md
Before opening a PR or making a large commit**, always run `/simplify` to review changed code for reuse opportunities, quality issues, and efficiency improvements. Fix any issues it finds before
zenml-io/zenml/.github/CLAUDE.md
template repos. Failure indicates breaking changes that need template updates. ## Special Workflows ### claude.yml AI code review integration. Triggered by `@claude` mentions in issues/PRs. Gated to internal team members via `teams.yml
phan/phan/CLAUDE.md
file paths in `.expected` files - **Line numbers**: Critical for matching expected warnings to actual code lines - **Issue types**: Must match exactly (e.g., `PhanTypeInvalidCallableMethodName`) - **Error messages**: Complete message text must match
Steady4 mentions in 2 weeks
No other project uses it yet
aaddrick/claude-desktop-debian/CLAUDE.md
summary and link to the PR ### Investigating Issues For older issues, review the state of the code when the issue was raised - it may have already been addressed: ```bash
SaladDay/cc-switch-cli/CLAUDE.md
assessment, known concerns, prior review findings, or another reviewer's conclusions. Reviewers must independently infer how the code attempts to meet the stated requirements. 5. Reviewers are read-only. Require
unkeyed/unkey/CLAUDE.md
reasoning from the code alone. - When debugging a failure, start from the incident or issue Polylane recorded: it carries the evidence an investigation already gathered. - Polylane reviews pull requests
cloudflare/vibesdk/CLAUDE.md
this repository. ## Communication Style - Be professional, concise, and direct - Do NOT use emojis in code reviews, changelogs, or any generated content. You may use professional visual indicators or favor markdown
breaking-brake/cc-wf-studio/CLAUDE.md
becomes the CHANGELOG entry) ``` This writes a `.changeset/ .md` file — commit it alongside your code. **You never hand-edit `CHANGELOG.md`; Changesets generates it.** If a PR genuinely needs no release
lukevella/rallly/CLAUDE.md
spaces?") — `features/instance-policy/` (`deriveInstancePolicy` in `utils.ts` is the inventory; `getInstancePolicy` from `data.ts` for server code, `loadInstancePolicy` from `loaders.ts` for pages, `useInstancePolicy` from `client.tsx`). When the organization layer lands this becomes
No other project uses it yet
streamyfin/streamyfin/CLAUDE.md
writing code in that area. | Document | Read it when | | --- | --- | | [docs/conventions/constants.md](docs/conventions/constants.md) | Adding a threshold, interval, ratio, storage key, or any value used twice | | [docs/conventions/contributing-flow.md](docs/conventions/contributing-flow.md) | Opening, describing, or reviewing
entireio/cli/CLAUDE.md
protocol](docs/architecture/external-agent-protocol.md) | | Security, privacy, scanners | [Security and privacy](docs/security-and-privacy.md), [implementation contracts](docs/development/checkpoint-implementation.md) | | Review command | [Review architecture](docs/architecture/review-command.md) | | Release artifacts, install scripts, version-check origins | [Release origins](docs/architecture/release-origins.md) | | E2E tests
umbraco/Umbraco-CMS/CLAUDE.md
dotnet format) - No build warnings - **Merge Strategy**: Squash and merge (via GitHub UI) - **Reviews**: Required from code owners #### PR Naming Convention Use the format: `Area: Description (closes #IssueID)` **Examples**: | Area
InternLM/xtuner/.claude/CLAUDE.md
requesting review. 3. Resolve all review comments before merging — do not dismiss without explanation. --- ## Code Review Standards ### What to Check 1. **Correctness**: Does the code do what it claims
Jeric-X/SyncClipboard/CLAUDE.md
operations; categories alone do not skip tests when running the full suite locally. ### Code Style ```bash # Check formatting (from src/ directory) dotnet format --verify-no-changes --severity info --no-restore
tixl3d/tixl/.claude/CLAUDE.md
turn of the current conversation, you may skip; across sessions, always re-read. - `.agentic/AGENT_INSTRUCTIONS.md` -- coding conventions, performance rules, operator guidelines, style and formatting. - `.agentic/SOLUTION_OVERVIEW.md` -- architecture map, dependency flow, task-oriented
Steady2 mentions in 2 weeks
No other project uses it yet
pytorch/executorch/CLAUDE.md
bullet lists of changes; explain review order for large PRs, or omit for small ones - Disclose PR was authored with AI, include tool name. ## Code Style - Minimal comments; code should
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.