sprout
block/sprout/AGENTS.md
they are defects authors agree with on sight. Authors apply them **before writing code**, and reviewers check against them; each cites the PRs where reviewers litigated it. 1. **Every caught
How real projects brief Codex, Cursor and every other agent that reads AGENTS.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.
block/sprout/AGENTS.md
they are defects authors agree with on sight. Authors apply them **before writing code**, and reviewers check against them; each cites the PRs where reviewers litigated it. 1. **Every caught
block/sprout/desktop/src/features/agents/AGENTS.md
code is worse than no rule; a new pattern that isn't written down here will be broken by the next agent that never learns it existed. Reviewers: treat
Steady13 mentions in 2 weeks
1 project uses a version of this
block/sprout/migrations/AGENTS.md
existing rows. Use the backfill framework in [docs/data-backfills.md](../docs/data-backfills.md), or, until it ships, a reviewed one-off script in `scripts/maintenance/`. - Make each change in every schema location: `migrations/`, `schema/tables/public
Steady13 mentions in 2 weeks
No other project uses it yet
utmapp/UTM/AGENTS.md
protocol — `UTMQemuVirtualMachine` (QEMU, via the QEMUKit/CocoaSpice packages) and `UTMAppleVirtualMachine` (Virtualization.framework, macOS-only). Most backend code branches on which. - **Config is the serialization format** — parallel `Codable` trees `UTMQemuConfiguration` and `UTMAppleConfiguration` (PLIST
No other project uses it yet
pingdotgg/t3code/AGENTS.md
same paths. That only works when it is a service method, not handler code. - **Contracts.** Anything crossing the wire is typed in `packages/contracts`. Change the schema and the server
Tencent/WeKnora/cli/AGENTS.md
action": "noun.verb"}, "detail": {} }, "_notice": {} } ``` `type` is the typed code (see [Error code reference](#error-code-reference) below). `hint` is prose; `retry_argv` is the suggested next argv as a JSON
No other project uses it yet
rustfs/rustfs/AGENTS.md
artifact-heavy work, read [implementation and Rust style rules](.agents/references/implementation.md). For a read-only code review, use its change-style and boundary sections as needed. - Before commits, pushes, PR creation/updates
rustfs/rustfs/crates/AGENTS.md
uses multiple locks. Never acquire the same set of locks in different orders across code paths. - Never hold a `tokio::sync::RwLock`/`Mutex` write guard across `.await` points unless
jdx/mise/AGENTS.md
Issue with AI assistance is fine and is not restricted. The user must review it before it is posted, and it needs the AI disclosure below. When you post
netty/netty/AGENTS.md
work back, say what you changed and what you verified, so the human can review it properly. ## Branches and Java baselines | Branch | Role | Java baseline | | ------ | ---- | ------------- | | 4.1 | maintenance, bug fixes only
huggingface/diffusers/.ai/AGENTS.md
post to GitHub directly** — no comments, reviews, or replies. Draft when asked and hand the text to the user. ## Code formatting - `make style` and `make fix-copies` should
qarmin/czkawka/AGENTS.md
just fix` produces any output on stderr or exits non-zero the code is not ready for review. --- ## Workspace Structure ``` czkawka/ ├── czkawka_core/ # Scanning logic – shared library used
SeleniumHQ/selenium/AGENTS.md
Grid routing/distributor/queue logic ## After making code changes - Call out any high risk areas touched - Note cross-binding impact and any follow-up issues needed ## Reviewing pull requests See `.github/pr_review.md
anywhere-labs/deepseek-harness-desktop/AGENTS.md
variant's upstream-family files export the same names as `undefined`, and the shared code skips the feature. Once both follow the same release they must mirror again. - Run upstream
k3s-io/k3s/.agents/AGENTS.md
Use when: browsing or selecting local k3s agentic workflows from this folder. Catalog of workflow folders and contract for cross-tool compatibility.
Gitlawb/openclaude/AGENTS.md
working in the OpenClaude repository. Read it before changing code, and also follow [CONTRIBUTING.md](CONTRIBUTING.md) for contributor policy, PR expectations, review follow-up, and project scope. ## Project Snapshot OpenClaude
swc-project/swc/AGENTS.md
continue. ## Code style - Write comments and documentations in English. - Write documentation for your code. - When introducing a workaround, leave sufficient comments explaining why it is needed and any known limitations
apache/kafka/AGENTS.md
checkstyleMain checkstyleTest spotlessCheck ./gradlew spotbugsMain spotbugsTest -x test # optional static analysis ``` Checkstyle reports: ` /build/reports/checkstyle/`. ## Coding conventions - **Commits / PR titles**: Start with `KAFKA-XXXXX`, `MINOR`, or `HOTFIX`. Use `KAFKA-XXXXX` only
OWASP/CheatSheetSeries/AGENTS.md
security review and testing. Illustrative status does not excuse incorrect or insecure guidance. - When reviewing code-heavy contributions, request a shorter conceptual revision with upstream implementation links. Successful execution
iOfficeAI/AionUi/AGENTS.md
path aliases: `@/*`, `@process/*`, `@renderer/*` - Prefer `type` over `interface` (per Oxlint config) - English for code comments; JSDoc for public functions ### Internationalization (i18n) New or changed user-facing text must use i18n
No other project uses it yet
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.