expo
expo/expo/AGENTS.md
first 1. Read [CONTRIBUTING.md](./CONTRIBUTING.md). It is the source for setup, package scripts, tests, documentation, and changesets. Do not copy those steps into a new guide. 2. If the directory
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
expo/expo/AGENTS.md
first 1. Read [CONTRIBUTING.md](./CONTRIBUTING.md). It is the source for setup, package scripts, tests, documentation, and changesets. Do not copy those steps into a new guide. 2. If the directory
HKUDS/DeepTutor/AGENTS.md
responding (Guided Learning — chat loop + mastery tools, gated per topic type) | | `immersive_reading` | responding (document- or timestamp-grounded media reading loop) | | `video_lesson` | code_generation → render_check → render_output (Remotion
CherryHQ/cherry-studio/.agents/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. Humans
Surging17 mentions in 2 weeks
8 projects use a version of this
CherryHQ/cherry-studio/docs/AGENTS.md
AGENTS.md — Documentation These instructions apply to `docs/**`. Read [the documentation governance workflow](../.agents/skills/docs-governance/SKILL.md) before restructuring, auditing, or authoring repository documentation. - Put one fact in one home. Cross-cutting behavior belongs
Steady17 mentions in 2 weeks
No other project uses it yet
roboflow/supervision/AGENTS.md
behavior changes. Skip changelog entries for lint-only, type-only, formatting-only, and pure documentation-only changes. - If work has open PR, changelog entry must link that
Steady7 mentions in 2 weeks
No other project uses it yet
tldraw/tldraw/AGENTS.md
explicitly asked. - Prefer editing existing files over creating new files. Do not add new documentation files unless requested. - Use sentence case for headings, titles, labels, and documentation text. ## Repo overview
No other project uses it yet
QuantumNous/new-api/AGENTS.md
protocol limits, usage sources, defaults, estimation, and settlement details in code comments or technical documentation. Descriptions must be short, equivalent across languages, and free of numeric prices and trailing punctuation
No other project uses it yet
moeru-ai/airi/AGENTS.md
compatibility guards. - If old callers or old data need extended support, write a refactor document with the target shape. Then start another Codex or Claude Code session from the shell
chenglou/pretext/AGENTS.md
Part 2) and the Decisions Log (Part 3). Read the log before reversing a documented decision; code comments that cite it mark where each one applies. A PR's description
Steady25 mentions in 2 weeks
No other project uses it yet
ClickHouse/ClickHouse/docs/AGENTS.md
Treat content between `AUTOGENERATED_START` and `AUTOGENERATED_END` in any documentation page as read-only generated output. Update that generator's source of truth instead of editing the generated region
No other project uses it yet
KRTirtho/spotube/AGENTS.md
plus files copied as is. `:composeApp:renderPackaging ` renders them into `composeApp/build/packaging/ ` (`RenderPackagingTask` in buildSrc documents the template data). Never hand-write versions, checksums or release notes into these files. - Checksums
astral-sh/ruff/AGENTS.md
review discussion. During code review, check the proposed changes against all applicable code, test, documentation, and architectural conventions in this `AGENTS.md`. Report meaningful violations introduced by the changes
pandas-dev/pandas/AGENTS.md
tasks defined in [pixi.toml](pixi.toml) for all workflows (building pandas, testing, type checking, building documentation, running benchmarks). Linting checks require [pre-commit](https://pre-commit.com/), installed in a conda
No other project uses it yet
Homebrew/brew/AGENTS.md
with e.g. `gh pr create --fill`. ## Code - Maintain existing code structure and organisation and document public APIs. - Use Sorbet `sig` type signatures and `typed: strict` for new files. - Never
No other project uses it yet
mudler/LocalAI/AGENTS.md
/import-model` dropdown is server-driven from `GET /backends/known`) | | [.agents/coding-style.md](.agents/coding-style.md) | Code style, editorconfig, logging, documentation conventions | | [.agents/llama-cpp-backend.md](.agents/llama-cpp-backend.md) | Working on the llama.cpp backend — architecture, updating, tool call parsing | | [.agents/vllm-backend.md](.agents/vllm-backend.md
Steady10 mentions in 2 weeks
No other project uses it yet
metabase/metabase/AGENTS.md
owns `docs/` and updates it. Edit `docs/` only when the task is explicitly a documentation task. If your code change affects documented behavior, say so in your summary
calcom/cal.diy/AGENTS.md
thing well **Note**: These limits apply to code files only. Non-code files like documentation (README.md, CHANGELOG.md), lock files (yarn.lock, package-lock.json), and auto-generated files are excluded from the count
1 project uses a version of this
JuliaLang/julia/AGENTS.md
runtime and LLVM codegen - [`cli/`](cli/) - Command-line interface and loader - [`doc/`](doc/) - Documentation and User Manual ## Running Julia You should have a recent binary copy of julia in your
No other project uses it yet
Gathin23/cleanyourtv/AGENTS.md
permission. | | `themes/` | One folder per theme: `config.json`, a required `screenshot.jpg`, optional wallpapers. Keys are documented in `themes/README.md`. | | `addons/` | Optional module-card apps, each its own Gradle project, never built into
abhigyanpatwari/GitNexus/AGENTS.md
node` under `gitnexus/` and `gitnexus-web/`; `uv run` for Python under `eval/`; documented CI/dev workflows. | | **Off-limits** | Real `.env` / secrets, production credentials, unrelated repos, destructive git ops without confirmation. | ## Model
No other project uses it yet
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.