pwa

PWA - native app parity, offline-first, engagement. Use when building installable web apps.

⭐4stars🔀3forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for building high-performance Progressive Web Apps (PWAs) using Next.js and Serwist. It focuses on achieving native app parity through offline-first architecture, optimized service worker caching, and enhanced user engagement via mobile-centric interactions like haptics and gestures.

Use Cases

  • Developing offline-ready web applications that maintain core functionality and data integrity during network disruptions.
  • Transforming Next.js websites into installable desktop and mobile apps with full manifest and multi-platform icon compliance.
  • Implementing native-like UX features including haptic feedback, custom gestures, and pull-to-refresh to bridge the gap between web and mobile.
  • Configuring secure service worker caching strategies to ensure fast load times and correct cache invalidation on Vercel deployments.
namepwa
descriptionPWA - native app parity, offline-first, engagement. Use when building installable web apps.

PWA Guideline

Tech Stack

  • Framework: Next.js (with Turbopack)
  • Service Worker: Serwist (Next.js integration)
  • Platform: Vercel

Non-Negotiables

  • Service worker must not cache personalized/sensitive/authorized content
  • Cache invalidation on deploy must be correct (no stale content)
  • Offline experience must be functional, not just a fallback page
  • Installation prompt must be contextual (after value demonstrated)
  • Complete manifest.webmanifest with all required fields
  • All required icons present (favicon, apple-touch-icon, PWA icons, maskable)

Context

PWA goal: users forget they're in a browser. The gap between "website" and "app" is measured in micro-interactions — haptics, gestures, offline resilience, and engagement hooks.

A bad PWA is worse than no PWA. But a great PWA can match 90% of native with 10% of the effort.

Driving Questions

  • What breaks when the user goes offline mid-action?
  • What would make users install this instead of bookmarking?
  • Which native gestures (swipe, pull, long-press) are missing?
  • What local notifications would drive daily engagement?
  • Where does the app feel "webby" instead of native?
  • What's the first thing users see when they open the installed app?