vercel/next.js▌

Use this skill when creating or modifying agent skills in .agents/skills/.

Use this skill when the user asks about PR status, CI failures, or review comments in the Next.js monorepo.

Use this skill when adding or changing framework feature flags in Next.js internals.

Produce an API reference page that documents a single API surface (function, component, file convention, directive, or config option). The page should be concise, scannable, and example-driven.

Produce a technical guide that teaches a real-world use case through progressive examples. Concepts are introduced only when the reader needs them.

Use this skill when changing conditional require() paths, Node-only imports, or edge/runtime branching.

Use this skill for changes touching vendored React, react-server-dom-webpack/*, or react-server layer boundaries.

Guided workflow for updating Next.js documentation based on code changes and PR reviews. \n \n Analyzes git diffs to identify affected documentation files using a code-to-docs mapping reference \n Provides templates and conventions for scaffolding new feature docs (components, functions, config, guides, file conventions) \n Walks through step-by-step updates to existing documentation with user confirmation before each change \n Includes validation checklist and linting commands to ensure formatt

Use this skill when reproducing runtime-bundle, module-resolution, or user-bundle inclusion regressions.