How do I install the Pwa Release skill?

Run npx skillmds@latest add ahs12/pwa-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pwa Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pwa Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pwa Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pwa Release?

ahs12 (@ahs12) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pwa Release by ahs12 — Agent Skill

Name: Pwa Release
Author: ahs12

File contents

PWA and Release

Read First

vite.config.ts for Vite, PWA, manifest, cache, and injected version settings.
src/main.tsx and PWA-related components for registration and update prompts.
public/, public/offline.html, Dockerfile, nginx.conf, and vercel.json for runtime behavior.
.github/workflows/build_test.yml and .github/workflows/release_dist.yml for CI and release packaging.
docs/VERSIONING.md for the version workflow, while treating package.json as the source of truth.

Change Rules

Preserve SPA fallback behavior for Vercel, Nginx, and the release ZIP.
Keep service-worker precache/runtime cache patterns, size limits, update prompts, and offline fallback intentional. Avoid caching secrets or mutable API responses indiscriminately.
Ensure public assets referenced by the manifest and includeAssets exist and are included in dist.
package.json owns the application version; builds inject it as __APP_VERSION__. Release tags must match the package version after removing an optional v prefix.
Do not manually edit generated dist/, dev-dist/, service-worker, or manifest output. Rebuild instead.
Remember that analytics and provider calls can still require network access even though core editing is offline-first.

Verification

Run pnpm run type-check, pnpm run lint, and pnpm run build.
Inspect dist/index.html, dist/sw.js, the manifest, fallback assets, and expected public assets after a build.
Perform a production preview smoke test for first load, refresh on a nested route, update prompt, installable manifest, and offline navigation when practical.
For Docker or release changes, verify the package and deployment artifact separately from the local Vite build.

---name: pwa-releasedescription: Safely change Vite, service-worker, offline fallback, cache, Docker, Vercel, or release-distribution behavior. Use when changing deployment configuration, public assets, versioning, or install/update flows.---# PWA and Release## Read First- `vite.config.ts` for Vite, PWA, manifest, cache, and injected version settings.- `src/main.tsx` and PWA-related components for registration and update prompts.- `public/`, `public/offline.html`, `Dockerfile`, `nginx.conf`, and `vercel.json` for runtime behavior.- `.github/workflows/build_test.yml` and `.github/workflows/release_dist.yml` for CI and release packaging.- `docs/VERSIONING.md` for the version workflow, while treating `package.json` as the source of truth.## Change Rules1. Preserve SPA fallback behavior for Vercel, Nginx, and the release ZIP.2. Keep service-worker precache/runtime cache patterns, size limits, update prompts, and offline fallback intentional. Avoid caching secrets or mutable API responses indiscriminately.3. Ensure public assets referenced by the manifest and `includeAssets` exist and are included in `dist`.4. `package.json` owns the application version; builds inject it as `__APP_VERSION__`. Release tags must match the package version after removing an optional `v` prefix.5. Do not manually edit generated `dist/`, `dev-dist/`, service-worker, or manifest output. Rebuild instead.6. Remember that analytics and provider calls can still require network access even though core editing is offline-first.## Verification- Run `pnpm run type-check`, `pnpm run lint`, and `pnpm run build`.- Inspect `dist/index.html`, `dist/sw.js`, the manifest, fallback assets, and expected public assets after a build.- Perform a production preview smoke test for first load, refresh on a nested route, update prompt, installable manifest, and offline navigation when practical.- For Docker or release changes, verify the package and deployment artifact separately from the local Vite build.

Frequently asked questions

Pwa Release