docusaurus
facebook/docusaurus/AGENTS.md
check its presence to know which rules to apply. ### General rules - Humans review all the code: always write code that is easy to read and review, following the [`code-style
No other project uses it yet
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.
facebook/docusaurus/AGENTS.md
check its presence to know which rules to apply. ### General rules - Humans review all the code: always write code that is easy to read and review, following the [`code-style
No other project uses it yet
coollabsio/coolify/AGENTS.md
artisan test --compact --filter=testName # single test php artisan test --compact tests/Feature/SomeTest.php # specific file # Code formatting (Pint, Laravel preset) vendor/bin/pint --dirty --format agent # format changed files # Frontend
warpdotdev/warp/AGENTS.md
feedback; defer checks and tests until after implementation where possible. 2. Once the code and self-review are complete, run the relevant tests and fix the code until they pass
Steady9 mentions in 2 weeks
2 projects use a version of this
webpack/webpack/AGENTS.md
real before/after (code, output, size, memory or CPU) under **Summary**. - **Subscribe to every PR you open**; unsubscribe once CI is green and every automated review is handled, or the requester
traefik/traefik/AGENTS.md
answer *why*, not *what*.** Comments that restate what the code already says are noise: they go stale and waste review time. Only add a comment when it records
scrapy/scrapy/AGENTS.md
only on what it has as well. - Review your own diff. Remove whatever the change does not need: unused parameters, dead code, leftover debugging, comments that restate the code. ## Code
No other project uses it yet
usememos/memos/AGENTS.md
response redaction. Black-box service tests live in `server/api/test/`, unit tests next to the code. ## Change Routing | Change | Update | Verify | | --- | --- | --- | | Go service or router behavior | Handlers under `server/`, rules under
git/git/po/AGENTS.md
Reviewing translation quality ## Background knowledge for localization workflows Essential background for the workflows below; understand these concepts before performing any housekeeping tasks in this document. ### Language code and notation
3 projects use a version of this
withastro/astro/AGENTS.md
narrate change history ("now", "previously", "no longer") and never address the reviewer ("this correctly handles..."). State how the code works, not how it came to be or why the change
tw93/Pake/AGENTS.md
suite minus the multi-arch real build | | `pnpm test` | Full suite including release workflow | ## Code Conventions - No Chinese comments in any source (Rust / TypeScript / any file). Comments and identifiers
ultralytics/ultralytics/AGENTS.md
intentionally removes them with evidence. **Review gate:** for every addition, the reviewer decides whether deleting or changing existing code would have fixed the problem instead — if it would, that
No other project uses it yet
BerriAI/litellm/AGENTS.md
requesting maintainer review, verify the current PR tip passes required CI and code coverage and has acceptable reviews from the review bots on the PR, such as Veria and Bugbot
penpot/penpot/AGENTS.md
Writing rules, from Orwell, 1946. These govern prose: docs, PR text, messages. Never touch code or technical terms; swap in everyday words only where precision survives. 1. Never
Steady6 mentions in 2 weeks
No other project uses it yet
chen08209/FlClash/AGENTS.md
expose the same skills to Claude Code. Current skills cover localization, UI work, UI performance, core/platform changes, and pre-commit structural quality review
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
rclone/rclone/AGENTS.md
elegant, smallest change you can. Do not refactor or re-order code unless necessary as this makes review more challenging. Re-use existing test scaffolding, existing or library routines
Steady4 mentions in 2 weeks
No other project uses it yet
spring-projects/spring-framework/AGENTS.md
usage. ## Docs - Reference docs are AsciiDoc in `framework-docs/modules/ROOT`; code snippets for `include-code::` live in `framework-docs/src/main/{java,kotlin}`. ## Commits and pull requests - Pull requests target `main
Steady2 mentions in 2 weeks
No other project uses it yet
ultralytics/yolov5/AGENTS.md
intentionally removes them with evidence. **Review gate:** for every addition, the reviewer decides whether deleting or changing existing code would have fixed the problem instead — if it would, that
No other project uses it yet
Gathin23/cleanyourtv/AGENTS.md
config.json`, for this TV. Do not edit the repo's docs, tests or other code, and do not open issues or pull requests unless the person asks you to. | | Change
pingchesu/gsd-hermes/docs/AGENTS.md
agents** detailed in this section. Twelve additional shipped agents (pattern-mapper, debug-session-manager, code-reviewer, code-fixer, ai-researcher, domain-researcher, eval-planner, eval-auditor, framework-selector, intel-updater
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.