What problem does it solve? Choosing the wrong caching strategy per resource type causes stale pages after deploys, missing offline support, or unbounded cache growth. This Skill provides the canonical strategy-per-route-class table, cache versioning rules, and update activation patterns so a PWA's service worker behaves correctly. ## Core Features & Use Cases - Strategy selection per route class: Maps HTML pages, hashed JS/CSS bundles, fonts, images, and API responses to NetworkFirst, CacheFirst, StaleWhileRevalidate, or NetworkOnly with concrete options like networkTimeoutSeconds and maxEntries. - Cache versioning and cleanup: Shows how to embed a build hash in every cacheName and delete orphaned caches on activation to prevent quota exhaustion and broken pages after deploys. - Update activation UX: Covers silent activation, reload-to-update prompts via workbox-window, and aggressive skipWaiting/clientsClaim, with guidance on which fits checkout-sensitive flows. - Use Case: When adding a service worker to a Next.js 16 app with Serwist, use this Skill to scaffold the runtimeCaching config, version the caches, and pick an update prompt pattern. ## Quick Start Ask the agent to configure a service worker for your PWA with the correct caching strategy per route class and versioned cache names.
