Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/next-partial-prefetching-optimizer
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+.
Passed 18 of 19 test cases with the skill, and 7 of 19 without it.
and 12 more in the full report
11 fixed7 passed either way1 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are preparing our Next.js production build configuration so our automated Playwright end-to-end navigation tests can execute `instant()` locks. Which experimental Next.js configuration flag must be enabled for testing?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies experimental.exposeTestingApiInProductionBuild in the Next.js configuration | Missed | Passed |
The instructions your model reads when the skill loads.
Optimize each requested source link and destination as its own contract. Turn
the requested prefetched UI, navigation-only UI, and trigger into a production
instant()
test. Record the current behavior, make the smallest optimization, verify the
differential, and keep the passing test as regression coverage.
Before making framework changes, read the bundled Optimizing prefetching guide
at
node_modules/next/dist/docs/01-app/02-guides/optimizing-prefetching.md. If the
bundled guide is unavailable, use the online
guide. It is the
source of truth for prefetch stages, prefetch={true}, session-specific UI,
and cost trade-offs.
When the work changes what belongs in the App Shell, follow the Instant navigation and Caching docs for cache placement, Suspense boundaries, loading UI, and authorization.
The guides own framework behavior and implementation patterns. This skill owns the navigation contract, production rig, trustworthy RED-to-GREEN loop, parity check, differential, and report.
This is not an adoption skill. If Cache Components or Partial Prefetching are
not adopted, use their adoption skills and return to this workflow. If the App
Shell itself cannot commit under instant(), use
next-cache-components-optimizer first, then resume the selected navigation.
Run the workflow unattended. Resolve the contract from the request and the existing application. Stop for user input only when a product decision is genuinely blocked and cannot be inferred safely without changing cost, freshness, authorization, or user-visible behavior.
This loop runs unattended, so do not stop between implementation steps. Finish the navigations the user named, then check in. The rig, lock, RED/GREEN loop, and stage names are internal scaffolding; report the product behavior instead.
test cases passed, vs 7 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.