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
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.
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
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
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.
Steady2 mentions in 2 weeks
No other project uses it yet
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.
Steady2 mentions in 2 weeks
No other project uses it yet
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.
Steady2 mentions in 2 weeks
No other project uses it yet
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
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
vercel/next.js/test/AGENTS.md
Tests for behavior that affects deployed applications must live in test/e2e/ and exercise the real deployment path. This applies to new features and regressions. Reserve test/production/ for behavior inherently specific to self-hosted servers or the local CLI. Simulating minimal mode is an exception. Use private switches such as NEXT_PRIVATE_MINIMAL_MODE and NEXT_PRIVATE_TEST_HEADERS only when a real deployment cannot exercise the protocol invariant under test. Explain that constraint in the test. A simulation must not replace real deployment coverage of behavior that…
Steady2 mentions in 2 weeks
No other project uses it yet
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:
Steady2 mentions in 2 weeks
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.