VercelAGENTS.mdnext.js / evals
vercel/next.js/evals/AGENTS.md
Do not export evals with "publish": false to next-evals-oss or publish their results on nextjs.org/evals.
AGENTS.md examples from real projects
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Most stars firstWorked for most · soon
VercelAGENTS.mdVercelAGENTS.mdnext.js / future-cache-components
vercel/next.js/evals/next-upgrade/evals/future-cache-components/AGENTS.md
You may edit this application and create local commits. Do not push or create pull requests. Use npm. Preserve the behavior described in README.md.
VercelAGENTS.mdnext.js / future-cache-components-nudge
vercel/next.js/evals/next-upgrade/evals/future-cache-components-nudge/AGENTS.md
Do not push or create pull requests. Use npm.
VercelAGENTS.mdnext.js / latest-nudge
vercel/next.js/evals/next-upgrade/evals/latest-nudge/AGENTS.md
You may edit this application. Do not push or create pull requests. Use npm. Preserve the behavior described in the user prompt.
VercelAGENTS.mdnext.js
vercel/next.js/.github/AGENTS.md
Set permissions: {} at the workflow level and grant the minimum needed per-job. Prefer GitHub-provided (actions/*) and Vercel-owned actions. For third-party actions: ${{ ... }} is interpolated into the script before bash runs, so untrusted values (PR title, branch name, issue body) can break out and execute. Route them through an env var and quote on use:
VercelAGENTS.mdnext.js / next
vercel/next.js/packages/next/AGENTS.md
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in dist/docs/ before writing any code. Heed deprecation notices.
VercelAGENTS.mdnext.js / test
vercel/next.js/test/AGENTS.md
No summary in the file. Open it to read it.
VercelAGENTS.mdnext.js / turbopack
vercel/next.js/turbopack/AGENTS.md
Turbopack is a general-purpose bundler that is built and designed for Next.js, but is not necessarily Next.js-specific. Keep Next.js concepts out of it.
VercelAGENTS.mdturborepo
vercel/turborepo/AGENTS.md
PR titles must follow Conventional Commits. See .github/workflows/lint-pr-title.yml for the enforced constraints. Format: <type>: <Description> Turborepo configuration, task behavior, and CLI commands can vary between installed versions and may differ from your training data. Resolve the turbo package from this file's directory or relevant workspace; in monorepos, it may not be visible from the repository root. For example, run node -p "require.resolve('turbo/package.json')" from a workspace that depends on turbo. Read docs/README.md inside that installed package first, then read the relevant…
VercelAGENTS.mdturborepo / apps
vercel/turborepo/apps/docs/AGENTS.md
The root AGENTS.md also applies to this app. Geistdocs owns shared runtime behavior, while this app owns Turborepo content, routes, metadata, assets, and adapters. This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in monorepos the next package may not be visible from the repo root) before writing any code. Heed deprecation notices. This block is written and re-added by…
VercelAGENTS.mdturborepo / factory
vercel/turborepo/apps/factory/AGENTS.md
This project uses the eve framework. Before writing code, always read the relevant guide in node_modules/eve/docs/.
VercelAGENTS.mdturborepo / basic
vercel/turborepo/examples/basic/AGENTS.md
Turborepo configuration, task behavior, and CLI commands can vary between installed versions and may differ from your training data. Resolve the turbo package from this file's directory or relevant workspace; in monorepos, it may not be visible from the repository root. For example, run node -p "require.resolve('turbo/package.json')" from a workspace that depends on turbo. Read docs/README.md inside that installed package first, then read the relevant pages from its docs/ directory before changing Turborepo configuration or commands. Heed deprecation notices. These…
VercelAGENTS.mdturborepo / web
vercel/turborepo/examples/with-nextjs-elysia/apps/web/AGENTS.md
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules -->
VercelAGENTS.mdai
vercel/ai/AGENTS.md
This file provides context for AI coding assistants (Cursor, GitHub Copilot, Claude Code, etc.) working with the Vercel AI SDK repository. The AI SDK by Vercel is a TypeScript/JavaScript SDK…
VercelAGENTS.mdai / apps
vercel/ai/apps/docs/AGENTS.md
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ (resolved from this file's directory; in…
VercelAGENTS.mdai / ai
vercel/ai/packages/ai/AGENTS.md
No summary in the file. Open it to read it.
VercelAGENTS.mdvercel
vercel/vercel/AGENTS.md
Guidelines for AI agents working on the Vercel monorepo. This is a pnpm monorepo containing 44+ packages for the Vercel CLI and runtimes: Run tests for a specific package: Always create a changeset for all PRs. A changeset is a markdown file in .changeset/ with YAML frontmatter listing affected packages and their bump type (patch/minor/major). Example changeset for a package change: Example changeset for non-package changes: Run before committing: When adding tests: Each package follows this structure: Workspace dependencies use…
VercelAGENTS.mdvercel / cli
vercel/vercel/packages/cli/AGENTS.md
Always-loaded guidance for work inside packages/cli. Keep this file small. The CLI UX design system lives in packages/cli/.agents/skills/cli-ux/ and should be loaded only when the task or code review touches user-facing CLI behavior. Common shared areas:
VercelAGENTS.mdvercel / python
vercel/vercel/python/AGENTS.md
- Dependencies: PEP 440 compatible release clauses (rich ~= 14.0), avoid pinning patch releases (rich ~= 14.0.0). - Only add code that is actually used. No speculative APIs or exports. - _internal/ is private — no backwards compatibility needed when refactoring. - uv: uv sync, uv run <cmd>, uv add <pkg> - ruff: uv run ruff check . (lint), uv run ruff format . (format) - pytest: uv run pytest, uv run pytest tests/testfoo.py, uv run pytest -k testname. Tests…
VercelAGENTS.mdeve
vercel/eve/AGENTS.md
Guidance for coding agents (and humans) working in this repository. For setup, PR workflow, and release process, see CONTRIBUTING.md. eve is a filesystem-first framework for durable backend AI agents. You author an agent as a directory on disk — instructions, skills, tools, connections, channels, subagents, and schedules are all files — and eve compiles and runs it. See the README for the full overview and docs/ for user-facing documentation. Always style the framework name as eve, lowercase, in user-facing copy,…
About AGENTS.md
What is AGENTS.md?
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
Where does it go?
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
What should it contain?
Setup and test commands, code style, and the rules a new contributor would need to know.
Does Claude Code read it?
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.