What problem does it solve? Structuring Android and Kotlin Multiplatform projects 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 your codebase stays maintainable as it grows. ## 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 patterns to create a domain module with a GetItemsByCategoryUseCase, a Room-backed repository implementation, and a Koin module wiring it into a ViewModel. ## Quick Start Ask the assistant to structure a new Android or KMP feature module using Clean Architecture with a UseCase, Repository, and Room data source.
