skills.rest
jitrapon
jitraponCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

kotlin-data-kmp-data-layer

Analyze Kotlin Multiplatform data-layer architecture for repository boundaries and source-of-truth design.

11|2|Updated Sep 8, 2015
Search Tags:#error handling#repository#architecture review#kotlin#multiplatform#data layer#source of truth
One-click install
npx skills add https://github.com/jitrapon/astro-mobile --skill kotlin-data-kmp-data-layer-jitrapon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kotlin-data-kmp-data-layer
Source: https://github.com/jitrapon/astro-mobile/tree/main/.claude/skills/kotlin-data-kmp-data-layer
Command: npx skills add https://github.com/jitrapon/astro-mobile --skill kotlin-data-kmp-data-layer-jitrapon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design, review, and implement Kotlin Multiplatform data layers that keep ownership clear, preserve a single source of truth, and hide transport and persistence details from upper layers.

Core Features & Use Cases

  • Repository Architecture Review: Check whether repositories are meaningful boundaries or just thin endpoint mirrors.
  • Source-of-Truth Design: Validate whether one local or in-memory authority is clearly defined and consistently updated.
  • KMP Data-Layer Safety: Confirm that APIs are main-safe, immutable at the boundary, and return consistent Result-based failures.
  • Use Case: Use this Skill when auditing a shared Kotlin module that coordinates local storage, remote sync, and business logic for Android and iOS.

Quick Start

Review the KMP data layer and identify repository boundaries, source-of-truth choices, and any violations of the Result-based API contract.

Frequently Asked Questions about kotlin-data-kmp-data-layer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a Kotlin Multiplatform data layer with a single source of truth?▼

A repository boundary in Kotlin Multiplatform is a meaningful architectural layer that coordinates local and remote data sources, rather than a thin endpoint mirror that directly exposes transport or persistence details to upper layers.

How do I handle errors consistently across shared Kotlin modules for Android and iOS?▼

To review a Kotlin Multiplatform data layer, validate repository boundaries, confirm source-of-truth design, check main-safe APIs, verify immutable boundary exposure, and ensure consistent Result-based error handling across local and remote data sources.

Does this KMP data layer review work for modules coordinating local and remote data sources?▼

Kotlin Multiplatform data layer safety requires main-safe APIs, immutable data exposure at boundaries, consistent Result-based error handling, and clear insulation of upper layers from transport or persistence details.

When should I not use a thin repository pattern in Kotlin Multiplatform?▼

To design a Kotlin Multiplatform data layer with a single source of truth, define one local or in-memory authority that is consistently updated, ensuring repositories coordinate remote sync and local storage while insulating upper layers from persistence details.

Related Skills

Explore More Software Engineering Skills→
huneyolivhuneyoliv
1

kotlin-build-kmp-gradle-governance

Review and design Gradle build structures for Kotlin Multiplatform projects.

Community
Advanced
cedric-champeixcedric-champeix
1

kotlin-data-kmp-data-layer

Identify best practices for Kotlin Multiplatform data layers with repositories and data sources.

Community
Advanced
Axel-DaMageAxel-DaMage
2

kotlin-specialist

Provide idiomatic Kotlin patterns for coroutine concurrency, KMP, Compose, and Ktor.

Community
Advanced
boomNDSboomNDS

architecture-patterns

Design backend architectures using Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

Community
Advanced