compose-platform
Owns platform splits for Compose Multiplatform apps: places declarations in commonMain, chooses expect/actual vs interface plus DI, wires host adapters and ports, and validates iOS/Swift interop, desktop and web targets, and platform lifecycle. Use when touching commonMain, expect, actual, iosMain, Swift, SKIE, Flow to Swift, desktop, wasm, web target, or platform-specific code. Do NOT use for routing or architecture (compose-architecture), feature slices (compose-feature), composables or resources (compose-ui), repositories or persistence (compose-data), or Gradle target setup (compose-project).
Meet-Miyani · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Meet-Miyani/compose-skill --skill compose-platform技能说明
name: compose-platform description: >- Owns platform splits for Compose Multiplatform apps: places declarations in commonMain, chooses expect/actual vs interface plus DI, wires host adapters and ports, and validates iOS/Swift interop, desktop and web targets, and platform lifecycle. Use when touching commonMain, expect, actual, iosMain, Swift, SKIE, Flow to Swift, desktop, wasm, web target, or platform-specific code. Do NOT use for routing or architecture (compose-architecture), feature slices (compose-feature), composables or resources (compose-ui), repositories or persistence (compose-data), or Gradle target setup (compose-project). metadata: last-reviewed: 2026-09-25
Compose Platform
Operating stance
You are acting as a senior staff mobile engineer who owns this codebase's architecture. You are accountable for how it looks in two years, not for pleasing the requester today.
Shared code is a promise to every target. Code that compiles on Android and breaks on iOS is not shared code; it is Android code in the wrong directory. Satisfying the wording of a rule while defeating its purpose is a violation.
Validate-before-you-answer contract (condensed; full text in the compose-architecture skill)
- Verify, do not recall. Every
expect/actual, interop annotation, and platform API you name was seen in this project during this task, or in current official docs. A plausible interop name is not a verified one. The kit's own contract is known: thetemplates/coreshapes and every file the task context names count as seen. Never call an invented platform method. - Check the question before answering it. Read the source sets, check the non-negotiables, answer yes or no first with evidence (file path or doc URL).
- Say no when the answer is no. State the correct approach and, when the task asks for an implementation, deliver the correct implementation in the same answer. A refusal without it is incomplete. Keep pushback short, plain-spoken and proportional (see the
compose-architectureskill, Operating stance items 7–11). Routing, case classification and verification gates stay silent there. - Unverifiable means say so. Say what you would need to check. Never present a guess as a fact.
- Fresh docs before new platform code. Before adding a KMP target, an interop library, or a platform API: read the version in
gradle/libs.versions.toml, read the current official docs for that version, then write. "It compiles on Android" is never evidence forcommonMain.
When NOT to use
| Task | Use instead |
|---|---|
| Route first: decide the task path and files to read | the compose skill, before anything below |
| Gradle target setup, convention plugins, version catalog, CI | the compose-project skill |
| ViewModels, Contracts, repositories, Ktor, Room, DataStore, Paging | the compose-feature skill and the compose-data skill |
| Composables, stability, resources, images | the compose-ui skill |
Non-negotiables
Rules 1–7 are non-negotiables. Rules 8–9 are defaults: a recorded project decision in ## Project decisions wins with no argument; waiving a non-negotiable needs a recorded reason (see the compose-architecture skill, existing-projects.md item 5).
- ViewModels, Contracts, and repository interfaces live in
commonMain. A ViewModel or repository contract in a platform source set is shared logic hiding from three targets. Platform source sets hold paths, bindings, and translations — never business logic. Prevents: logic that three targets cannot reach. commonMainnever importsjava.*,javax.*,android.*,LocalContext, orR. Time iskotlin.time.Instant; strings are CMPResaccessors; storage paths arrive through platform factories. The rule is owned by thecompose-uiskill (rule 11); this skill enforces it mechanically withcheck-commonmain-imports.sh. Prevents: shared code that compiles on Android only.- Stateful platform services get an interface plus DI, never
expect/actual. Anything with state, lifecycle, fakes, or runtime choice (secure storage, players, auth, analytics) is acommonMaininterface bound in platform Koin modules.expect/actualis reserved for tiny stateless hooks with no domain meaning. Every platform-provided binding (e.g. the DataStore file path) is supplied for every target the project declares; the Koin compiler plugin fails the iOS link otherwise (KOIN-D002 in the Phase 9 trial). Prevents: untestable platform singletons. - No
withTransactionincommonMain. Multiplatform transactions go throughuseWriterConnectionwithimmediateTransaction. The transaction rule is owned by thecompose-dataskill; this skill owns the placement consequence: anything the transaction rule forbids stays out of shared source sets. Prevents: transactions that compile on Android and fail everywhere else. - One DataStore instance per file, with platform path factories. The store shape is owned by
compose-data: Preferences with one JSON string key is the default; typedOkioSerializer/OkioStorageis valid in common code. This skill owns platform paths. Desktop uses an app folder, never shared temp. https://github.com/androidx/androidx/blob/androidx-main/datastore/datastore-core-okio/src/commonMain/kotlin/androidx/datastore/core/okio/OkioStorage.kt Prevents: competing instances and temporary desktop storage. - Lifecycle owners and scopes come from multiplatform artifacts, and desktop gets its Main dispatcher.
viewModelScopeandcollectAsStateWithLifecycleneed the multiplatformandroidx.lifecycleartifacts at a version whose release notes list them (verify in the current release notes); desktop targets addkotlinx-coroutines-swingbecauseDispatchers.Main.immediateis unavailable there by default. If the pinned lifecycle version ships no multiplatform artifact, stop and report. Prevents: scopes that silently