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, UseCases, Repositories, and data layer design. ## Core Features & Use Cases - Module Structure & Dependency Rules: Defines a recommended layout (app, core, domain, data, presentation, design-system) with strict dependency direction so domain stays pure Kotlin. - UseCase and Repository Patterns: Provides operator-invoke UseCases, Flow-based reactive streams, repository interfaces in domain, and implementations coordinating local and remote DataSources. - Data Layer Tooling: Includes Room entities and DAOs for Android, SQLDelight schemas and Ktor HTTP clients for KMP, plus mapper extension functions between DTOs, entities, and domain models. - Use Case: When starting a new KMP feature, apply this Skill to scaffold the domain UseCase, repository interface, Room/SQLDelight persistence, Ktor remote source, and Koin DI modules with correct layer boundaries. ## Quick Start Ask the AI to structure a new Android or Kotlin Multiplatform feature using Clean Architecture with a UseCase, Repository, Room database, and Koin dependency injection.
