kotlin-platform-kmp-bridges

Optimize Kotlin Multiplatform boundaries by clarifying edge placement and sharing rules.

63|6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/mmiani/kotlin-kmp-claude-agent-skills --skill kotlin-platform-kmp-bridges-mmiani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-platform-kmp-bridges
Source: https://github.com/mmiani/kotlin-kmp-claude-agent-skills/tree/main/skills/kotlin-platform-kmp-bridges
Command: npx skills add https://github.com/mmiani/kotlin-kmp-claude-agent-skills --skill kotlin-platform-kmp-bridges-mmiani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams design and review platform-specific integrations and shared-to-native boundaries in Kotlin Multiplatform projects, reducing leakage of native APIs into shared code and clarifying module ownership.

Core Features & Use Cases

  • Guidance on correct source-set placement and hierarchical sharing to maximize reuse
  • Evaluation of expect/actual usage with recommendations for interfaces and entry points
  • Clear decision criteria for bridging platform APIs and isolating platform-specific code at the edges

Quick Start

Apply these guidelines to your current KMP project to place platform-specific code at the edges.

Frequently Asked Questions about kotlin-platform-kmp-bridges

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

FAQPage Schema
How do I prevent native API leakage in Kotlin Multiplatform shared code?

Define sharing rules for Kotlin Multiplatform source-set hierarchies by evaluating edge placement and maximizing intermediate shared code to optimize platform-specific boundaries and reuse.

What is the best way to use expect/actual in Kotlin Multiplatform architecture?

Evaluate expect/actual usage in Kotlin Multiplatform by applying clear decision criteria for bridging platform APIs, controlling their application, and isolating platform-specific code at the edges.

How do I structure source-set hierarchies for Android and iOS targets in KMP?

Optimize platform-specific boundaries in Kotlin Multiplatform by clarifying edge placement and sharing rules across Android, iOS, and native targets, including source-set hierarchies and intermediate shared code.

When should I isolate platform-specific code at the edges in Kotlin Multiplatform?

Apply sharing-first placement rules during architecture reviews to isolate platform-specific code at the edges, reducing native API leakage into shared modules and clarifying ownership.

Does this approach work for architecture reviews and module boundary decisions in KMP?

Guide teams to optimize platform-specific boundaries in Kotlin Multiplatform projects by clarifying edge placement and sharing rules, applicable during architecture reviews, module boundary decisions, and bridge design across Android, iOS, and native targets.