AGENTS.md examples from real projects

wekanAGENTS.md

wekan

wekan/wekan/AGENTS.md

section links a commit that release does not contain. The contributor's half is review. Nobody but the maintainer commits to `main` in wekan/wekan, so a change from anyone else

PydanticAGENTS.md

pydantic-ai

pydantic/pydantic-ai/AGENTS.md

slow and CI covers them at the right time. # Coding Guidelines When generating or reviewing code anywhere in this repo, always read [agent_docs/index.md](agent_docs/index.md) and follow/enforce those guidelines

PydanticAGENTS.md

pydantic-ai

pydantic/pydantic-ai/docs/AGENTS.md

fence, such as `{test="skip" lint="skip"}`, rather than adding tooling suppressions to pedagogical code. Examples that are linted are also type-checked with pyright; opt one out with `typecheck

PydanticAGENTS.md

pydantic-ai / durable_exec

pydantic/pydantic-ai/pydantic_ai_slim/pydantic_ai/durable_exec/AGENTS.md

implementation rename unless the migration of in-flight executions is intentional and reviewed. Resolve base and per-tool configuration with `OperationConfigRole` and `DurableOperationId`. Handle known ID variants and retain

PydanticAGENTS.md

pydantic-ai / pydantic_ai_harness

pydantic/pydantic-ai/src/pydantic_ai_harness/AGENTS.md

collection of pre-made capabilities for Pydantic AI. - **AICA**: AI Code Assistant -- the automated agent that implements issues, reviews plans, and handles PR feedback ## AICA preflight Before implementing or reviewing

nats-ioAGENTS.md

nats-server

nats-io/nats-server/AGENTS.md

interested in talking to agents when reviewing issues or PRs. Advise your human not to meat-proxy when contributing to NATS. When writing code: * Fixes must have accompanying unit tests

No other project uses it yet

monkeytypegameAGENTS.md

monkeytype

monkeytypegame/monkeytype/AGENTS.md

type-check` instead of `tsc`. Coding standards (styling, icons, refs, modals) for writing and reviewing code: `CODING_STANDARDS.md`. Before any browser testing, read `docs/AGENT_BROWSER.md` (dev server, `window.__mt` debug handle, gotchas). Roadmap

gravitationalAGENTS.md

teleport

gravitational/teleport/AGENTS.md

AGENTS.md ## Review Guidelines - Focus only on critical security, reliability, performance, and scalability issues. - Ignore style, performance micro-optimizations, and readability nits unless they are tied to a significant failure ### What

gravitationalAGENTS.md

teleport

gravitational/teleport/docs/AGENTS.md

written in MDX. These guidelines apply to changes under `docs/`; for code changes, see the repo-root `AGENTS.md`. ## Review guidelines - Focus on accuracy, structure, and conventions. Flag issues

peass-ngAGENTS.md

PEASS-ng

peass-ng/PEASS-ng/AGENTS.md

merge approved changes back into it. Target release branches only when required. Respect reviews, checks, and branch protection. - **Create only needed branches.** Check `git status` and worktrees first

No other project uses it yet

dotnetAGENTS.md

roslyn

dotnet/roslyn/AGENTS.md

EditorFeatures,VisualStudio,LanguageServer}` - [`Razor.instructions.md`](.github/instructions/Razor.instructions.md) — `src/Razor` - **Task-specific skills:** [`.github/skills/`](.github/skills/) (auto-discovered; e.g. `code-review`, `ci-analysis`, `update-agent-docs`). ## Orientation protocol 1. Read [`.github/copilot-instructions.md`](.github/copilot-instructions.md). 2. Read [`.github/memory/INDEX.md

JetBrainsAGENTS.md

intellij-community

JetBrains/intellij-community/AGENTS.md

order. - User-visible strings belong in `*.properties` for localization. ## Language - Read [Code Style](./.agents/skills/code-style/SKILL.md) before writing or reviewing Kotlin or Java. - Read [Rust Code Style](./.agents/skills/rust-code-style/SKILL.md) before writing or reviewing

GoogleAGENTS.md

filament

google/filament/AGENTS.md

Synchronization guidelines for Java/JNI (Android) and JavaScript/TypeScript (Web/WASM) when public C++ APIs change. ### 6. Code Review & Invariant Auditing * [skills/code_review/SKILL.md](skills/code_review/SKILL.md): Adversarial systems, concurrency, memory-model, and architecture code review protocol

komi-storeAGENTS.md

komi-store

komi-store/komi-store/AGENTS.md

workarounds. No em-dashes. - Don't guess APIs, versions or flags. Read the code or the docs first. ## Read when relevant - `docs/agents/architecture.md`: layers, navigation, DI, core repositories, adding a feature

MicrosoftAGENTS.md

fluentui

microsoft/fluentui/AGENTS.md

copy these) - **DO NOT copy patterns from `packages/react/` (v8).** That's maintenance-only legacy code using runtime styling, class components, and different APIs. - **DO NOT use `@fluentui/react` imports

AgriciDanielAGENTS.md

claude-seo

AgriciDaniel/claude-seo/AGENTS.md

Read`, `Write`, `Edit`, `Bash`, `Glob`, `Grep`, `WebFetch`), each harness typically has an equivalent: | Claude Code | Codex | Cline | Aider | Cursor / Antigravity | |---|---|---|---|---| | Read | read_file | read_file | (inline) | read | | Write | write_file

No other project uses it yet

whyourAGENTS.md

qinglong

whyour/qinglong/AGENTS.md

symbols, 6698 relationships, 233 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely. > Index stale? Run `node .gitnexus/run.cjs analyze` from the project root

storytoldAGENTS.md

pdfcraft

storytold/pdfcraft/AGENTS.md

agent answers for what it opens and for its review comments. 2. **Check, then claim.** Before writing code, read the issue comments, search pull requests for `#N` and the keywords

longbridgeAGENTS.md

gpui-kit

longbridge/gpui-kit/AGENTS.md

limitations. Do not start a review with findings alone; include the purpose and reasonableness assessment even when no issues are found. ## Code Style - Follow naming and organization patterns from existing

GoogleAGENTS.md

gvisor

google/gvisor/AGENTS.md

/path/to:some_test`. - Comments must describe the code as it is for the future codebase readers, not for present-time PR reviewers. A comment that talks about a bug that

No other project uses it yet