Help us improve
Share bugs, ideas, or general feedback.
From grimoire
Designs data and sync architecture for mobile or web apps that must function without a reliable network connection. Covers local storage, conflict resolution, optimistic UI, and sync queues.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireHow this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:design-offline-firstThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design data and sync architecture so the app works fully offline and merges changes correctly when connectivity returns.
Guides offline-first mobile architecture: local DB sync (WatermelonDB, Realm, Hive, SQLite), conflict resolution (LWW, CRDT), optimistic UI, background sync (WorkManager, BGTaskScheduler), connectivity detection. Use for reliable offline apps.
Builds Progressive Web Apps with offline support, installability, and caching strategies using service workers and web app manifests.
Develops React Native, Flutter, and native iOS/Android mobile apps using modern architecture patterns, cross-platform strategies, native integrations, offline sync, and app store optimization.
Share bugs, ideas, or general feedback.
Design data and sync architecture so the app works fully offline and merges changes correctly when connectivity returns.
Adopted by: Salesforce mobile, Google Docs, Notion, Linear, and Figma — all implement offline-first sync; CouchDB/PouchDB pattern is the canonical reference implementation for offline sync
Impact: Google research shows 53% of users abandon mobile sites that take over 3 seconds to load; apps that work offline eliminate the entire class of "no connection" failures that drive uninstalls; Figma reported offline support as a top enterprise adoption driver
Treating the network as unreliable by default — rather than an exception — produces more resilient applications. Offline-first means writes go to local storage immediately and sync to the server eventually, rather than blocking on network availability for every user action.
Optimistic write flow: User checks off a to-do → UI updates immediately → write queued to IndexedDB → background sync pushes to server → server confirms → queue entry removed. If offline for 3 days: all checkmarks persist locally, sync on reconnect, server applies all in order.