edge-cache-architecture-architect

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 failures. 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 to choose between static, ISR, PPR, and fully dynamic surfaces. - 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 and middleware avoid Node-only APIs and that personalization never leaks into shared caches. - Use Case: When building a Next.js e-commerce page, use this Skill to split the globally cacheable product shell from user-specific cart fragments, define revalidation triggers for inventory changes, and confirm middleware stays within edge runtime constraints. ## Quick Start Ask the AI to design a caching and rendering strategy for your Next.js product page that mixes static content with personalized user data.