progressive-web-app

Featured

Build Progressive Web Apps (PWAs) with offline support, installability, and caching strategies. Trigger whenever the user mentions PWA, service workers, web app manifests, Workbox, 'add to home screen', or wants their web app to work offline, feel native, or be installable.

Web & Frontend 27,705 stars 2858 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Progressive Web Apps (PWAs) ## Overview A Progressive Web App is a web application that uses modern browser capabilities to deliver a fast, reliable, and installable experience — even on unreliable networks. The three required pillars are: 1. **HTTPS** — Required in production for service workers to register (localhost is exempt for development). 2. **Web App Manifest** (`manifest.json`) — Makes the app installable and defines its appearance on device home screens. 3. **Service Worker** (`sw.js`) — A background script that intercepts network requests, manages caches, and enables offline functionality. ## When to Use This Skill - Use when the user wants their web app to work offline or on unreliable networks. - Use when building a mobile-first web project where users should be able to install the app to their home screen. - Use when the user asks about caching strategies, service workers, or improving web app performance and resilience. - Use when the user mentions Workbox, web app manifests, background sync, or push notifications for the web. - Use when the user asks "can my website be installed like an app?" or "how do I make my site work offline?" — even if they don't use the word PWA. ## Deliverables Checklist Every PWA implementation must include these files at minimum: - [ ] `index.html` — Links manifest, registers service worker - [ ] `manifest.json` — Full app metadata and icon set - [ ] `sw.js` — Service worker with install, activate, and fetch handlers - [ ...

Details

Author
davila7
Repository
davila7/claude-code-templates
Created
11 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

progressive-web-app

Build Progressive Web Apps (PWAs) with offline support, installability, and caching strategies. Trigger whenever the user mentions PWA, service workers, web app manifests, Workbox, 'add to home screen', or wants their web app to work offline, feel native, or be installable.

39,350 Updated today
sickn33
Web & Frontend Solid

progressive-web-app

Progressive Web Apps with service workers, web manifest, offline support, installation prompts. Use for installable web apps, offline functionality, push notifications, or encountering service worker registration, cache strategy, manifest configuration errors.

162 Updated 2 weeks ago
secondsky
Web & Frontend Listed

fec-pwa-implementation

Use when adding or reviewing Progressive Web App capabilities such as installability, manifest metadata, Service Worker registration, Workbox caching, offline fallback, app update prompts, maskable icons, or iOS PWA compatibility. Do not use for general API caching or non-installable performance tuning; Chinese triggers include PWA, 离线, Service Worker.

14 Updated today
bovinphang
Code & Development Listed

pwa-review

Comprehensive 185-point PWA audit beyond Lighthouse - analyzes manifest, service worker, offline capabilities, security, iOS compatibility, and advanced PWA features

0 Updated today
Alexis315
API & Backend Listed

pwa-portal-app

Build, package, and upload a small PWA app for a self-hosted PWA Portal. Use when the user wants to create or modify a tool/app for their portal — e.g. "make me a receipt app for my portal", "build a quote calculator", "I need a contact form app". Handles scaffolding, implementation, packaging, and upload via the portal API.

0 Updated 2 days ago
jacob-scheatzle