@sylphx/flow 2.28.1 → 2.28.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +10 -0
  2. package/assets/skills/pwa/SKILL.md +53 -9
  3. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,15 @@
1
1
  # @sylphx/flow
2
2
 
3
+ ## 2.28.2 (2025-12-19)
4
+
5
+ Enhance PWA skill with comprehensive native app parity checklist (35 capabilities)
6
+
7
+ ### 📚 Documentation
8
+
9
+ - **skills:** expand PWA native parity to 35 capabilities ([8d32115](https://github.com/SylphxAI/flow/commit/8d321157ff66894f8b4fc6689eee39b6ce9176d1))
10
+ - **skills:** remove priority categorization from PWA skill ([64d3966](https://github.com/SylphxAI/flow/commit/64d39660da95fc3b03c03534e906d0a9d81e9e1f))
11
+ - **skills:** enhance PWA skill with native app parity checklist ([8840a51](https://github.com/SylphxAI/flow/commit/8840a51e0fa3e9e1c638ca4a101235a9169edca9))
12
+
3
13
  ## 2.28.1 (2025-12-19)
4
14
 
5
15
  ### 🐛 Bug Fixes
package/assets/skills/pwa/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: pwa
3
- description: PWA - service workers, offline support. Use when building PWA features.
3
+ description: PWA - native app parity, offline-first, engagement. Use when building installable web apps.
4
4
  ---
5
5
 
6
6
  # PWA Guideline
@@ -8,24 +8,68 @@ description: PWA - service workers, offline support. Use when building PWA featu
8
8
  ## Tech Stack
9
9
 
10
10
  * **Framework**: Next.js
11
+ * **Service Worker**: Serwist (Next.js integration)
11
12
  * **Platform**: Vercel
12
13
 
13
14
  ## Non-Negotiables
14
15
 
15
16
  * Service worker must not cache personalized/sensitive/authorized content
16
17
  * Cache invalidation on deploy must be correct (no stale content)
18
+ * Offline experience must be functional, not just a fallback page
19
+ * Installation prompt must be contextual (after value demonstrated)
20
+
21
+ ## Native App Parity
22
+
23
+ | Capability | API |
24
+ |------------|-----|
25
+ | True offline | Cache API + localStorage/IndexedDB |
26
+ | Background sync | Background Sync API |
27
+ | App icon badge | Badging API |
28
+ | Local notifications | Notifications API |
29
+ | Push notifications | Web Push API |
30
+ | App shortcuts | manifest.json `shortcuts` |
31
+ | File handling | File Handling API |
32
+ | Protocol handling | registerProtocolHandler |
33
+ | Pull-to-refresh | Touch events + CSS |
34
+ | View transitions | View Transitions API |
35
+ | Bottom sheets | CSS + touch gestures |
36
+ | Skeleton loading | CSS + React Suspense |
37
+ | Swipe gestures | Touch/Pointer events |
38
+ | Haptic feedback | Vibration API |
39
+ | Sound effects | Web Audio API |
40
+ | Media controls | Media Session API |
41
+ | Wake lock | Screen Wake Lock API |
42
+ | Orientation lock | Screen Orientation API |
43
+ | Fullscreen | Fullscreen API |
44
+ | Picture-in-Picture | PiP API |
45
+ | Share | Web Share API |
46
+ | Receive share | Share Target API |
47
+ | Clipboard | Clipboard API |
48
+ | Camera/Mic | MediaDevices API |
49
+ | Geolocation | Geolocation API |
50
+ | Motion sensors | DeviceMotion/Orientation |
51
+ | Bluetooth | Web Bluetooth API |
52
+ | NFC | Web NFC API |
53
+ | Barcode scan | Barcode Detection API |
54
+ | Speech | Web Speech API |
55
+ | Payments | Payment Request API |
56
+ | Credentials | Credential Management API |
57
+ | Idle detection | Idle Detection API |
58
+ | Network status | Network Information API |
59
+ | Reduced motion | `prefers-reduced-motion` |
60
+ | Window controls | Window Controls Overlay |
17
61
 
18
62
  ## Context
19
63
 
20
- 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.
64
+ PWA goal: users forget they're in a browser. The gap between "website" and "app" is measured in micro-interactions — haptics, gestures, offline resilience, and engagement hooks.
21
65
 
22
- Consider: what would make users want to install this? What should work offline? How do we handle the transition between online and offline gracefully?
66
+ A bad PWA is worse than no PWA. But a great PWA can match 90% of native with 10% of the effort.
23
67
 
24
68
  ## Driving Questions
25
69
 
26
- * Would users actually want to install this as an app? Why or why not?
27
- * What should the offline experience be, and what is it today?
28
- * What happens when users go offline in the middle of something important?
29
- * How do we handle cache invalidation without breaking the experience?
30
- * What push notification opportunities exist that we're not using?
31
- * What would make the installed experience better than the browser experience?
70
+ * What breaks when the user goes offline mid-action?
71
+ * What would make users install this instead of bookmarking?
72
+ * Which native gestures (swipe, pull, long-press) are missing?
73
+ * What local notifications would drive daily engagement?
74
+ * Where does the app feel "webby" instead of native?
75
+ * What's the first thing users see when they open the installed app?
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sylphx/flow",
3
- "version": "2.28.1",
3
+ "version": "2.28.2",
4
4
  "description": "One CLI to rule them all. Unified orchestration layer for AI coding assistants. Auto-detection, auto-installation, auto-upgrade.",
5
5
  "type": "module",
6
6
  "bin": {