Implement Progressive Web App features for React and Svelte projects. This skill should be used when the user asks to 'make a PWA', 'add offline support', 'create a service worker', 'fix caching issues', or wants installable web apps. Keywords: PWA, service worker, offline, manifest, caching, installable, Workbox, vite-pwa.
npx skills add https://github.com/jwynia/agent-skills --skill pwa-development
Implement Progressive Web App features including service workers, caching strategies, offline support, and installation prompts for React and Svelte applications.
Use this skill when:
Do NOT use this skill when:
PWAs fail when offline behavior is an afterthought. A PWA is not "add service worker to existing app." It's a fundamental architectural decision about data flow, caching, and connectivity failure.
Symptoms: No manifest.json, no service worker, online-only
Interventions:
scripts/manifest-generator.ts to create manifest<link rel="manifest"> to HTML headscripts/sw-scaffolder.tsSymptoms: Manifest exists but SW missing, breaks offline
Key Questions:
Interventions:
scripts/cache-strategy-advisor.tsSymptoms: Stale content, unexpected caching behavior
Interventions:
scripts/pwa-audit.tsdata/caching-strategies.jsonSymptoms: Users stuck on old versions, multiple refreshes needed
Interventions:
assets/update-prompt.tsx)Symptoms: User actions lost offline, no sync indicator
Interventions:
Symptoms: Works on Android, breaks on iOS
Interventions:
data/ios-quirks.jsonIndicators: Lighthouse PWA 100, works offline, updates cleanly
| Strategy | Use For | Behavior |
|----------|---------|----------|
| Cache First | Static assets, fonts | Serve from cache, update in background |
| Network First | API data, user content | Try network, fall back to cache |
| Stale While Revalidate | Semi-static content | Serve stale, update cache for next time |
| Network Only | Auth, real-time data | Always network, no caching |
| Script | Purpose |
|--------|---------|
| manifest-generator.ts | Generate manifest.json |
| sw-scaffolder.ts | Generate service worker |
| cache-strategy-advisor.ts | Recommend caching strategies |
| pwa-audit.ts | Validate PWA configuration |
Precaching every asset - massive initial download.
Fix: Precache only critical app shell. Runtime cache content.
Never expiring caches - stale content forever.
Fix: Cache versioning, delete old on activate, set max age.
Forcing updates without notification.
Fix: Notify user, let them choose when to refresh.
Building for Chrome, testing iOS last.
Fix: Test iOS early. Accept iOS limitations.
npm i -D vite-plugin-pwa
npm i -D @vite-pwa/sveltekit
npm i next-pwa
See data/framework-patterns.json for configuration.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take jwynia/pwa-development from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm.
Without those the skill loads but fails at the first command.