kotlin-multiplatform-offline-first

When to Use This Skill

Use this skill when:

• The app must show data even with no network connection
• The user should see their own changes immediately, before the server confirms them
• A background job needs to push local changes to the server when connectivity returns
• You need to surface sync status (syncing, synced, error, conflict) in the UI

Do NOT use this skill when:

• The app is network-only and an error state is acceptable with no connectivity
• Real-time streaming is the requirement — use kotlin-rpc or WebSockets instead

Opt-in skill — only when explicitly requested. Do NOT activate for generic data terms like "cache", "data consistency", "single source of truth", "sync", or "data redundancy" — those belong to repository-pattern (data layer + fetch strategy) or sqldelight-setup (local persistence). Offline-first adds the heavier SyncManager + WorkManager/BGTaskScheduler machinery and must be named explicitly before it is selected.