# Build Offline-Ready Progressive Web Apps

Web apps can fail on unreliable connections and lack a clear installation experience. This skill provides PWA implementation examples for manifests, service workers, caching, and offline workflows.

## Install

```bash
npx skillstore add alinaqi/pwa-development
```

## Metadata

- Status: approved
- Slug: alinaqi-pwa-development
- Skillstore revision: r1
- Version status: missing
- Tree hash: 5bc7066fed15eb90f2f732001bafbbff34d5bdcb42b86b1ada78b54cba9ea6e5
- Author: alinaqi
- GitHub username: alinaqi
- Repository: https://github.com/alinaqi/maggy/tree/55aabe2493627e1de9cd09459d555181d66f3111/skills/pwa-development
- Ref: c993c6abcbffafea2683d7748b53b3dfaf438415
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands, network, env\_access
- Quality score: 62
- Public page: https://skillstore.pages.dev/skills/alinaqi-pwa-development
- Manifest: https://skillstore.pages.dev/api/skills/alinaqi-pwa-development/manifest

## Capabilities

- Provides basic and enhanced web app manifest examples, including icons, shortcuts, and share targets.
- Explains service worker registration, lifecycle events, cache strategies, and offline fallback pages.
- Shows Workbox runtime caching, expiration settings, and background sync for form submissions.
- Demonstrates install prompts, standalone detection, push subscriptions, and notification event handling.
- Includes Vite, Next.js, and Create React App configuration examples.
- Provides performance techniques, service worker update examples, and manual PWA testing checklists.

## Use Cases

- Add an Installable App Experience: Create a manifest, register a service worker, and add installation controls to an existing website.
- Support Field Work Without Connectivity: Plan offline fallback pages and queued form submissions for teams working with unreliable connections.
- Review PWA Release Readiness: Use the manifest, offline behavior, update, and performance checklists to organize browser testing.

## Prompt Templates

### Create a Basic Manifest

```
Create a web app manifest for [app name] at [start URL]. Include standalone display, theme colors, and required icon sizes.
```

### Add Offline Fallbacks

```
Add service worker registration and an offline fallback to [project]. Cache public assets only and restrict cleanup to this application.
```

### Configure Workbox Caching

```
Configure Workbox for [Vite project]. Choose strategies for public assets and API responses, set expiration limits, and exclude authenticated endpoints.
```

### Design a Secure Offline Workflow

```
Design offline submissions for [workflow] using Workbox background sync. Address account changes, sensitive data retention, duplicate submissions, and update testing.
```

## Limitations

- Contains documentation and examples, not an executable application or automated test suite.
- Requires project-specific backend endpoints, icons, push configuration, and helper functions.
- Browser support, framework packages, and Lighthouse guidance require verification against current versions.
- Cache examples require privacy controls and application-specific cleanup before production use.

## Best Practices

- Choose cache strategies by resource sensitivity and freshness needs; exclude private responses unless isolation and retention controls are explicit.
- Namespace application caches and remove only obsolete versions owned by the application.
- Test installation, offline behavior, queued submissions, and updates across target browsers using current tooling.

## Anti Patterns

- Copying broad API caching rules into authenticated applications without session isolation or logout cleanup.
- Deleting every origin cache except the current cache during service worker activation.
- Treating example framework commands or historical audit criteria as guaranteed current production guidance.

## Security Audit

- Audited at: 2026-11-07T14:39:23.433\+00:00
- Summary: All 92 static alerts are false positives for the reported threats, including Markdown backticks, fixed imports, routine requests, and misidentified identifiers. Two contextual risks remain: shared caches can retain private responses across sessions, and activation deletes unrelated caches on the same origin. No evidence found of prompt injection, credential theft, or malicious execution instructions.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0