kotlin-platform-kmp-bridges

Assesses and optimizes Kotlin Multiplatform project structure and implementation.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/huneyoliv/ubus-ui --skill kotlin-platform-kmp-bridges-huneyoliv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-platform-kmp-bridges
Source: https://github.com/huneyoliv/ubus-ui/tree/main/.agents/kotlin-platform-kmp-bridges
Command: npx skills add https://github.com/huneyoliv/ubus-ui --skill kotlin-platform-kmp-bridges-huneyoliv

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill aids developers in crafting effective Kotlin Multiplatform (KMP) architecture, ensuring that code is shared efficiently and platform-specific implementations are managed correctly.

Core Features & Use Cases

  • Source Set Management: Optimize code placement across different source sets for effective sharing and platform adaptation.
  • Shared-to-Native Boundaries: Encourage clear separation and minimal coupling between shared and platform-specific code.
  • Best Practices: Offers guidance on leveraging KMP features like expect/actual, interface-based dependency injection, and platform-family API access.
  • Use Case: For a project that requires both Android and iOS app development, this Skill can help ensure a robust and maintainable multiplatform codebase by avoiding unnecessary duplication and overuse of platform-specific code.

Quick Start

Execute the skill by reviewing the KMP project's architecture against the guidelines provided to identify potential improvements and optimizations.

Frequently Asked Questions about kotlin-platform-kmp-bridges

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

FAQPage Schema
What is the best way to organize Kotlin Multiplatform source sets for Android and iOS?

Organizing Kotlin Multiplatform source sets involves optimizing code placement to maximize platform-specific sharing and ensure efficient adaptation. This approach maintains clear separation and minimal coupling between shared and native code.

How do I manage expect and actual declarations to minimize coupling in KMP projects?

Managing expect and actual declarations requires establishing clear shared-to-native boundaries. By leveraging interface-based dependency injection and adhering to best practices, you ensure minimal coupling between shared and platform-specific code.

Does Kotlin Multiplatform work for sharing code across mobile, desktop, and web targets?

Kotlin Multiplatform supports sharing code across mobile, desktop, and web targets utilizing Kotlin/Native. Assessing your project structure ensures adherence to best practices and specific requirements for each platform target.

Why does my Kotlin Multiplatform architecture have unnecessary code duplication?

Unnecessary code duplication in Kotlin Multiplatform architecture often stems from inefficient source-set organization and poor abstraction. Optimizing project structure and applying proper expect/actual usage reduces duplication effectively.

When should I use interface-based dependency injection in Kotlin Multiplatform?

Interface-based dependency injection in Kotlin Multiplatform should be used to enforce clear separation and minimal coupling. It provides an effective alternative to overusing platform-specific code when accessing platform-family APIs.