OpenSkillIndex← back to search
claude-code

Flow pwa

PWA - service workers, offline support. Use when building PWA features.

install
source · Clone the upstream repo
git clone https://github.com/SylphxAI/flow
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/SylphxAI/flow "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/pwa" ~/.claude/skills/sylphxai-flow-pwa && rm -rf "$T"
manifest: .claude/skills/pwa/SKILL.md
source content

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?