What problem does it solve? It guides developers through adopting Next.js 16 Cache Components, replacing legacy caching APIs like unstable_cache and experimental.ppr with the new use cache directive, cache profiles, and tag-based invalidation while respecting tenant isolation rules. ## Core Features & Use Cases - Partial Prerendering Setup: Enable cacheComponents and mix static, cached, and dynamic content in a single route using Suspense boundaries. - Cache Configuration: Apply built-in cacheLife 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 unstable_cache, force-dynamic, and route segment revalidate configs to the use cache model, including handling runtime APIs like cookies() via arguments or use cache: private. - Use Case: When upgrading an EVA dashboard page to Next.js 16, wrap slow aggregate queries in use cache with hourly revalidation, tag them per tenant, and stream user-specific notifications through Suspense. ## Quick Start Apply the next-cache-components skill to convert this Next.js page to use Cache Components with appropriate cacheLife and cacheTag settings.