Skip to main content
Visual Arts & DesignWeb Polish29 lines

Progressive Web App and Offline Behavior

Add or repair a web app manifest, install experience and service worker offline behavior. Verify cache policy, updates, multiple tabs and signed-out data handling.

Quick Summary9 lines
Write an offline contract before registering a worker. List what must open after a previous successful visit, what can display stale data with a label, and which actions require a network. Distinguish a cold offline visit with no local resources from repeat use. Do not imply that a manifest provides offline behavior.

## Key Points

- [W3C Web Application Manifest](https://www.w3.org/TR/appmanifest/)
- [Service Workers specification](https://w3c.github.io/ServiceWorker/)
- [Chrome service worker lifecycle guidance](https://web.dev/articles/service-worker-lifecycle)
skilldb get web-polish-skills/progressive-web-appFull skill: 29 lines
Paste into your CLAUDE.md or agent config

Progressive Web App and Offline Behavior

Write an offline contract before registering a worker. List what must open after a previous successful visit, what can display stale data with a label, and which actions require a network. Distinguish a cold offline visit with no local resources from repeat use. Do not imply that a manifest provides offline behavior.

Define scope and cache boundaries

Set a consistent app identity, start URL, scope, name, icons and display settings in the manifest. Check those settings on the actual browser and OS. Treat browser install UI as optional enhancement and preserve the normal web experience. Use the existing service worker when possible and verify its script origin and scope. A worker can control only its permitted scope, and it may not control the first navigation.

Use versioned public assets and a deliberate request strategy. An immutable hashed asset can be safely cache-first within its release. A navigation may prefer network with a known offline fallback. Decide explicitly whether an API result is eligible for offline display and how to communicate age. Keep private data and account-specific responses out of shared caches unless an approved, user-scoped local data design handles them. Do not cache failed responses by default, queue unsafe writes automatically or replay old mutations on reconnect.

Verify an update across sessions

Plan for a new worker waiting while old tabs are still using old assets. Do not unconditionally activate a new release if it would strand old documents with incompatible code or remove assets they still need. If a user can choose to refresh, preserve unsaved work and load a consistent new version. Delete only obsolete caches owned by this app and do not assume other apps on the origin can share their names safely.

Run cold start, first controlled navigation, warm offline restart, failed route, update while two tabs are open and sign-out followed by another test account. Verify visible fallback and actual network/cache activity. Test manual install or browser install availability only where supported and distinguish installation, control and offline readiness in the receipt. Record browser versions, cache versions and any account cleanup or untested device behavior.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add web-polish-skills

Get CLI access →

Related Skills

Reference-Based UI Implementation Verification

Translate a supplied screenshot or design into a responsive implementation and verify matching layout, typography, spacing, assets and interaction at representative viewports.

Web Polish•29L

Responsive Repair

Fix broken responsive layouts in a vibecoded website — content overflowing on mobile, misaligned grids, missing breakpoint handling, touch targets that are too small, and navigation that doesn't adapt. Trigger when things "break on mobile," "look bad on tablet," or "don't resize properly."

Web Polish•301L

Build a Restaurant Website Customers Can Use

Build a mobile restaurant homepage with accessible menu, accurate hours and locations, and trustworthy booking or takeaway actions. Use when launching or repairing a local restaurant site.

Web Polish•29L

Typography Cleanup

Fix font chaos in a vibecoded website — too many font sizes, inconsistent weights, broken heading hierarchy, mismatched line heights, and mixed font families. Establish a clean type scale and apply it everywhere. Trigger when fonts "look off," headings are inconsistent, or there are too many text sizes.

Web Polish•255L

UI Audit

Audit a vibecoded or inconsistent website for visual and structural problems — mismatched components, font chaos, color drift, spacing irregularities, broken states, and missing interactions. Produces a prioritized fix list. Trigger when users say "this looks off," "make it consistent," "audit the UI," "fix the design," or "polish this site."

Web Polish•204L

Vibecode Upgrade

The comprehensive playbook for upgrading a vibecoded website from "it works" to "it feels premium." Combines all other web-polish skills into a prioritized workflow — audit, extract tokens, unify components, fix responsiveness, add polish. Trigger when users want to "upgrade the whole site," "make it look professional," "polish everything," or "it was vibecoded and needs to be cleaned up."

Web Polish•237L