next-cache-components-optimizer

Run the page-render loop: capture the shell-only render with the instant cookie set, rank Suspense fallback areas by visible pixel size, then push I/O down into Suspense-wrapped children or add 'use cache' with a cacheLife profile. Verify with before and after screenshots that visibly differ.

Use the navigation loop: pushstate to the target route with the instant cookie set, capture suspended boundaries, and filter out client-hook blockers like usePathname that only affect SSR. Fix real blockers with push-down or 'use cache: private' plus prefetch = 'allow-runtime'.

No. The Skill refuses to run unless cacheComponents: true is set in next.config.ts, since its levers like 'use cache', cacheLife profiles, and runtime prefetch all depend on that mode. It also requires the next-dev-loop session for browser and log access.

These errors mean the route has no static shell because dynamic I/O runs without a Suspense boundary. The Skill treats this as a no-shell bailout: you must wrap the offending dynamic access in <Suspense> before any shell-growing or caching optimization can apply.

Use 'use cache: private' when the I/O reads request APIs like cookies(), headers(), or searchParams, since shared caching bails to dynamic for those reads. Pair it with prefetch = 'allow-runtime' on the owning segment so navigation can resolve session-specific data at link-visibility time.