What problem does it solve? Next.js 16 replaces legacy caching APIs like unstable_cache and route segment config with Cache Components, and developers need clear guidance on enabling Partial Prerendering, applying the use cache directive, and handling cache invalidation correctly. ## Core Features & Use Cases - Partial Prerendering Setup: Enable cacheComponents in next.config.ts and mix static, cached, and dynamic content in a single route using Suspense boundaries. - Cache Lifetime Control: Configure cacheLife with built-in profiles (minutes, hours, days) or inline stale/revalidate/expire values, and tag entries with cacheTag for targeted invalidation via updateTag or revalidateTag. - Migration Guidance: Convert legacy patterns like experimental.ppr, force-static, revalidate exports, and unstable_cache calls into the use cache directive model. - Use Case: When building a dashboard that mixes a static shell, hourly-refreshed stats, and per-user notifications, apply use cache with cacheLife('hours') to the stats component and wrap the dynamic notifications in Suspense. ## Quick Start Ask the AI to refactor a Next.js page to use Cache Components with the use cache directive, cacheLife, and cacheTag for cached data and Suspense for dynamic content.