mobile-offline-paritylisted

# Skill: Mobile Offline Parity ## Intent Ensure mobile and mobile-like requirements handle offline, intermittent connectivity, device constraints, and synchronization explicitly. This skill applies to native mobile, hybrid mobile, PWA, field apps, and operator apps running in constrained environments. ## Use when Use this skill when a REQ touches mobile apps, PWA behavior, offline mode, local storage, synchronization, field operations, device APIs, push notifications, camera, location, poor connectivity, or mobile UX. ## Do not use when Do not use this skill for desktop-only backend services, server-only APIs, or frontend pages with no mobile/offline/device behavior. ## Signals - The REQ mentions mobile, iOS, Android, React Native, Flutter, PWA, offline, sync, local storage, cache, device, camera, geolocation, push notification, field operator, tablet, handheld, or intermittent network. - Acceptance criteria include offline behavior or mobile responsiveness. - Design profile mentions mobile operator app, field app, industrial operator UI, or consumer mobile app. ## Required behavior - Define online, offline, reconnecting, synced, conflict, and failed-sync states when relevant. - Keep offline data boundaries explicit. - Avoid silent data loss. - Make synchronization idempotent where practical. - Document device permission assumptions. - Keep mobile UI accessible and usable on constrained screens. - Provide local tests for offline state transitions when the stack all