cmp-doctorlisted

Diagnose and heal both the toolchain AND the project a Kotlin/Compose Multiplatform (CMP/KMP) build needs. Use this when the user wants to set up or fix their CMP/KMP toolchain, install the Android SDK / AVD / emulator for KMP, install Appium and its drivers for a Compose Multiplatform app, set up JDK 17 / Xcode / CocoaPods / XcodeGen for KMP, or asks "set up CMP toolchain", "install Appium for KMP", "install Android SDK for Compose Multiplatform", "why won't my KMP project build", "my Compose Multiplatform build fails", "kotlin and ksp version mismatch", "check my version catalog", "prepare my machine for KMP Android + iOS", or "fix my Kotlin Multiplatform environment". When run inside ANY Gradle/KMP project (not just create-cmp-scaffolded ones) it additionally diagnoses the project itself: kotlin↔ksp lockstep, drift vs proven-green version sets, the KSP2/iOS Room catch-22, local.properties/SDK wiring, ~/.konan bloat, and free disk space — with --fix applying the safe heals. Idempotent, OS-aware, and consent
kvdm-co-pilot/create-cmp · ★ 0 · AI & Automation · score 72

Install: claude install-skill kvdm-co-pilot/create-cmp

# cmp-doctor — bootstrap the CMP toolchain & diagnose the project Your job: get the machine to a state where a CMP/KMP project can build (Android, and iOS on macOS) and run device tests — and, when run inside a project, get the *project* to a buildable state too. (The stamped E2E harness is Maestro — `curl -fsSL https://get.maestro.mobile.dev | bash`; the Appium drivers below serve the legacy pre-Maestro path.) You wrap the engine's bootstrap (`src/doctor.mjs` per CONTRACT/DESIGN; exposed on the CLI as the `doctor` subcommand). **Do not hand-roll installs in bash** when the engine can do it — the engine is idempotent and verifies each tool. Use this skill to drive it and to relay its consent prompts. ## What it checks, then offers to install - **JDK 17** (Temurin, via Homebrew or SDKMAN). - **Android SDK + cmdline-tools** via `sdkmanager` (platform, build-tools, platform-tools, emulator, a system image) and a bootable **AVD**. - **Xcode + Command Line Tools** — checks `xcode-select`. Xcode itself cannot be installed from the CLI; the App Store step is surfaced as the *one* unavoidable manual action and handled gracefully. - **CocoaPods** and **XcodeGen** (Homebrew). - **Node + Appium 3.x** and its **drivers** (`appium driver install uiautomator2`, and `xcuitest` on macOS), each verified — legacy e2e path only; Maestro is a separate one-line install. - **adb / emulator reverse-port** wiring for the test harness. On **Linux**, it scopes to Android-only and says so exp