pwa — for Claude Code community, for Claude Code, ide skills, code-generation, developer-tools, minimal-effective-prompt, semantic-search, starcoder2, Guideline, Framework

v1.0.0
GitHub

Acerca de este Skill

Escenario recomendado: Ideal for AI agents that need framework: next.js. Resumen localizado: But a bad PWA is worse than no PWA — stale content, broken offline states, and confusing installation prompts erode trust. It covers ai, automation, code-generation workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Características

Framework: Next.js
Service worker must not cache personalized/sensitive/authorized content
Cache invalidation on deploy must be correct (no stale content)
Would users actually want to install this as an app? Why or why not?
What should the offline experience be, and what is it today?

# Temas principales

for Claude Code code-generation developer-tools minimal-effective-prompt semantic-search starcoder2
SylphxAI SylphxAI
[4]
[3]
Actualizado: 4/4/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

Escenario recomendado: Ideal for AI agents that need framework: next.js. Resumen localizado: But a bad PWA is worse than no PWA — stale content, broken offline states, and confusing installation prompts erode trust. It covers ai, automation, code-generation workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

¿Por qué usar esta habilidad?

Recomendacion: pwa helps agents framework: next.js. But a bad PWA is worse than no PWA — stale content, broken offline states, and confusing installation prompts erode trust. This AI agent skill supports Claude Code

Mejor para

Escenario recomendado: Ideal for AI agents that need framework: next.js.

↓ Casos de uso accionables for pwa

Caso de uso: Framework: Next.js
Caso de uso: Service worker must not cache personalized/sensitive/authorized content
Caso de uso: Cache invalidation on deploy must be correct (no stale content)

! Seguridad y limitaciones

  • Limitacion: Service worker must not cache personalized/sensitive/authorized content
  • Limitacion: Cache invalidation on deploy must be correct (no stale content)
  • Limitacion: Requires repository-specific context from the skill documentation

About The Source

The section below is adapted from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Demo Labs

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ y pasos de instalación

These questions and steps mirror the structured data on this page for better search understanding.

? Preguntas frecuentes

¿Qué es pwa?

Escenario recomendado: Ideal for AI agents that need framework: next.js. Resumen localizado: But a bad PWA is worse than no PWA — stale content, broken offline states, and confusing installation prompts erode trust. It covers ai, automation, code-generation workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

¿Cómo instalo pwa?

Ejecuta el comando: npx killer-skills add SylphxAI/flow. Funciona con Cursor, Windsurf, VS Code, Claude Code y más de 19 IDE adicionales.

¿Cuáles son los casos de uso de pwa?

Los casos de uso principales incluyen: Caso de uso: Framework: Next.js, Caso de uso: Service worker must not cache personalized/sensitive/authorized content, Caso de uso: Cache invalidation on deploy must be correct (no stale content).

¿Qué IDE son compatibles con pwa?

Esta skill es compatible con Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Usa la CLI de Killer-Skills para una instalación unificada.

¿Tiene limitaciones pwa?

Limitacion: Service worker must not cache personalized/sensitive/authorized content. Limitacion: Cache invalidation on deploy must be correct (no stale content). Limitacion: Requires repository-specific context from the skill documentation.

↓ Cómo instalar este skill

  1. 1. Abre tu terminal

    Abre la terminal o línea de comandos en el directorio de tu proyecto.

  2. 2. Ejecuta el comando de instalación

    Ejecuta: npx killer-skills add SylphxAI/flow. La CLI detectará tu IDE o agente automáticamente y configurará la skill.

  3. 3. Empieza a usar el skill

    El skill ya está activo. Tu agente de IA puede usar pwa de inmediato en el proyecto actual.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below is adapted from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

pwa

Install pwa, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below is adapted from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

PWA Guideline

Tech Stack

  • Framework: Next.js
  • Platform: Vercel

Non-Negotiables

  • Service worker must not cache personalized/sensitive/authorized content
  • Cache invalidation on deploy must be correct (no stale content)

Context

A PWA is an opportunity to deliver native-like experience without an app store. But a bad PWA is worse than no PWA — stale content, broken offline states, and confusing installation prompts erode trust.

Consider: what would make users want to install this? What should work offline? How do we handle the transition between online and offline gracefully?

Driving Questions

  • Would users actually want to install this as an app? Why or why not?
  • What should the offline experience be, and what is it today?
  • What happens when users go offline in the middle of something important?
  • How do we handle cache invalidation without breaking the experience?
  • What push notification opportunities exist that we're not using?
  • What would make the installed experience better than the browser experience?

Habilidades relacionadas

Looking for an alternative to pwa or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumen localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
Inteligencia Artificial

widget-generator

Logo of f
f

Resumen localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat. It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

★ 149.6k
⑂ 0
Inteligencia Artificial

flags

Logo of vercel
vercel

Resumen localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Resumen localizado: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review. It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
Desarrollador