What problem does it solve? Structuring Android and Kotlin Multiplatform codebases without clear layer boundaries leads to tangled dependencies, untestable business logic, and framework leakage into domain code. This Skill provides concrete patterns for module separation, dependency rules, and data flow so teams can build maintainable, testable apps. ## Core Features & Use Cases - Module Structure & Dependency Rules: Defines a layered layout (app, core, domain, data, presentation) with strict dependency direction, keeping the domain layer pure Kotlin. - UseCase and Repository Patterns: Provides ready-to-adapt templates for UseCases with operator invoke, repository interfaces in domain, and implementations coordinating local and remote DataSources. - Data Layer Integrations: Includes working examples for Room, SQLDelight, Ktor clients, mapper extensions, and DI setup with Koin or Hilt. - Use Case: When starting a new KMP feature, apply the module layout, define a repository interface in domain, implement it in data with Room and Ktor DataSources, and wire everything with Koin modules. ## Quick Start Ask the AI to structure a new Android or KMP feature using Clean Architecture with a UseCase, Repository, and Room-backed data layer.