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.
Steady2 mentions in 2 weeks
1 project uses a version of this
143k6mo agoReviewMountCreate a free account to mount
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 <commit>"), 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.
Steady2 mentions in 2 weeks
No other project uses it yet
143k6mo agoReviewMountCreate a free account to mount
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.
Steady2 mentions in 2 weeks
87 projects use a version of this
143k6mo agoReviewMountCreate a free account to mount
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.
Steady2 mentions in 2 weeks
No other project uses it yet
143k6mo agoReviewMountCreate a free account to mount
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
143k6mo agoReviewMountCreate a free account to mount
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
143k6mo agoReviewMountCreate a free account to mount
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
143k6mo agoReviewMountCreate a free account to mount
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
143k6mo agoReviewMountCreate a free account to mount
Audit and reduce Next.js browser initial-load work. Use for slow route startup, oversized client bundles, duplicate browser dependencies, or features that can wait for interaction.
Surging2 mentions in 2 weeks
3 projects use a version of this
143k6mo agoReviewMountCreate a free account to mount
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.
Rising2 mentions in 2 weeks
13 projects use a version of this
143k6mo agoReviewMountCreate a free account to mount
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`.
Cooling2 mentions in 2 weeks
18 projects use a version of this
143k6mo agoReviewMountCreate a free account to mount
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.
Steady2 mentions in 2 weeks
10 projects use a version of this
143k6mo agoReviewMountCreate a free account to mount
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+.
Surging2 mentions in 2 weeks
3 projects use a version of this
143k6mo agoReviewMountCreate a free account to mount
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. -…
Steady2 mentions in 2 weeks
No other project uses it yet
143k6mo agoReviewMountCreate a free account to mount
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
VercelSkill