zenml
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
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.
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
weave-os/router/CLAUDE.md
write. - **Non-tautological tests** — every test must assert behavior that breaks if prod code deleted. ## Layer model and import rules Three concentric layers. Imports flow inward only. ``` +-------------------------------------------------------------------+ | cmd/router/main.go (composition root
Surging1 mention in 2 weeks
1 project uses a version of this
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
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
SaladDay/cc-switch-cli/CLAUDE.md
issues. - Validate every finding against the code. Make minimal fixes for confirmed issues within scope, run the relevant checks, then start another blind review with a new subagent under
No other project uses it yet
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
No other project uses it yet
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
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
Steady7 mentions in 2 weeks
No other project uses it yet
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
IsmaelMartinez/teams-for-linux/CLAUDE.md
bots like changelog, build artifacts, SonarQube): - Make the requested code changes - Commit and push the changes 3. Reply to the review by adding a PR comment summarizing all changes made
No other project uses it yet
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
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
rstudio/rstudio/.claude/CLAUDE.md
spanning open-source and pro-only code is made in rstudio-pro first: the whole change is opened as a PR there, reviewed, and approved, but not merged. An "open
clidey/whodb/CLAUDE.md
AGENTS.md ## Claude Code - Use plan mode for multi-file, risky, architectural, or ambiguous changes. - Use subagents only for bounded sidecar work: exploration, review, test triage, or documentation lookup. - Prefer separate
Steady4 mentions in 2 weeks
No other project uses it yet
langwatch/langwatch/CLAUDE.md
secret**; values resolve through `@langwatch/secrets` (ADR-132) and `haven env` masks them. Module code never reads `process.env`. ## Git and GitHub - Other changes in the checkout belong to someone else. Stage
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.