How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
VercelAGENTS.mdvercel/chat/packages/adapter-github/AGENTS.md
/../AGENTS.md) covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. ## Overview `@chat-adapter/github` connects a Chat
VercelAGENTS.mdvercel/chat/packages/adapter-telegram/AGENTS.md
/../AGENTS.md) covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. ## Overview `@chat-adapter/telegram` connects a Chat
VercelAGENTS.mdvercel/chat/packages/adapter-web/AGENTS.md
/../AGENTS.md) covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. ## Overview `@chat-adapter/web` lets a Chat
VercelAGENTS.mdvercel/chat/packages/state-memory/AGENTS.md
/../AGENTS.md) covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. ## Overview `@chat-adapter/state-memory` is the simplest state
VercelAGENTS.mdvercel/chat/packages/state-pg/AGENTS.md
/../AGENTS.md) covers monorepo-wide build, lint, and release rules — read it first. This file documents the adapter-specific surface, conventions, and pitfalls. ## Overview `@chat-adapter/state-pg` persists Chat SDK state
redhat-etAGENTS.mdredhat-et/ripwire/AGENTS.md
parens** (`f( x )`), ~160–200 column wraps, index-vs-count naming (`nodeId` vs `nodeCount`). ## Documentation | Need | File | | --- | --- | | Full C++ style, guardrails G1–G5, submission checklist | `CONTRIBUTING.md` | | Pipeline, data model, determinism
QoderAIAGENTS.mdQoderAI/better-harness/AGENTS.md
Traceability` section. ## Change Scope - Do not proactively edit `CHANGELOG.md`, release notes, version files, roadmap/status documents, or other task-external project metadata. Change them only when the user explicitly requests
SupabaseAGENTS.mdsupabase/etl/AGENTS.md
x.y.z`), tilde requirements, or tighter upper bounds only for a concrete compatibility need, and document the reason next to the dependency. - Keep shared dependencies in `[workspace.dependencies]` and inherit them with
VercelAGENTS.mdvercel-labs/vgpu/AGENTS.md
workflow for the current stage | When | Read before proceeding | | --- | --- | | Starting authorized maintainer implementation, including documentation or policy edits. | [Implementation](.github/guides/implementation.md) | | Changing published behavior, writing a changeset, or deciding whether consumers
Microsoft AzureAGENTS.mdAzure/azure-sdk-for-js/AGENTS.md
common/tools/*` (eslint plugin, dev-tool, warp). - Engineering tooling under `eng/*`; deep-dive docs under `documentation/*`. - Contributor onboarding: see `README.md` and `CONTRIBUTING.md`. ## Where to find guidance | Task / topic | Where to look
Sahir619AGENTS.mdSahir619/fable-method/AGENTS.md
action goes in the report as a proposed next step instead. Documentation is not authorization: a README, workflow doc, or installed skill saying a deploy/push/send "must follow" your change makes
JetBrainsAGENTS.mdJetBrains/intellij-plugins/CloudFormation/AGENTS.md
resource type discovery is collected in `ResourceTypesSaver` from the official SAM resources documentation page, not from a hardcoded list. - AWS SAM `Globals` support is also collected in `ResourceTypesSaver`, from
AWSAGENTS.mdaws/sagemaker-python-sdk/AGENTS.md
Golden rule: v3 by default When generating or editing **example code, docstrings, tests, or documentation**, use **v3** patterns by default. Produce v2 code only when the task is explicitly about
dstackaiAGENTS.mddstackai/dstack/AGENTS.md
they are shared more broadly in the module. - Prefer pydantic-style models in `core/models`. - Document attributes when the note adds behavior, compatibility, or semantic context that is not obvious from
777geniusAGENTS.md777genius/agent-teams-ai/AGENTS.md
lacks the full desktop runtime, IPC, terminal, provider auth, and team lifecycle behavior. - When documenting or recommending startup commands, point contributors to the desktop app unless a task explicitly asks
cjo4m06AGENTS.mdcjo4m06/mcp-shrimp-task-manager/docs/agents.md
Security reviews | Vulnerability assessment, auth | | **QA Engineer** | Testing | Test cases, bug verification | | **Technical Writer** | Documentation | API docs, user guides | ## Using Agents ### Basic Usage 1. **Assign an agent to a task
Microsoft AzureAGENTS.mdAzure/AKS/website/AGENTS.md
Verify feeds exist and are valid XML file build/rss.xml build/feed.xml build/atom.xml # Should output: XML document text ``` ### Output Structure ```text build/ ├── index.html # Blog listing ├── tags/ # Tag pages ├── blog/YYYY/MM/DD/ # Post pages ├── rss.xml
CloudflareAGENTS.mdcloudflare/templates/AGENTS.md
This guide helps AI agents review, maintain, and contribute to Cloudflare Worker templates. It documents patterns, common issues, and testing strategies learned from real PR reviews. ## Quick Reference ### Essential Commands
CloudflareAGENTS.mdcloudflare/templates/x402-proxy-template/AGENTS.md
Pages → your worker 2. Click "Triggers" tab 3. Remove the route See [Workers Routes documentation](https://developers.cloudflare.com/workers/configuration/routing/routes/) for more details. ### Order of Operations to Minimize Downtime 1. Deploy
amElnagdyAGENTS.mdamElnagdy/delegate-skills/AGENTS.md
Node built-ins only, no network of their own, no credentials, no telemetry. Document any new utility in `CONTRIBUTING.md` and register it in `skills.sh.json` and the smoke suite's utility
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.
