kmp-repository-pattern

When to Use This Skill

Use when you need to:

• Connect the network layer (Ktor) and local database (SQLDelight) into a unified data source
• Implement offline-capable features
• Ensure the UI always reflects local truth, not raw network responses
• Map network/database types to domain models at the correct boundary
• Implement optimistic updates (update UI immediately, sync in background)

Requires: kmp-network-layer, kmp-sqldelight-setup.

Trigger keywords: repository pattern, data layer, offline-first, cache-first, network-first, single source of truth, local cache, domain mapping, repository implementation, data source, optimistic update, sync strategy, data redundancy, content management, data handling, cache strategy, data consistency, data sync, fetch strategy, content duplication, in-memory repository, no backend yet, backend not ready, mock repository.

Freshness rule: Ktor and SQLDelight APIs change — recheck both before using this skill with a version upgrade, and verify the fetch-strategy examples against the current driver APIs.