Making v0 navigations instant with Next.js 16.3 and an agent loop

On August 6, 2026, the Next.js blog described Instant Navigations in 16.3. They help dynamic App Router apps feel snappy without moving data-fetching to the client: Suspense loading states or 'use cache' let Next extract a shell and load it into the browser before navigation, a Partial Prerendering-style approach for personalized apps.

The Next.js team adopted this in v0, Vercel's full-stack coding platform, using a coding agent and the next-cache-components-optimizer Skill. For each slow journey the agent wrote a failing Playwright test with the instant() helper from @next/playwright, applied Skill patterns, re-ran until green, and kept the tests in CI. One refactor moves session and team fetches under Suspense so the settings shell stays instant. Install the Skill with npx skills add vercel/next.js --skill next-cache-components-optimizer, then prompt agents to make a named navigation instant.

The post closes on a simple point: frameworks still matter in the agent era because helpers like instant() turn fuzzy UX into deterministic tests. That App Router work sits on the same Vercel deploy path as Chapter 1.

Read original: Making Navigations Instant in v0 — Next.js

Related in the book: Chapter 1