How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
SupabaseAGENTS.mdsupabase/supabase/apps/kb/AGENTS.md
directory of the project pnpm dev:kb # From the apps/kb directory pnpm dev ``` ### Astro documentation Full documentation: https://docs.astro.build Consult these guides before working on related tasks: - [Adding pages, dynamic
addyosmaniAGENTS.mdaddyosmani/agent-skills/docs/agents.md
this file. 5. If the persona enables a new orchestration pattern, document it in `references/orchestration-patterns.md` rather than inventing the pattern in the persona file itself
nexu-ioAGENTS.mdnexu-io/open-design/plugins/AGENTS.md
source_kind='bundled'`. - `plugins/spec/` is the portable plugin specification and authoring kit. It is documentation, starter material, and example source for contributors and external agents; it must not be treated
nexu-ioAGENTS.mdnexu-io/open-design/skills/AGENTS.md
category filter row in Integrations → Skills (e.g. `image-generation`, `video-generation`, `audio-music`, `slides`, `documents`, `design-systems`, `figma`, `animation-motion`, `3d-shaders`, `diagrams`, `creative-direction`, `marketing-creative`, `screenshots`, `web-artifacts
ruvnetAGENTS.mdruvnet/RuView/.claude/commands/monitoring/agents.md
does NOT access files directly - ❌ The tool does NOT execute commands ## See Also - Main documentation: /CLAUDE.md - Other commands in this category - Workflow examples in /workflows
infiniflowAGENTS.mdinfiniflow/ragflow/AGENTS.md
build.sh --test`; that is expected, not an external service. ## Working Rules - When reviewing documentation or code, inspect the full affected path and report all verifiable findings in one review
koala73AGENTS.mdkoala73/worldmonitor/AGENTS.md
tauri/`; [architecture](ARCHITECTURE.md) | Focused Rust checks or `npm run test:sidecar` | | Tests and documentation | `tests/`, `e2e/`, `docs/`; [verification guide](CONTRIBUTING.md#verify-the-changed-path) | Relevant existing test or docs check
koala73AGENTS.mdkoala73/worldmonitor/public/agents.md
Machine interfaces, authentication, request policy, and rate limits.
bytedanceAGENTS.mdbytedance/deer-flow/backend/AGENTS.md
channels) │ │ └── channels/ # IM platform integrations │ ├── scripts/benchmark/ # Standalone reproducible backend benchmarks │ ├── tests/ # Test suite │ └── docs/ # Documentation ├── frontend/ # Next.js frontend application └── skills/ # Agent skills directory ├── public/ # Public skills (committed) └── custom/ # Custom skills
stablyaiAGENTS.mdstablyai/orca/AGENTS.md
src/renderer/src/components/ui/`. Don't invent new color values, font sizes, or shadow tiers when a documented one already covers the role. When STYLEGUIDE.md is silent, follow the resolution order
ElasticAGENTS.mdelastic/elasticsearch/AGENTS.md
rest-api-spec`: JSON spec definitions for the public REST API endpoints. * `docs`: Project documentation. * `distribution`: Logic for building distribution packages. * `x-pack`: Modules, plugins, and commercial features under
ElasticAGENTS.mdelastic/elasticsearch/docs/AGENTS.md
will only validate that subdirectory's links and may silently miss errors in cross-document references. ```bash # From /path/to/elasticsearch (repo root): docs-builder
career-ops-hqAGENTS.mdcareer-ops-hq/career-ops/AGENTS.md
Layer (NEVER auto-updated; personalization goes HERE):** `cv.md`, `config/profile.yml`, `modes/_profile.md`, `modes/_custom.md`, `article-digest.md`, `portals.yml`, `data/*`, `documents/*`, `reports/*`, `output/*`, `interview-prep/*` - **System Layer (auto-updatable; DON'T put user data here):** `modes/_shared.md
code-yeongyuAGENTS.mdcode-yeongyu/oh-my-openagent/docs/AGENTS.md
docs/ — User-Facing Documentation **Generated:** 2026-08-24 / f3642fcda ## OVERVIEW 30 tracked Markdown files across 6 subdirectories (guide 7, reference 18, examples 3 JSONC, legal 2, templates 1, troubleshooting
code-yeongyuAGENTS.mdcode-yeongyu/oh-my-openagent/packages/AGENTS.md
packages by hand. Either share via a core package or accept the duplication and document it. - Never modify `bin/oh-my-opencode.js` inside a platform launcher package - regenerate it through `script/build-binaries.ts
ClineAGENTS.mdcline/cline/sdk/AGENTS.md
Development reference for the Cline SDK workspace.
ClineAGENTS.mdcline/cline/sdk/packages/llms/AGENTS.md
Development guidance for the @cline/llms package.
mem0aiAGENTS.mdmem0ai/mem0/docs/AGENTS.md
Documentation (`docs/`) Mintlify site published at https://docs.mem0.ai. ## Commands ```bash make docs # from repo root cd docs && mintlify dev ``` ## Structure | Path | Contents | |------|----------| | `api-reference/` | Platform REST endpoints | | `open-source/` | Self
mem0aiAGENTS.mdmem0ai/mem0/integrations/AGENTS.md
bundle path in the applicable marketplace files. Preserve the existing public plugin name. 6. Document it under `docs/integrations/` and add the page to `docs/docs.json` and `docs/llms.txt`. 7. Add rows
mem0aiAGENTS.mdmem0ai/mem0/skills/AGENTS.md
overview of the pipeline. - Invocation, modes, exit codes. Everything else, meaning full step mechanics, document templates, and verbatim subagent prompts, goes in `references/` with a link from the overview. Current
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.
