pwa

You can make a web app reliably offline-capable by registering a service worker with caching strategies. This Skill provides a framework-agnostic pattern for manual service worker creation, navigate fallback, and versioned caches.

The best way to handle cache-first vs network-first rules is applying a framework-agnostic PWA pattern. This Skill implements specific caching strategies for offline reliability, determining when to serve cached assets versus fetching fresh network updates.

To set up a manifest for installability and update prompts, you configure the web app manifest and implement a smooth update flow. This Skill provides the setup needed for cross-device installable experiences and versioned cache management.

Yes, this PWA service worker pattern works without a specific web framework. It provides a complete framework-agnostic implementation, applying manual service worker creation and inline registration guidance to any web app seeking offline reliability.

Your service worker update flow serves stale content due to improper versioned cache management. This Skill implements versioned caches and a smooth update flow, ensuring users receive fresh updates through proper cache-first vs network-first rules.

You need a navigate fallback in your service worker caching strategies when providing offline reliability for web app navigations. This Skill covers navigate fallback implementation to ensure users experience smooth page loads during network failures.