next-cache-components

Enable Partial Prerendering (PPR) in Next.js by setting `cacheComponents: true` in your `next.config.ts` file. This allows the Skill to blend static, cached, and dynamic content seamlessly within a single route.

Cache invalidation in Next.js uses `updateTag()` for immediate invalidation and `revalidateTag()` for background invalidation. The Skill manages both mechanisms to ensure cached content refreshes appropriately when underlying data changes.

Yes, you can stream user-specific dynamic content while caching static layouts in a Next.js application. Partial Prerendering allows you to prerender static headers, cache frequently accessed data, and dynamically stream user-specific content within the same page.

Yes, this Skill specifically enables and configures Next.js 16+ Cache Components. It handles runtime data constraints and cache key generation specifically for the Next.js 16+ environment.

Limitations of using cache directives for Partial Prerendering include specific handling required for runtime data constraints and cache key generation. Cache invalidation must be explicitly managed using `updateTag` or `revalidateTag` to prevent stale content.