kotlin-platform-kmp-bridges

Audit Kotlin Multiplatform bridge designs for source-set placement and minimal expect/actual usage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and review Kotlin Multiplatform bridges to keep platform-specific code at the edges while maximizing shared logic, reducing unnecessary expect/actual usage, and preserving clear abstraction boundaries.

Core Features & Use Cases

  • Enforces correct source-set placement to maximize commonMain sharing.
  • Guides hierarchical sharing and minimal platform splits to avoid duplication.
  • Promotes stable shared contracts and conservative use of expect/actual, with explicit entry-point wiring when needed.

Quick Start

Audit the Kotlin Multiplatform project and move platform-specific logic into edge-case bridges, favor shared contracts in commonMain.

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 reduce unnecessary expect/actual usage in Kotlin Multiplatform?

Evaluate intermediate source sets and platform-family APIs to maximize shared logic, keeping native code separated through stable interfaces and explicit entry-point wiring that prevents vendor leakage.

What is the best way to structure Kotlin Multiplatform source sets for clean sharing?

The best way to structure Kotlin Multiplatform source sets is to enforce correct placement, guide hierarchical sharing, and align with the default hierarchy template to maximize commonMain sharing and avoid platform duplication.

How does a Kotlin Multiplatform bridge design prevent vendor leakage?

A Kotlin Multiplatform bridge design prevents vendor leakage by documenting stable interfaces and guidelines that keep platform-specific code at the edges, ensuring native code remains properly separated from shared contracts.

When do I need to use intermediate source sets in a KMP project?

You need intermediate source sets in a KMP project when evaluating platform-family APIs and hierarchical sharing to minimize platform splits, avoid duplication, and properly separate native code from shared logic.

Does Kotlin Multiplatform bridge design require explicit entry-point wiring?

Kotlin Multiplatform bridge design requires explicit entry-point wiring when needed to promote stable shared contracts and conservative use of expect/actual, ensuring clean abstraction boundaries across platforms.