What problem does it solve? Kotlin codebases accumulate inconsistent type usage, ad-hoc coroutine patterns, and layering violations when multiple contributors or agents edit code without shared conventions. This Skill enforces a consistent set of opinionated Kotlin rules and routes each concern to the correct upstream chrisbanes skill cluster. ## Core Features & Use Cases - Fail-closed routing to upstream skills: Maps concerns like Flow/StateFlow, exhaustive when, KMP boundaries, and Gradle runs to named chrisbanes skills, stopping with an install command if they are missing. - Opinionated overlays: Enforces rules such as app/UI modules never importing data-layer DTOs, LiveData-to-StateFlow migration, named boolean parameters with safe defaults, and a single JSON serialization stack. - Use Case: While refactoring an Android screen that still uses LiveData, the Skill directs the agent to load kotlin-concurrency-and-flow, migrate to StateFlow, and finish with a real Gradle assemble to verify the change. ## Quick Start Ask the agent to review or edit a Kotlin file using the kotlin-best-practices skill, for example to migrate a LiveData-based screen to StateFlow.
