How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
logancyangAGENTS.mdlogancyang/obsidian-copilot/AGENTS.md
same-callable groups only when a material test-lifecycle constraint makes merging misleading, and document that reason next to the groups. Write `it(...)` descriptions that state the observable behavior without
VercelAGENTS.mdvercel-labs/native/AGENTS.md
schema.native-sdk.dev`. - `examples/` — the showcase apps, many predating the JSON default (`app.zon` + `src/`). - `docs/` — the documentation site; `docs/AGENTS.md` has its MDX conventions. - `skills/` and `skill-data/` — the agent skills
mufeedvhAGENTS.mdmufeedvh/code2prompt/AGENTS.md
crates/code2prompt-core/**` → `verify-core` - `crates/code2prompt/**` → `verify-cli` - `crates/code2prompt-python/**` → `verify-python` - `website/**` → `verify-website` - Public behavior/docs/comments → `documentation` A change can require several verification skills. Root `cargo test` does not exercise the Python
trailofbitsAGENTS.mdtrailofbits/skills/AGENTS.md
Contributing Skills ## Resources **Official Anthropic documentation (always check these first):** - [Claude Code Plugins](https://code.claude.com/docs/en/plugins) - [Agent Skills](https://code.claude.com/docs/en/skills) - [Best Practices](https://code.claude.com/docs/en/skills#best-practices) - [Skill Authoring Best Practices
NVIDIAAGENTS.mdNVIDIA/warp/AGENTS.md
devices). ## Docstrings Follow Google-style docstrings. Use doctest for code examples where practical. - Document `__init__` parameters in the class docstring, not the `__init__` method - Don't repeat default values from
tw93AGENTS.mdtw93/Waza/AGENTS.md
codex plugin list`. - Non-trivial diffs: run the review workflow before release handoff. - Documentation-only changes: check internal links and command names. ## Commit And Release - Commit convention: `{type}: {description}` where
grabAGENTS.mdgrab/cursor-talk-to-figma-mcp/AGENTS.md
latest ``` ## Agent Notes - Always call `join_channel` before issuing any Figma commands - Call `get_document_info` first to understand the design structure - Use `read_my_design` or `get_selection` before
open-multi-agentAGENTS.mdopen-multi-agent/open-multi-agent/AGENTS.md
lazily with dynamic `import()`. Do not maintain a fixed dependency or adapter count in documentation. - OpenTelemetry APIs, SDKs, semantic-convention packages, and exporters belong in `@open-multi-agent/otel`, never
olimorrisAGENTS.mdolimorris/codecompanion.nvim/AGENTS.md
NEVER create files unless absolutely necessary - ALWAYS prefer editing existing files - NEVER proactively create documentation files - ALWAYS keep memory in the current working directory and `memories/` folder ### Self-improvement loop
OpenAIAGENTS.mdopenai/plugins/plugins/build-web-apps/skills/react-best-practices/AGENTS.md
React Best Practices **Version 1.0.0** Vercel Engineering January 2026 > **Note:** > This document is mainly for agents and LLMs to follow when maintaining, > generating, or refactoring React and Next.js codebases. Humans
OpenAIAGENTS.mdopenai/plugins/plugins/build-web-apps/skills/supabase-best-practices/AGENTS.md
Usage 1. Read `SKILL.md` for the main skill instructions 2. Browse `references/` for detailed documentation on specific topics 3. Reference files are loaded on-demand - read only what you need
OpenAIAGENTS.mdopenai/plugins/plugins/vercel/skills/react-best-practices/AGENTS.md
React Best Practices **Version 1.0.0** Vercel Engineering January 2026 > **Note:** > This document is mainly for agents and LLMs to follow when maintaining, > generating, or refactoring React and Next.js codebases. Humans
Devin-AXISAGENTS.mdDevin-AXIS/iPolloWork/AGENTS.md
repository root limited to public launchers, workspace configuration, and legal, community, or primary project documents. - Put engineering documents and generated reports in `docs/`, product and architecture plans in `specs/`, automation
GreptimeTeamAGENTS.mdGreptimeTeam/greptimedb/AGENTS.md
bulk unless the user explicitly requests it. - Update generated artifacts only through the generators documented in [`.agents/generated-files.md`](.agents/generated-files.md). ## Validation by change type Use the narrowest command that covers the change
Human-Agent-SocietyAGENTS.mdHuman-Agent-Society/reef/AGENTS.md
these rules are not all checked mechanically. - Before submitting a pull request that changes documentation, complete the [Documentation review checklist](#documentation-review-checklist) and fix any issues. Review the resulting
GoogleAGENTS.mdgoogle/perfetto/docs/AGENTS.md
Perfetto Project Development Guidelines for AI Agents This document provides essential instructions and best practices for developing in the Perfetto codebase. Adhere to these guidelines to ensure consistency and quality
tech-leads-clubAGENTS.mdtech-leads-club/agent-skills/AGENTS.md
markdown body ├── scripts/ # Optional executable scripts ├── templates/ # Optional file templates └── references/ # Optional on-demand documentation ``` Always use the Nx generator (`nx g @tech-leads-club/skill-plugin:skill`) to create skills
SentryAGENTS.mdgetsentry/XcodeBuildMCP/AGENTS.md
format npm run build npm test ``` 4. Update `CHANGELOG.md` under `## [Unreleased]` 5. Update documentation if adding or modifying features 6. Clone and test against example projects (e.g., `XcodeBuildMCP-iOS-Template
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/agent-governance-rust/AGENTS.md
dependencies without a clear OSS need. - Keep crates.io metadata aligned with the repository and documentation. - Credential boundary functions (`is_left_boundary_char` / `is_right_boundary_char` in `redactor.rs`) must only
MicrosoftAGENTS.mdmicrosoft/agent-governance-toolkit/AGENTS.md
unrelated changes into docs-only or example-only PRs. - Preserve honesty in docs: document shipped behavior, not aspirational behavior. ## Spam / SEO Outreach Filtering Close or ignore PRs, issues, and discussions
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.
