kotlin-multiplatform

Evaluate Kotlin Multiplatform adoption and module strategy across JVM, Android, iOS, and JS targets.

Updated Apr 8, 2026

Search Tags:#architecture #publishing #kotlin #multiplatform #compose-multiplatform #expect-actual #gradle-dsl

Ready to run

npx skills add https://github.com/ClankerGuru/opsx --skill kotlin-multiplatform-clankerguru

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kotlin-multiplatform
Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/kotlin-multiplatform
Command: npx skills add https://github.com/ClankerGuru/opsx --skill kotlin-multiplatform-clankerguru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps engineering teams evaluate Kotlin Multiplatform adoption and module structure, reducing architecture risk and boilerplate when choosing between JVM, Android, iOS, and JS targets.

Core Features & Use Cases

Decide on when to adopt Kotlin Multiplatform and how to structure a module layout (commonMain, platform-specific sources, and target hierarchies).
Assess toolchains and DSLs (kotlin { } blocks, Compose Multiplatform, and publishing considerations) for a production-grade library or app.
Use case: plan a migration or new project with clear target coverage, dependencies, and build configuration to minimize cross-target friction.

Quick Start

Outline a Kotlin Multiplatform module plan for a new project.

Frequently Asked Questions about kotlin-multiplatform

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

FAQPage Schema

How do I structure Kotlin Multiplatform modules for a new project?▼

Structure Kotlin Multiplatform modules by defining a clear target hierarchy and separating commonMain sources from platform-specific sources to minimize cross-target friction. This approach ensures proper architecture for JVM, Android, iOS, and JS targets.

When should I adopt Kotlin Multiplatform for my application?▼

Adopt Kotlin Multiplatform when you need to share business logic across JVM, Android, iOS, and JS targets while reducing architecture risk and boilerplate. Evaluate your production-grade toolchain and dependency requirements to determine if migration fits your project scope.

What's the best way to configure Gradle DSL for Kotlin Multiplatform publishing?▼

Configure Gradle DSL for Kotlin Multiplatform publishing by defining targets and source-set hierarchies inside the kotlin block. Assess Compose Multiplatform dependencies and publishing considerations to ensure proper artifact distribution across your required platforms.

How does expect actual work in Kotlin Multiplatform architecture?▼

Expect actual in Kotlin Multiplatform architecture allows you to declare common API expectations in commonMain and provide actual platform-specific implementations. This mechanism reduces boilerplate while maintaining consistent interfaces across JVM, Android, iOS, and JS targets.

Does Compose Multiplatform support iOS and JS targets?▼

Yes, Compose Multiplatform supports iOS and JS targets alongside Android and JVM. You can assess the toolchain and DSL configurations to build production-grade applications with shared UI components across your defined target hierarchy.

What are the limitations of Kotlin Multiplatform default source-set hierarchies?▼

Default source-set hierarchies in Kotlin Multiplatform may limit granular platform-specific sharing between intermediate targets like JVM and Android. Evaluate your module strategy and dependency decisions to anticipate constraints when configuring custom source-sets for complex production environments.