mobile-kmp
Skill8 starsChanged 59 days agoMITView on GitHub
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.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- mobile-accessibilitySkill
- mobile-analyticsSkill
- mobile-androidSkill
- mobile-architectureSkill
- mobile-authSkill
- mobile-billingSkill
- mobile-ciSkill
- mobile-code-reviewSkill
- mobile-debugSkill
- mobile-detect-stackSkill
- mobile-firebaseSkill
- mobile-flutterSkill
- mobile-hardwareSkill
- mobile-iosSkill
- mobile-migrationSkill
- mobile-networkingSkill
- mobile-notificationsSkill
- mobile-observabilitySkill
- mobile-offline-syncSkill
- mobile-performanceSkill
- mobile-privacySkill
- mobile-releaseSkill
- mobile-rnSkill
- mobile-securitySkill
- mobile-testSkill
- mobile-ui-uxSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Read settings.gradle.kts, the affected module's build.gradle.kts, version catalog and source-set directories.
- Very specific: line 24
Use the topic skill for the requested work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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'sbuild.gradle.kts, version catalog and source-set directories. Record the configured targets;androidMainandiosMainare not proof that a target is built in CI. - Trace a real symbol from
commonMainthrough an interface orexpectdeclaration 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
actualimplementations, 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-androidormobile-iosonly for an affected host or target-specific implementation; do not apply native-app instructions blindly tocommonMain.
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.
Interface design
For UI/UX reviews, wireframes, design systems and screen redesigns, use mobile-ui-ux and its reference for this stack. For Apple targets, also consult its Apple design workflow; validate platform claims against current official guidance and the installed toolkit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

