{"id":77640,"plugin_id":"plugins_6ae8cc5ee77c81918ab31ed7701a28de","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:26.961Z","digest":"a4a986269f99d4ce7457a735e82db48eb443d09f79f4ae73397b5c09b83908ec","against":null,"payload":{"description":"Turn an existing web app into a genuine PWA or build a new installable PWA with manifest, service worker strategy, offline behavior and installation testing.","included_files":[],"name":"build-pwa","skill_md_contents":"---\nname: build-pwa\ndescription: Turn an existing web app into a genuine PWA or build a new installable PWA with manifest, service worker strategy, offline behavior and installation testing.\n---\n\n# Build Pwa\n\n1. Read `../../references/web-and-pwa.md`; start with the user's web framework and existing content. Explain that PWA installation and capability vary by browser and OS, especially iOS.\n2. Implement a valid manifest (name, icons, start URL, display modes), HTTPS deployment expectations and a versioned service worker when needed. Pick a cache strategy per resource class; avoid caching sensitive authenticated data by default.\n3. Define offline UX: shell, data that may be cached, unavailable actions, queued writes only when consistency/replay is safe, conflict behavior and user-facing sync status.\n4. Test installability with compatible tools/browsers, simulate offline and cache refresh, update flows and version migration. Validate mobile layouts and app icon sizes when assets are available.\n5. Do not claim background sync, push, arbitrary file access or install prompt is universally supported. Record platform/browser constraints and actual tests.\n6. Return manifest/service worker source, commands, test log and limitations.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}