skills.rest
huneyoliv
huneyolivCOMMUNITY
Explore all skills by this author →
GitHub

kotlin-data-kmp-data-layer

Design and review Kotlin Multiplatform data layers with ownership and API guidelines.

1|Updated Apr 10, 2026
Search Tags:#API design#source-of-truth#data layer#Kotlin Multiplatform#repository design
One-click install
npx skills add https://github.com/huneyoliv/ubus-ui --skill kotlin-data-kmp-data-layer-huneyoliv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kotlin-data-kmp-data-layer
Source: https://github.com/huneyoliv/ubus-ui/tree/main/.agents/kotlin-data-kmp-data-layer
Command: npx skills add https://github.com/huneyoliv/ubus-ui --skill kotlin-data-kmp-data-layer-huneyoliv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide for designing and reviewing Kotlin Multiplatform data layers, addressing various aspects like ownership, source-of-truth, API shape, and more.

Core Features & Use Cases

  • Design Guidelines: Offers best practices for KMP data layer architecture.
  • Review Checklist: Includes dimensions to assess the quality of the data layer.
  • Implementation Examples: Provides examples of how to implement best practices.
  • Use Case: When developing a Kotlin Multiplatform project, use this Skill to ensure a robust and efficient data layer.

Quick Start

Run the 'kotlin-data-kmp-data-layer' skill to review the data layer of your Kotlin Multiplatform project.

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 single source of truth for a Kotlin Multiplatform data layer?▼

To establish a single source of truth in a Kotlin Multiplatform data layer, apply structured repository design guidelines that enforce clear ownership and consistent API shapes across shared modules.

What are the best practices for Kotlin Multiplatform repository design and API shape?▼

Best practices for Kotlin Multiplatform repository design involve structuring clear ownership boundaries, defining consistent API shapes, and applying review checklists to ensure your data layer remains robust and maintainable.

How do I review an existing Kotlin Multiplatform data layer for maintainability?▼

Review a Kotlin Multiplatform data layer for maintainability by assessing it against a structured checklist focused on source-of-truth validation, API design quality, and clear ownership boundaries.

Can I use these data layer guidelines for any Kotlin Multiplatform project scale?▼

These Kotlin Multiplatform data layer guidelines apply to any project scale by focusing on core architectural principles like ownership and API design rather than specific scale constraints, ensuring broad applicability.

Why does my Kotlin Multiplatform data layer have inconsistent state across platforms?▼

Inconsistent state across platforms in a Kotlin Multiplatform data layer typically stems from lacking a defined single source of truth and unclear repository ownership boundaries within the shared architecture.

Related Skills

Explore More Software Engineering Skills→
ROYCE-8425ROYCE-8425
1

android-clean-architecture

Guide Clean Architecture implementation for Android and Kotlin Multiplatform projects.

Community
Advanced
nazrulsoftwaredevnazrulsoftwaredev

compose-multiplatform-patterns

Standardize UI architecture and state management for Compose Multiplatform applications.

Community
Advanced
kedokato-devkedokato-dev

kotlin-coroutines

Implement advanced Kotlin coroutine patterns with Flow, Channels, and structured concurrency.

Community
Advanced
riftzen-bitriftzen-bit

android-clean-architecture

Organize Android and Kotlin Multiplatform projects into clean architecture layers.

Community
Advanced