AGENTS.md examples from real projects

usememosAGENTS.md

memos

usememos/memos/AGENTS.md

never by rewriting the body. See `docs/design/README.md`. Verify current behavior in source code and tests, not in design documents. - Brand copy (tagline, descriptions, README intro) comes verbatim from [`BRAND.md

gitAGENTS.md

git / po

git/git/po/AGENTS.md

reimplement. It generates `po/l10n-pending.json` with messages that need translation. ```shell l10n_extract_pending () { test $# -ge 1 || { echo "Usage: l10n_extract_pending " >&2; return 1; } PO_FILE="$1" PENDING="po/l10n-pending.json

withastroAGENTS.md

astro

withastro/astro/AGENTS.md

YOUR changes made unused. - Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. # Goal-Driven Execution **Define

No other project uses it yet

marktextAGENTS.md

marktext

marktext/marktext/AGENTS.md

State management | Pinia 3 | | Routing | Vue Router 4 | | UI library | Element Plus | | Unit tests | Vitest 4 | | E2E tests | Playwright | | Package manager | pnpm >=10 workspace (`packageManager: pnpm@10.33.4`) | | Repo layout | pnpm

ghostty-orgAGENTS.md

ghostty

ghostty-org/ghostty/AGENTS.md

Demit-macos-app=false` to skip building the app bundle and speed up compilation. - **Test (Zig):** `zig build test` - Prefer to run targeted tests with `-Dtest-filter` because the full

ghostty-orgAGENTS.md

ghostty / macos

ghostty-org/ghostty/macos/AGENTS.md

macos/build.nu [--scheme Ghostty] [--configuration Debug] [--action build]` - Output: `macos/build/ /Ghostty.app` (e.g. `macos/build/Debug/Ghostty.app`) - Run unit tests directly with `macos/build.nu --action test` ## AppleScript - The AppleScript scripting definition is in `macos/Ghostty.sdef`. - Guard AppleScript

ultralyticsAGENTS.md

ultralytics

ultralytics/ultralytics/AGENTS.md

solution. Avoid impossible-state handling, speculative flags, compatibility shims, policy scaffolding, and unrelated cleanup. Tests are out of scope by default — rely on existing coverage and focused validation; only

No other project uses it yet

hugohe3AGENTS.md

ppt-master

hugohe3/ppt-master/AGENTS.md

worktrees/`, CI, or mandatory branch setup unless the user explicitly requests them. The only test location is `skills/ppt-master/scripts/tests/` under the conditions in [`docs/rules/code-style.md`](docs/rules/code-style.md) §11. - On conflict with a generic

No other project uses it yet

tw93AGENTS.md

Pake

tw93/Pake/AGENTS.md

pake skill) ├── llms.txt # Agent-facing contract summary (--json, --config, exit codes) ├── scripts/ # Utility scripts ├── tests/ # Unit, integration, and release-flow tests ├── .github/workflows/ # quality/test and release automation ├── default_app_list.json # Popular apps config

BerriAIPipes a download into a shellAGENTS.md

litellm

BerriAI/litellm/AGENTS.md

maintain/change - modern In descending order of importance When adding new features, add meaningful tests. Don't add tests that don't check anything substantial and is there just to make

BerriAIAGENTS.md

litellm

BerriAI/litellm/.circleci/AGENTS.md

runs only on its schedule, so the API pipelines that set `run_migration_tests` or `routing_parity_base` would stop running it. If main stops getting integration runs, check that

BerriAIAGENTS.md

litellm / litellm-rust

BerriAI/litellm/litellm-rust/AGENTS.md

only delegates, and spell each variant with explicit `#[strum(serialize = "...")]` instead of `serialize_all` ## Test placement - Never create a `tests.rs` (or `test.rs`) file under `src/`, and never `#[path = "tests.rs

BerriAIAGENTS.md

litellm / tests

BerriAI/litellm/tests/AGENTS.md

Tests Nothing on the other side of the call: `tests/unit`. A proxy we start with an upstream we script: `tests/integration`. Someone else's service with real credentials: `tests/e2e`. Tests

No other project uses it yet

penpotAGENTS.md

penpot

penpot/penpot/AGENTS.md

only via the `update-changelog` skill flow or on explicit user request. - **Never pipe test output directly to filters** (`| head`, `| tail`, `| grep`, etc.). Always redirect to a file first: `command

makeplaneReads credentialsAGENTS.md

plane

makeplane/plane/AGENTS.md

proper error types, log errors appropriately - **State Management**: MobX stores in `packages/shared-state`, reactive patterns - **Testing**: All features require unit tests, use existing test framework per package - **Components**: Primitives come from

No other project uses it yet

pi-holeAGENTS.md

pi-hole

pi-hole/pi-hole/AGENTS.md

assets installed onto the system - `gravity.sh` - builds `gravity.db` from configured blocklists - `manpages/` - man pages - `test/` - BATS test suite, run inside distro-specific Docker containers ## Dev environment tips - You need Docker

rcloneAGENTS.md

rclone

rclone/rclone/AGENTS.md

that you, the human submitter, understand every line you propose and have compiled and tested it against real rclone code - not just generated it. See the "AI-assisted contributions" section

No other project uses it yet

crewAIIncAGENTS.md

crewAI

crewAIInc/crewAI/AGENTS.md

practices and idiomatic patterns. 2. Maintain existing code structure and organization. 3. Write unit tests for new functionality focusing on behaivor and not implementation. 4. Document public APIs and complex

No other project uses it yet

spring-projectsAGENTS.md

spring-framework

spring-projects/spring-framework/AGENTS.md

artifacts target Java 17+. - Scope builds to the modules you touched: `./gradlew :spring-webmvc:test`, a single test with `--tests `. - Run `./gradlew : :check` before finishing: it runs tests and Checkstyle

No other project uses it yet

railsAGENTS.md

rails

rails/rails/AGENTS.md

them should not break others unless there's an explicit dependency. ## Testing Commands ### Running Tests in a Component From within the component directory (preferred method): ```bash cd actionview && bin/test

No other project uses it yet