What problem does it solve? Dynamic responses on Netlify are not cached by default, and misconfigured cache headers silently fragment the CDN cache or get wiped on every deploy. This Skill provides the exact header patterns, purge APIs, and debugging steps needed to control Netlify's CDN caching correctly. ## Core Features & Use Cases - Cache Header Patterns: Ready-to-use Netlify-CDN-Cache-Control, Cache-Control, and durable cache configurations for functions and static assets, including stale-while-revalidate. - On-Demand Purge: Tag responses with Netlify-Cache-Tag and invalidate them via purgeCache(), including how to pass a personal access token when running outside the Netlify Functions runtime. - Cache Key Control: Use Netlify-Vary to key cache entries on specific query params, cookies, headers, country, or language, and prevent tracking parameters from fragmenting the cache. - Use Case: A product listing API served by a Netlify Function is slow under load. Add Netlify-CDN-Cache-Control: public, s-maxage=86400 with a Netlify-Cache-Tag: product header, then purge by tag whenever inventory changes. ## Quick Start Ask the assistant to add CDN caching with a purge tag to a Netlify Function response using the netlify-caching guidance.
