What problem does it solve? Vague "make it faster" requests often lead to accidental dynamic rendering, leaked personal data in shared caches, and edge runtime crashes from Node-only imports. This Skill turns those requests into deliberate, production-safe caching and rendering decisions. ## Core Features & Use Cases - Rendering Strategy Selection: Classify data by volatility, sensitivity, and audience specificity, then choose between static, ISR, PPR, dynamic, route handlers, and middleware. - Cache Layer Assignment: Assign the right cache layer (data cache, route cache, router cache, or CDN) with explicit invalidation events and cache tags. - Edge Compatibility Review: Verify that edge routes avoid Node-only APIs and that personalization stays separated from shared cacheable content. - Use Case: When building a Next.js storefront with personalized recommendations, use this Skill to design a static shell with dynamic islands, define cache tags for inventory updates, and keep user data out of the shared CDN cache. ## Quick Start Ask the AI to design a caching and rendering strategy for your Next.js page, describing your data sources, personalization needs, and latency budget.