How do I install the Mobile Kmp skill?

Run npx skillmds@latest add wrsilva/mobile-kmp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mobile Kmp safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mobile Kmp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mobile Kmp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mobile Kmp?

wrsilva (@wrsilva) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mobile Kmp by wrsilva — Agent Skill

Name: Mobile Kmp
Rating: 4.5 (4 reviews)
Author: wrsilva

Mobile Kmp

Works on Kotlin Multiplatform mobile projects with shared Kotlin source sets and Android/iOS targets. Use for architecture, tests, debugging, reviews, performance, security, accessibility, dependencies and releases when `org.jetbrains.kotlin.multiplatform` is applied; inspect actual targets, `commonMain`/`commonTest`, target source sets, Compose Multiplatform and the iOS framework/host app before giving platform advice.

wrsilva Updated Sep 22, 2026

File contents

Kotlin Multiplatform

KMP is a sharing mechanism, not a promise that both apps use the same UI or SDK. Resolve the module and target graph before choosing Android, iOS or shared-code guidance.

Question	Read
Which code and dependencies can be shared?	references/source-sets.md
How does shared Kotlin reach the iOS app?	references/apple-interop.md
Is UI shared with Compose Multiplatform or native on each target?	references/compose-ui.md
Which build, measurement or release task applies?	references/build-performance.md

Ground the answer

Read settings.gradle.kts, the affected module's build.gradle.kts, version catalog and source-set directories. Record the configured targets; androidMain and iosMain are not proof that a target is built in CI.
Trace a real symbol from commonMain through an interface or expect declaration to each configured implementation and its Android/iOS caller. Name the module, source set and owner at every boundary. For shared Compose UI, trace its host entry too.
Match validation to the changed boundary: shared Kotlin tests on configured targets, target tests for actual implementations, and host UI/device tests for behavior that crosses into Android or iOS. A JVM test is not iOS coverage.
Use the topic skill for the requested work. Use mobile-android or mobile-ios only for an affected host or target-specific implementation; do not apply native-app instructions blindly to commonMain.

The Kotlin Multiplatform source-set reference defines commonMain, commonTest and target compilations. Confirm DSL and task names in the project's installed Kotlin and Gradle versions.

---name: mobile-kmpdescription: Works on Kotlin Multiplatform mobile projects with shared Kotlin source sets and Android/iOS targets. Use for architecture, tests, debugging, reviews, performance, security, accessibility, dependencies and releases when `org.jetbrains.kotlin.multiplatform` is applied; inspect actual targets, `commonMain`/`commonTest`, target source sets, Compose Multiplatform and the iOS framework/host app before giving platform advice.---# Kotlin MultiplatformKMP is a sharing mechanism, not a promise that both apps use the same UI or SDK. Resolve the module and target graph before choosing Android, iOS or shared-code guidance.| Question | Read ||---|---|| Which code and dependencies can be shared? | [references/source-sets.md](references/source-sets.md) || How does shared Kotlin reach the iOS app? | [references/apple-interop.md](references/apple-interop.md) || Is UI shared with Compose Multiplatform or native on each target? | [references/compose-ui.md](references/compose-ui.md) || Which build, measurement or release task applies? | [references/build-performance.md](references/build-performance.md) |## Ground the answer1. Read `settings.gradle.kts`, the affected module's `build.gradle.kts`, version catalog and source-set directories. Record the configured targets; `androidMain` and `iosMain` are not proof that a target is built in CI.2. Trace a real symbol from `commonMain` through an interface or `expect` declaration to each configured implementation and its Android/iOS caller. Name the module, source set and owner at every boundary. For shared Compose UI, trace its host entry too.3. Match validation to the changed boundary: shared Kotlin tests on configured targets, target tests for `actual` implementations, and host UI/device tests for behavior that crosses into Android or iOS. A JVM test is not iOS coverage.4. Use the topic skill for the requested work. Use `mobile-android` or `mobile-ios` only for an affected host or target-specific implementation; do not apply native-app instructions blindly to `commonMain`.The [Kotlin Multiplatform source-set reference](https://kotlinlang.org/docs/multiplatform/multiplatform-dsl-reference.html) defines `commonMain`, `commonTest` and target compilations. Confirm DSL and task names in the project's installed Kotlin and Gradle versions.

Frequently asked questions