vercel / next.js

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

1 file — installable on its own

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

1 file — installable on its own

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

1 file — installable on its own

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

3 files — installable on its own

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

1 file — installable on its own

Use this skill when writing or modifying tests that involve prefetch requests, client router navigations, or the segment cache. The createRouterAct utility from test/lib/router-act.ts lets you assert on prefetch and navigation responses in an end-to-end way without coupling to the exact number of requests or the protocol details. This is why most client router-related tests use this pattern.

1 file — installable on its own

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

1 file — installable on its own

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

4 files — installable on its own

Use this skill when writing or optimizing performance-critical code paths in Next.js server internals — especially per-request hot paths like rendering, streaming, routing, and caching.

1 file — installable on its own

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.

1 file — installable on its own

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

1 file — installable on its own