What problem does it solve? Kotlin Multiplatform projects often end up with inconsistent Gradle setups: hardcoded dependency versions scattered across modules, Android entry points living inside the shared module (which breaks with AGP 9.0), and premature or missing convention plugins. This Skill defines clear conventions for module organization, a single version catalog, and when to introduce build-logic. ## Core Features & Use Cases - Module Structure Enforcement: Ensures each platform with an installable app (androidApp, desktopApp, iosApp) has its own entry point module, while shared stays a pure KMP library module. - Version Catalog Centralization: Mandates a single gradle/libs.versions.toml as the only source of versions, with kebab-case naming and BOM usage where available (e.g., Koin BOM). - Convention Plugin Guidance: Provides decision rules for when to introduce build-logic convention plugins—only when real duplication exists across two or more modules. - Use Case: When migrating a project to AGP 9.0, use this Skill to audit that MainActivity lives in androidApp rather than shared, and that no module declares hardcoded dependency versions outside the catalog. ## Quick Start Audit my Kotlin Multiplatform project's Gradle setup and move any hardcoded dependency versions into libs.versions.toml while separating the Android entry point into its own androidApp module.
