How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
DeepSeekAGENTS.mddeepseek-ai/deepseek-harness/.agents/notes/AGENTS.md
proposals and decision records that preserve rationale, alternatives, consequences, and required verification. Follow the [documentation standard](../../docs/AGENTS.md) and the [Agent Note rules](README.md). **Every new Agent Note triggers a supersession
DeepSeekAGENTS.mddeepseek-ai/deepseek-harness/.agents/notes/archived/AGENTS.md
repair, delete, or move a sealed artifact; use an active Agent Note or current documentation for new decisions and facts. The archival change may only relocate a complete English/Chinese/sidecar triplet
DeepSeekAGENTS.mddeepseek-ai/deepseek-harness/.agents/notes/implemented/AGENTS.md
Implemented Agent Notes These Agent Notes describe shipped decisions. Follow the [root instructions](../../../AGENTS.md), [documentation standard](../../../docs/AGENTS.md), and [Agent Note format](../README.md#the-file-format); `verify-agent-note-format` gates
DeepSeekAGENTS.mddeepseek-ai/deepseek-harness/docs/AGENTS.md
AGENTS.md — The documentation standard This file defines document structure, Markdown tiers, writing rules, and `verify-doc-budgets` ceilings. Use [dsh-doc](../.agents/skills/dsh-doc/SKILL.md) for placement and validation, and [dsh-prose-standard
DeepSeekAGENTS.mddeepseek-ai/deepseek-harness/packages/AGENTS.md
subsystem ownership through a canonical English page link or justified [exemption](../scripts/verify-subsystem-pages.ts). - Package READMEs document model, token, and KV-cache effects using the [canonical Model Experience format](../docs/cookbook/adding-a-package.md#4-write
DeepSeekAGENTS.mddeepseek-ai/deepseek-harness/packages/experimental/AGENTS.md
through `devDependencies`; examples may load them explicitly. - Experimental status does not relax engineering, security, documentation, lifecycle, testing, invariant, or snapshot requirements. - Publishing an experimental package does not promote
DeepSeekAGENTS.mddeepseek-ai/deepseek-harness/website/AGENTS.md
AGENTS.md — Documentation website adapter Follow the [root instructions](../AGENTS.md), the [documentation standard](../docs/AGENTS.md), and the [documentation workflow](../.agents/skills/dsh-doc/SKILL.md). ## Keep documentation content out of this tree `website/` owns only VitePress configuration
MicrosoftAGENTS.mdmicrosoft/vscode/src/vs/platform/agentHost/AGENTS.md
Multi-Chat Architecture > Node runtime service construction is documented separately in [`node/serviceBootstrapping.md`](node/serviceBootstrapping.md). > Host startup timings, process-lifetime correlation, and session workload counts are documented in [`PERFORMANCE.md`](PERFORMANCE.md). > **Status: COMPLETE
MicrosoftAGENTS.mdmicrosoft/vscode/src/vs/platform/agentHost/node/copilot/prompts/AGENTS.md
tools registered by Agent Host. This internal debugging setting assumes those values use the documented string shape. > **Launch-time freeze.** The SDK accepts a system message only at session create/resume
Significant-GravitasAGENTS.mdSignificant-Gravitas/AutoGPT/AGENTS.md
calling `onKeyDown` as a safety net; every handler on a raw ` `/` `, a container, or `document` must use `isKey` itself. That atom-level guard is deliberately unconditional, so a modifier chord
Significant-GravitasAGENTS.mdSignificant-Gravitas/AutoGPT/.claude/skills/vercel-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
Significant-GravitasAGENTS.mdSignificant-Gravitas/AutoGPT/docs/AGENTS.md
Documentation Guidelines ## Block Documentation Manual Sections When updating manual sections (` `) in block documentation files (e.g., `docs/integrations/basic.md`), follow these formats: ### How It Works Section Provide a technical explanation
langgeniusAGENTS.mdlanggenius/dify/api/AGENTS.md
explicit and bounded. Do not perform external I/O inside an open transaction unless a documented consistency contract requires it. - Read configuration through `configs.dify_config`, access storage through `extensions.ext_storage.storage`, and route
langgeniusAGENTS.mdlanggenius/dify/dify-agent/AGENTS.md
package's `uv` environment and Pydantic v2 APIs. Inspect current dependency source or official documentation before integrating, implementing, or mocking an API whose runtime contract is not established locally. ## Tests
VercelAGENTS.mdvercel/next.js/test/AGENTS.md
specific to self-hosted behavior; even then, prefer an explicit deploy-mode assertion that documents the different deployed semantics
MicrosoftAGENTS.mdmicrosoft/PowerToys/AGENTS.md
Top-level AI contributor guidance for developing PowerToys - a collection of Windows productivity utilities
OpenAIAGENTS.mdopenai/codex/AGENTS.md
methods, newtypes, or other idiomatic Rust API shapes when they keep the callsite self-documenting. - When you cannot make that API change and still need a small positional-literal callsite
OpenAIAGENTS.mdopenai/codex/codex-rs/tui/src/bottom_pane/AGENTS.md
explanation of the current behavior. - Keep implementations/docstrings aligned unless a divergence is intentional and documented. Practical check: - After edits, sanity-check that docs mention only APIs/behavior that exist in code
SupabaseAGENTS.mdsupabase/supabase/AGENTS.md
Structure | Directory | Purpose | | ------------------------ | ------------------------------------------------------------------------------------------------------------------ | | `apps/studio` | Supabase Studio/Dashboard — has its own `apps/studio/AGENTS.md` (see below) | | `apps/docs` | Documentation site — Next.js app router, MDX (port 3001, served under `/docs`) — has its own `apps/docs/AGENTS.md` | | `apps/www` | Marketing
SupabaseAGENTS.mdsupabase/supabase/apps/docs/AGENTS.md
length, brevity - `style-guide/02-elements.md` — admonitions, code blocks, procedures, tabs, images - `style-guide/03-page-structure.md` — document type, section grouping, chunking Load the file you need rather than the whole directory
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.
