What problem does it solve? Teams often enable a CDN in front of an origin and see no benefit because the origin sends no-store or missing cache headers, the cache key is polluted by tracking parameters, or deploys depend on slow purges. This Skill provides the patterns and checklists needed to make edge caching actually work. ## Core Features & Use Cases - Cache-Control Design: Set max-age, s-maxage, immutable, and stale-while-revalidate correctly per content type so browsers and shared caches behave as intended. - Cache Key and Vary Hygiene: Strip non-significant query parameters and avoid Vary: Cookie or Vary: User-Agent so hit rates do not collapse. - Fingerprinting and Invalidation Strategy: Use content-hashed asset filenames to eliminate routine purges, reserving purge for emergencies only. - Origin Protection and Edge Compute Guidance: Apply origin shielding against thundering herds and scope edge functions to routing, auth, and header shaping. - Use Case: Before launching a site behind CloudFront or Cloudflare, run the delivery checklist to verify every content type has an intentional Cache-Control policy and measure the edge hit rate. ## Quick Start Review my origin's cache headers and CDN configuration and tell me what to change to improve edge cache hit rate.
