AGENTS.md examples from real projects

VercelReads credentialsAGENTS.md

next.js

vercel/next.js/AGENTS.md

This is a pnpm monorepo containing the Next.js framework and related packages. The main Next.js framework lives in packages/next/. This is what gets published as the next npm package. Source code is in packages/next/src/. Key entry points: Compiled output goes to packages/next/dist/ (mirrors src/ structure). Before editing or creating files in any subdirectory (e.g., packages/*, crates/*), read all README.md files in the directory path from the repo root up to and including the target file's directory. This helps identify any…

No other project uses it yet

VercelAGENTS.md

next.js / bundle-analyzer

vercel/next.js/apps/bundle-analyzer/AGENTS.md

This app enables the Rust React Compiler (reactCompiler and turbopackRustReactCompiler in next.config.mjs). When adding or reviewing UI code:

No other project uses it yet

VercelAGENTS.md

next.js / crates

vercel/next.js/crates/AGENTS.md

Read and follow the shared turbo_tasks caching and invalidation guidance. Those turbo_tasks rules also apply throughout crates/ and all its subdirectories when developing with turbo_tasks.

No other project uses it yet

VercelAGENTS.md

next.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.

No other project uses it yet

VercelAGENTS.md

next.js / agent-062-pokedex-dev-loop

vercel/next.js/evals/evals/agent-062-pokedex-dev-loop/AGENTS.md

Before any Next.js work, find and read the relevant doc in app/node_modules/next/dist/docs/. Your training data is outdated — the docs are the source of truth.

No other project uses it yet

VercelAGENTS.md

next.js / next-13

vercel/next.js/evals/next-upgrade/apps/member-dashboard/next-13/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.

No other project uses it yet

VercelAGENTS.md

next.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:

No other project uses it yet

VercelAGENTS.md

next.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.

No other project uses it yet

VercelAGENTS.md

next.js / test

vercel/next.js/test/AGENTS.md

All newly created e2e tests must work with Cache Components both enabled and disabled. The test infrastructure runs both variants. In the enabled variant, __NEXT_CACHE_COMPONENTS=true enables Cache Components even when the fixture's next.config does not declare cacheComponents. - Write fixtures that conform to Cache Components rules by default: put uncached or request-time work behind appropriate <Suspense> boundaries, and use "use cache" for work that should be cached. Preserve what the test is intended to cover when adapting the fixture. -…

No other project uses it yet

VercelAGENTS.md

next.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. These rules apply throughout this directory tree when developing with turbo_tasks:

No other project uses it yet

VercelAGENTS.md

turborepo

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.md

turborepo / 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.md

turborepo / 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.md

turborepo / 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.md

turborepo / 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.md

ai

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…

No other project uses it yet

VercelAGENTS.md

ai / 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…

No other project uses it yet

VercelAGENTS.md

ai / ai

vercel/ai/packages/ai/AGENTS.md

No summary in the file. Open it to read it.

No other project uses it yet

VercelAGENTS.md

vercel

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 an internal package (the public packages that bundle it are added at version time): Example changeset…

VercelAGENTS.md

vercel / 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: