AGENTS.md examples from real projects

steipeteAGENTS.md

CodexBar

steipete/CodexBar/AGENTS.md

first validated session. Restrict a provider to a browser subset only with a documented technical reason next to the code

No other project uses it yet

renovatebotAGENTS.md

renovate

renovatebot/renovate/AGENTS.md

multiple hosting platforms (GitHub, GitLab, Bitbucket, Azure DevOps, Gitea, Forgejo, Gerrit, etc.). ## Development Documentation The **./docs/development/** directory contains detailed documentation for developers, like style guides, testing guidelines, and configuration options

2025EmmaAGENTS.md

vibe-coding-cn

2025Emma/vibe-coding-cn/AGENTS.md

README.md` 给出全貌，`Makefile` 封装日常命令，`CONTRIBUTING.md` 说明贡献流程，`LICENSE` 载明协议。保持根目录扁平，避免巨石文件。 - 多语言 i18n：`i18n/ /` 统一三层结构（documents / prompts / skills）。现有语言：中文 `zh`、英文 `en`、希伯来语 `he`，以及高频/常用的

NVIDIAAGENTS.md

NemoClaw

NVIDIA/NemoClaw/AGENTS.md

maintainer, and validation plan. `Request changes`, `Defer`, and `Decline` do not authorize implementation. Small documentation corrections and low-risk fixes do not require this decision. If the product decision

No other project uses it yet

NVIDIAAGENTS.md

NemoClaw

NVIDIA/NemoClaw/docs/AGENTS.md

Documentation Agent Guide ## Role You are a documentation engineer and writer for NemoClaw public-facing documentation. Treat `docs/` as the source of truth for published content and AI-agent Markdown

No other project uses it yet

NVIDIAAGENTS.md

NemoClaw / fern

NVIDIA/NemoClaw/fern/AGENTS.md

Fern Documentation Agent Guide You are a documentation engineer and writer responsible for the NemoClaw Fern site shell. Use this guide when editing files under `fern/`. ## Role - Maintain the Fern

No other project uses it yet

NVIDIAAGENTS.md

NemoClaw / messaging

NVIDIA/NemoClaw/src/lib/messaging/AGENTS.md

request maintainer direction, or route the integration through [Community Solutions](../../../docs/resources/community-contributions.mdx). Do not document the integration as NemoClaw behavior. Derive the channel contract from authoritative upstream documentation and source before

No other project uses it yet

mochajsAGENTS.md

mocha

mochajs/mocha/AGENTS.md

rule and location before changing lint configuration or adding suppressions. - Docs-related workflows where documentation generation succeeds but a subsequent static site or bundler step (for example, `astro build`) fails

vectordotdevAGENTS.md

vector

vectordotdev/vector/AGENTS.md

files - `debian/`, `rpm/` - Linux package configurations - `/scripts/` - Build, test, and deployment automation - `/docs/` - Developer documentation - `/tests/` - Integration and E2E tests ## Development Workflow ### Iterative Development Process When working on Vector

No other project uses it yet

vectordotdevAGENTS.md

vector / website

vectordotdev/vector/website/AGENTS.md

website make serve ``` The local site is available at <http://localhost:1313>. Build CUE documentation from the `website/` directory: ```bash make cue-build ``` After editing Markdown, run `make check-markdown

No other project uses it yet

react-grid-layoutAGENTS.md

react-grid-layout

react-grid-layout/react-grid-layout/AGENTS.md

first The module structure, public API surface, data models, and recent behavioral changes are documented in the generated maps in `codemaps/`. Load them before making edits: - `codemaps/architecture.md` — module boundaries, package

No other project uses it yet

RustPythonAGENTS.md

RustPython

RustPython/RustPython/AGENTS.md

Agent Instructions for RustPython This document provides guidelines for AI coding agents (GitHub Copilot, Claude Code, Gemini, etc.) contributing to the RustPython project. ## Project Overview RustPython is a Python

No other project uses it yet

HomebrewAGENTS.md

homebrew-cask

Homebrew/homebrew-cask/AGENTS.md

Agent Instructions for homebrew-cask This document helps coding agents produce high-quality PRs for Homebrew Cask contributions. ## Before Any PR 1. **Check for existing PRs** for the same cask

mediar-aiAGENTS.md

screenpipe

mediar-ai/screenpipe/AGENTS.md

review is the bottleneck. For ordinary desktop React/layout changes, use the browser-mock loop documented in `apps/screenpipe-app-tauri/README.md`; do not build Tauri merely for UI validation. Drive the real app only

MicrosoftAGENTS.md

onnxruntime

microsoft/onnxruntime/AGENTS.md

that is not clear from the immediate context. Do not narrate obvious code or document the sequence of approaches taken to reach the current implementation; that history belongs

dyad-shAGENTS.md

dyad

dyad-sh/dyad/AGENTS.md

users, such as: - Claude settings, commands, or agent configuration - Linting or test setup changes - Documentation-only changes - CI/build configuration updates

No other project uses it yet

GoogleAGENTS.md

adk-python

google/adk-python/AGENTS.md

invocation lifecycle, please refer to the `adk-architecture` skill and the referenced documentation therein. ## ADK Knowledge, Architecture, and Style Skills related to ADK development are in `.agents/skills/`. ## Project Architecture

citrolabsAGENTS.md

ego-lite

citrolabs/ego-lite/AGENTS.md

acorn at runtime to power `help()` — JSDoc on exported helpers is therefore user-facing documentation. Data flow: `stdin JS` → `runMain()` → `helperContext()` helpers → browser runtime/CDP → snapshot or DOM/AX resolution → optional site

No other project uses it yet

handsontableAGENTS.md

handsontable / handsontable

handsontable/handsontable/handsontable/AGENTS.md

token, once merged, is never removed or renamed. Rules: `src/featureManifest/AGENTS.md`. - No global `window`, `document`, `console` - use `this.hot.rootWindow`, `this.hot.rootDocument`, and helpers from `src/helpers/console.ts` - **Shadow DOM / sandboxed hosts:** never decide

handsontableAGENTS.md

handsontable / visual-tests

handsontable/handsontable/visual-tests/AGENTS.md

tests/cross-browser/` - Examples for testing live in `examples/next/visual-tests/ /demo/` (the docs tree `examples/next/docs/` is the documentation examples; nothing here serves it) ## Decision rule A screenshot asserts pixels