AGENTS.md examples from real projects

remix-runAGENTS.md

remix

remix-run/remix/AGENTS.md

review focused UI library examples, including an adversarial product UX review. ## App And Demo Skills For working on Remix code in demos or writing Remix app code, use the root

VercelAGENTS.md

agent-skills / vercel-optimize

vercel-labs/agent-skills/skills/vercel-optimize/AGENTS.md

projects that are not deployed on Vercel, greenfield projects with no traffic, or general code review. ## Requirements - Node.js 20+ - Vercel CLI with `vercel metrics`, `vercel usage`, `vercel contract`, and `vercel

onyx-dot-appReads credentialsAGENTS.md

onyx

onyx-dot-app/onyx/AGENTS.md

Common tasks table in `.agents/feature-map/INDEX.md`. - Look up a code path in `.agents/feature-map/PATHS.md` to find its component. - The step-by-step review procedure is `.agents/feature-map/VERIFYING.md`. - Onyx overloads words such as Persona

zeroclaw-labsAGENTS.md

zeroclaw

zeroclaw-labs/zeroclaw/AGENTS.md

panic impossible. - Do not suppress unused production code with underscore names or `#[allow(dead_code)]`; remove it, connect it, or track it. Underscore names remain valid for required but intentionally

podman-container-toolsAGENTS.md

podman

podman-container-tools/podman/AGENTS.md

Podman Development  ## Persona This guide is for AI coding assistants (for example Claude, ChatGPT, Copilot). Use it for context on codebase layout, development patterns, testing

lbjlaqAGENTS.md

Antigravity-Manager

lbjlaq/Antigravity-Manager/AGENTS.md

Checks**: Execute only when tagging final releases; should not be executed during daily tasks, code reviews, simple edits, simple debugging, or trivial hardcoded changes. Run on demand before releasing

tirth8205Deletes or force-pushesAGENTS.md

code-review-graph

tirth8205/code-review-graph/AGENTS.md

must push - If push fails, resolve and retry until it succeeds ## MCP Tools: code-review-graph **This project has a knowledge graph. Start with the code-review-graph MCP tools

No other project uses it yet

SigNozAGENTS.md

signoz / frontend

SigNoz/signoz/frontend/AGENTS.md

implement structural fixes. Ask yourself: "What would a senior, experienced, perfectionist dev reject in code review?" Fix all of it. 2. REVIEWABLE FILES: When creating new code, follow the rules

filamentphpAGENTS.md

filament

filamentphp/filament/AGENTS.md

accessibility, and test databases. - **Documentation**: Load [writing-filament-docs](.agents/skills/writing-filament-docs/SKILL.md) when adding, editing, or reviewing developer documentation. - **Documentation screenshots**: Load [capturing-filament-screenshots](.agents/skills/capturing-filament-screenshots/SKILL.md) when adding screenshot examples, changing screenshot

No other project uses it yet

conductor-ossAGENTS.md

conductor

conductor-oss/conductor/AGENTS.md

cautious with external dependencies—prefer well-maintained libraries - Follow secure coding practices for input validation and error handling - Review [SECURITY.md](SECURITY.md) for vulnerability reporting procedures ## Writing Documentation Documentation in this

facebookAGENTS.md

rocksdb

facebook/rocksdb/AGENTS.md

live in `CLAUDE.md`. Read and follow [`CLAUDE.md`](./CLAUDE.md) in full before making changes or reviewing code in this checkout. If there is any ambiguity between this file and `CLAUDE.md`, `CLAUDE.md

yetoneAGENTS.md

magpie

yetone/magpie/AGENTS.md

follow the same page's documentation update, semantic change description, and review rules. ## Code standards Write and review changes against the [code standards](docs/code-standards.md). ## Community PRs Before reviewing a community

No other project uses it yet

OpenAIAGENTS.md

openai-python

openai/openai-python/AGENTS.md

tests, and examples small; alter exported APIs only when explicitly required. ## Security requirements for coding agents Read and apply [contributor security requirements](CONTRIBUTING.md#security-requirements-for-contributions) for credentials, synthetic

No other project uses it yet

FujiwaraChokiReads credentialsAGENTS.md

MoneyPrinterV2

FujiwaraChoki/MoneyPrinterV2/AGENTS.md

CASE` for constants - Keep new business logic in focused modules under `src/`; keep provider/integration code in `src/classes/`. - Prefer small, explicit functions and preserve existing CLI-first behavior. ## Testing Guidelines - There

trycuaAGENTS.md

cua

trycua/cua/AGENTS.md

files canonical instead of duplicating their field lists, polling ladder, or RFC lifecycle here. Coding agents act as workers within that contract, not as a planning authority. GitHub holds

mantinedevAGENTS.md

mantine

mantinedev/mantine/AGENTS.md

available (`command -v codex`). If it is, run `/codex-code-review` to get an automated code review of unstaged changes and apply fixes. ## Code Style **Comments Guidelines:** - **Do not include inline comments

No other project uses it yet

garrytanPipes a download into a shellAGENTS.md

gbrain

garrytan/gbrain/AGENTS.md

gbrain write-request `) before retrying, reporting or moving on. Full contract, transcripts, effects, exit codes and marker grammar: [`docs/protocol/AGENT_OPERATOR_v1.md`](./docs/protocol/AGENT_OPERATOR_v1.md). ## Read this order 1. `./AGENTS.md` (this file) — install + operating protocol

No other project uses it yet

ScrapeGraphAIReads credentialsAGENTS.md

Scrapegraph-ai

ScrapeGraphAI/Scrapegraph-ai/AGENTS.md

AGENTS.md Instructions for AI coding agents (Claude Code, Codex, Cursor, Copilot agents, …) working on **ScrapeGraphAI**. Human contributors should read [CONTRIBUTING.md](CONTRIBUTING.md); everything here is in addition to it. --- ## 1. Golden

nautechsystemsAGENTS.md

nautilus_trader

nautechsystems/nautilus_trader/AGENTS.md

alone. ### Tests - Do not add test-only behavior, branches, attributes, or interfaces to production code. - Do not weaken, remove, bypass, or rewrite tests or required behavior merely to obtain

No other project uses it yet

hectorventAGENTS.md

floci

hectorvent/floci/AGENTS.md

rules below still apply to it. ### General - Use constructor injection - Prefer self-explanatory code over comments - Avoid unnecessary comments - Always use braces in conditionals - Never leave a `catch` block empty