What problem does it solve? Kotlin Multiplatform generates the Swift-facing API automatically, and the result is often ugly or broken: mangled method names, missing default arguments, sealed classes that don't map to Swift enums, Flow without async/await, and functions that vanish from the Objective-C header. This Skill diagnoses the exact interop limitation behind each symptom and applies the standard upstream fix in the Kotlin API. ## Core Features & Use Cases - Header-driven diagnosis: Builds the iOS framework and reads the generated Objective-C header to see exactly what Swift sees before guessing at causes. - Symptom-to-fix mapping: Covers overload renaming, default arguments, sealed class bridging, Flow/suspend exposure, generics erasure, @HiddenFromObjC, Result bridging, and @Throws exception handling. - Tooling guidance: Recommends SKIE or KMP-NativeCoroutines where they fix categories of problems automatically, plus guardrails like iOS compile tests to catch regressions. - Use Case: The iOS team reports that a suspend function appears as a completion-handler method and a sealed class shows up as plain classes. Use this Skill to identify the interop limitation, adopt SKIE, and verify the regenerated header exposes Swift-native async functions and enums. ## Quick Start Ask the assistant to diagnose why Swift cannot see or cleanly call a specific Kotlin API in your KMP shared module and apply the appropriate interop fix.
