--- title: "Vercel (@vercel) skills · skilld" canonical_url: "https://skilld.dev/gh/vercel" meta: description: "43 agent skills published by Vercel on skilld. TypeScript, vercel-ai, ai-sdk." "og:description": "43 agent skills published by Vercel." "og:title": "Vercel on skilld" --- ` ![Avatar for Vercel](https://skilld.dev/_img/avatar?url=https%3A%2F%2Fgithub.com%2Fvercel.png) # **Vercel** [@vercel](https://github.com/vercel)org Agentic infrastructure for every app and agent. 43 skills5 repos 143k Mostly·TypeScript, vercel-ai, ai-sdk [GitHub](https://github.com/vercel) [Website](https://vercel.com) ## Skills ### [vercel/next.js](https://skilld.dev/gh/vercel/next.js) The React Framework 25 skills 143k `npx skilld add vercel/next.js` - [ **/authoring-skills**143k How to create and maintain agent skills in .agents/skills/. Use when creating a new SKILL.md, writing skill descriptions, choosing frontmatter fields, or deciding what content belongs in a skill vs AGENTS.md. Covers the supported spec fields, description writing, naming conventions, and the relationship between always-loaded AGENTS.md and on-demand skills. /authoring-skills by vercel](https://skilld.dev/gh/vercel/next.js/authoring-skills) - [ **/backport-pr**143k Backport a merged Next.js pull request from canary to a previous release branch such as next-16-2. Use when the user asks to backport, cherry-pick, or open a backport PR from a PR number to an older Next.js version. Covers finding the merged PR commit, creating a backport branch from the target release branch, cherry-picking from canary, validating, and opening the PR with the release branch as the base. /backport-pr by vercel](https://skilld.dev/gh/vercel/next.js/backport-pr) - [ **/create-pr**143k Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers .github/pull\_request\_template.md, --body formatting, codex/ branch names, and Codex app git directives. /create-pr by vercel](https://skilld.dev/gh/vercel/next.js/create-pr) - [ **/dce-edge**143k DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render / stream-utils for edge builds. Covers if/else branching for webpack DCE, TypeScript definite assignment, the NEXT\_RUNTIME vs real feature flag distinction, and forcing flags false for edge in define-env.ts. /dce-edge by vercel](https://skilld.dev/gh/vercel/next.js/dce-edge) - [ **/deploy-release-test**143k Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test\_e2e\_deploy\_release.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for focused deployment-test sanity checks; run the relevant tests locally with pnpm test-deploy instead. Covers resolving the latest branch SHA, waiting for vercel-packages, preserving default workflow inputs, dispatching the workflow, and verifying the run. /deploy-release-test by vercel](https://skilld.dev/gh/vercel/next.js/deploy-release-test) - [ **/flags**143k How to add or modify Next.js experimental feature flags end-to-end. Use when editing config-shared.ts, config-schema.ts, define-env-plugin.ts, next-server.ts, export/worker.ts, or module.compiled.js. Covers type declaration, zod schema, build-time injection, runtime env plumbing, and the decision between runtime env-var branching vs separate bundle variants. /flags by vercel](https://skilld.dev/gh/vercel/next.js/flags) - [ **/gate-tests**143k How to use the \`@gate\` / \`@force-gate\` test directives instead of \`it.skip\` or fake-green skip patterns. Use when a test is known-failing under some test-matrix dimension (dev mode, a bundler, an experimental flag like cacheComponents), when converting \`if (isNextDev) return\` guards or env-var \`describe.skip\` branches, when adding a condition to test/lib/gate/conditions.ts, or when keying a fixture's experimental flag on a \_\_NEXT\_TEST\_AXIS letter. Covers directive choice, condition tiers, the test-axis fixture pattern, pitfalls, and verification commands. /gate-tests by vercel](https://skilld.dev/gh/vercel/next.js/gate-tests) - [ **/gh-stack**143k Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out. /gh-stack by vercel](https://skilld.dev/gh/vercel/next.js/gh-stack) - [ **/insight-error-page**143k Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new \`errors/\.mdx\` page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification against canonical docs, and Vercel technical writing style. /insight-error-page by vercel](https://skilld.dev/gh/vercel/next.js/insight-error-page) - [ **/next-cache-components-adoption**143k Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the \`cacheComponents\` flag, work through a flood of blocking-prerender / instant validation errors, run the \`cache-components-instant-false\` codemod, or decide between opting routes out with \`export const instant = false\` and fixing them in place. /next-cache-components-adoption by vercel](https://skilld.dev/gh/vercel/next.js/next-cache-components-adoption) - [ **/next-cache-components-optimizer**143k Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then guards against regression. Use when asked to make a route's navigation instant (its static shell commits immediately), fix a route whose static shell isn't prerendered/served/prefetched, grow a route's static shell or fix its slow first paint, diagnose which Suspense boundary keeps a route out of its static shell, or write the instant() e2e guard for one. Requires Next.js 16.3+ with cacheComponents; directs an upgrade if older. /next-cache-components-optimizer by vercel](https://skilld.dev/gh/vercel/next.js/next-cache-components-optimizer) - [ **/next-dev-loop**143k Verify Next.js runtime behavior after editing app code. Use this skill to confirm a change actually works in a running app — not just that it compiles or type-checks. Combines /\_next/mcp (Next.js's view) with agent-browser (the browser's view). Requires a running \`next dev\`. /next-dev-loop by vercel](https://skilld.dev/gh/vercel/next.js/next-dev-loop) - [ **/next-partial-prefetching-adoption**143k Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the \`partialPrefetching\` flag, opt routes in with \`export const prefetch = 'partial'\`, audit \`Link prefetch={true}\` behavior, preserve existing prefetched UI with \`instant()\` tests, or resolve the instant-link-prefetch-partial and instant-shell-url-data insights. /next-partial-prefetching-adoption by vercel](https://skilld.dev/gh/vercel/next.js/next-partial-prefetching-adoption) - [ **/next-partial-prefetching-optimizer**143k Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport, and intent prefetching. Requires Next.js 16.3+. /next-partial-prefetching-optimizer by vercel](https://skilld.dev/gh/vercel/next.js/next-partial-prefetching-optimizer) - [ **/next-rspack**143k Maintain @next/rspack-core and @next/rspack-binding packages. Use when editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json. Covers upgrading @rspack/core npm version, rspack\_\* crate versions, Rust toolchain version, building and linking for local testing, and NEXT\_RSPACK environment variable usage. Does NOT apply to root rust-toolchain.toml (that's for Turbopack). /next-rspack by vercel](https://skilld.dev/gh/vercel/next.js/next-rspack) - [ **/pr-status-triage**143k Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction. /pr-status-triage by vercel](https://skilld.dev/gh/vercel/next.js/pr-status-triage) - [ **/react-sync**143k Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration. Use when working on React changes that need validation in Next.js, or when asked to run buildForNext, pnpm sync-react, or synchronize a React checkout with Next.js. /react-sync by vercel](https://skilld.dev/gh/vercel/next.js/react-sync) - [ **/react-vendoring**143k React vendoring and react-server layer boundaries. Use when editing entry-base.ts, $$compiled.internal.d.ts, compiled/react\* packages, or taskfile.js copy\_vendor\_react. Covers the entry-base.ts boundary (all react-server-dom-webpack/\* imports must go through it), vendored React channels, type declarations, Turbopack remap to react-server-dom-turbopack, ComponentMod access patterns, and ESLint suppression for guarded requires. /react-vendoring by vercel](https://skilld.dev/gh/vercel/next.js/react-vendoring) - [ **/router-act**143k How to write end-to-end tests using createRouterAct and LinkAccordion. Use when writing or modifying tests that need to control the timing of internal Next.js requests (like prefetches) or assert on their responses. Covers the act API, fixture patterns, prefetch control via LinkAccordion, fake clocks, and avoiding flaky testing patterns. /router-act by vercel](https://skilld.dev/gh/vercel/next.js/router-act) - [ **/runtime-debug**143k Debug and verification workflow for runtime-bundle and module-resolution regressions. Use when diagnosing unexpected module inclusions, bundle size regressions, or CI failures related to NEXT\_SKIP\_ISOLATE, nft.json traces, or runtime bundle selection (module.compiled.js). Covers CI env mirroring, full stack traces via \_\_NEXT\_SHOW\_IGNORE\_LISTED, route trace inspection, and webpack stats diffing. /runtime-debug by vercel](https://skilld.dev/gh/vercel/next.js/runtime-debug) - [ **/sandbox-bench**143k Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app (rps, latency, p95; TTFB, RSS and document/Flight bytes when the Next side captures them) and, for React changes, through the react repo's flight-ssr-bench fixture (Node AND Edge web-streams paths, Fizz and Flight+Fizz). Use whenever the user asks to bench, perf test, or A/B a React PR, a react-server-dom / Flight / vendored React change, or a Next.js PR ("is this PR faster", "does this regress RSC?", "measure the perf impact of \"), even if they don't say "benchmark" — any request to quantify a server-side performance difference between two revisions belongs here. Runs remotely (laptop-free), applies correctness gates before measuring, and reports boot-level confidence intervals. /sandbox-bench by vercel](https://skilld.dev/gh/vercel/next.js/sandbox-bench) - [ **/update-docs**143k This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes. /update-docs by vercel](https://skilld.dev/gh/vercel/next.js/update-docs) - [ **/v8-jit**143k V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure allocation, array packing, and profiling with --trace-opt / --trace-deopt. /v8-jit by vercel](https://skilld.dev/gh/vercel/next.js/v8-jit) - [ **/write-api-reference**143k Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options. \*\*Auto-activation:\*\* User asks to write, create, or draft an API reference page. Also triggers on paths like \`docs/01-app/03-api-reference/\`, or keywords like "API reference", "props", "parameters", "returns", "signature". \*\*Input sources:\*\* Next.js source code, existing API reference pages, or user-provided specifications. \*\*Output type:\*\* A markdown (.mdx) API reference page with YAML frontmatter, usage example, reference section, behavior notes, and examples. /write-api-reference by vercel](https://skilld.dev/gh/vercel/next.js/write-api-reference) - [ **/write-guide**143k Generates technical guides that teach real-world use cases through progressive examples. \*\*Auto-activation:\*\* User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. \*\*Input sources:\*\* Feature skills, API documentation, existing code examples, or user-provided specifications. \*\*Output type:\*\* A markdown guide with YAML frontmatter, introduction, 2-4 progressive steps, and next steps section. /write-guide by vercel](https://skilld.dev/gh/vercel/next.js/write-guide) ### [vercel/ai](https://skilld.dev/gh/vercel/ai) The AI Toolkit for TypeScript. From the creators of Next.js, the AI SDK is a free open-source library for building AI-powered applications and agents 13 skills 27k `npx skilld add vercel/ai` - [ **/add-function-examples**27k Guide for adding new AI function examples, for testing specific features against the actual provider APIs. /add-function-examples by vercel](https://skilld.dev/gh/vercel/ai/add-function-examples) - [ **/add-harness-package**27k Guide for adding new AI SDK harness packages. Use when creating a new @ai-sdk/harness-\ package that adapts a coding-agent runtime to HarnessV1. /add-harness-package by vercel](https://skilld.dev/gh/vercel/ai/add-harness-package) - [ **/add-provider-package**27k Guide for adding first-party AI provider packages to the AI SDK. Use when creating a provider package under packages/ to integrate an external AI service. /add-provider-package by vercel](https://skilld.dev/gh/vercel/ai/add-provider-package) - [ **/adr-skill**27k Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting, and validates output against an agent-readiness checklist. /adr-skill by vercel](https://skilld.dev/gh/vercel/ai/adr-skill) - [ **/capture-api-response-test-fixture**27k Capture API response test fixture. /capture-api-response-test-fixture by vercel](https://skilld.dev/gh/vercel/ai/capture-api-response-test-fixture) - [ **/develop-ai-functions-example**27k Develop examples for AI SDK functions. Use when creating, running, or modifying examples under examples/ai-functions/src to validate provider support, demonstrate features, or create test fixtures. /develop-ai-functions-example by vercel](https://skilld.dev/gh/vercel/ai/develop-ai-functions-example) - [ **/island-rescue**27k How to be rescued from a lonely island /island-rescue by vercel](https://skilld.dev/gh/vercel/ai/island-rescue) - [ **/list-npm-package-content**27k List the contents of an npm package tarball before publishing. Use when the user wants to see what files are included in an npm bundle, verify package contents, or debug npm publish issues. /list-npm-package-content by vercel](https://skilld.dev/gh/vercel/ai/list-npm-package-content) - [ **/major-version-mode**27k Context for working on the next AI SDK major release. Only use when explicitly invoked by the user (e.g. via '/major-version-mode'). Do NOT trigger autonomously based on task content. /major-version-mode by vercel](https://skilld.dev/gh/vercel/ai/major-version-mode) - [ **/migrate-ai-sdk-v6-to-v7**27k Migrate applications from AI SDK 6.x to AI SDK 7.0. Use when upgrading Vercel AI SDK packages, fixing v7 migration errors, or when the user mentions AI SDK v6, v7, upgrade, migration, breaking changes, system to instructions, fullStream, telemetry, tool context, or finalStep. /migrate-ai-sdk-v6-to-v7 by vercel](https://skilld.dev/gh/vercel/ai/migrate-ai-sdk-v6-to-v7) - [ **/update-harness-dependencies**27k Update the primary SDK dependencies of harness packages. Use when asked to update the harness SDKs or harness adapter dependencies. /update-harness-dependencies by vercel](https://skilld.dev/gh/vercel/ai/update-harness-dependencies) - [ **/update-provider-models**27k Add new or remove obsolete model IDs for existing AI SDK providers. Use when adding a model to a provider, removing an obsolete model, or processing a list of model changes from an issue. Triggers on "add model", "remove model", "new model ID", "obsolete model", "update model IDs". /update-provider-models by vercel](https://skilld.dev/gh/vercel/ai/update-provider-models) - [ **/use-ai-sdk**27k Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat". /use-ai-sdk by vercel](https://skilld.dev/gh/vercel/ai/use-ai-sdk) ### [vercel/eve](https://skilld.dev/gh/vercel/eve) The Open Framework for Building Agents 3 skills 5.4k `npx skilld add vercel/eve` - [ **/eve**5.4k Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals. /eve by vercel](https://skilld.dev/gh/vercel/eve/eve) - [ **/gh-pr-description**5.4k Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers. /gh-pr-description by vercel](https://skilld.dev/gh/vercel/eve/gh-pr-description) - [ **/technical-writing**5.4k Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions. /technical-writing by vercel](https://skilld.dev/gh/vercel/eve/technical-writing) ### [vercel/ai-elements](https://skilld.dev/gh/vercel/ai-elements) 1 skill 2.5k `npx skilld add vercel/ai-elements` - [ **/ai-elements**2.5k Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface. /ai-elements by vercel](https://skilld.dev/gh/vercel/ai-elements) ### [vercel/components.build](https://skilld.dev/gh/vercel/components.build) An open-source standard for building modern, composable and accessible UI components. 1 skill 797 `npx skilld add vercel/components.build` - [ **/building-components**797 Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation. /building-components by vercel](https://skilld.dev/gh/vercel/components.build) Skills published by Vercel. Checked GitHub just now