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 organizing modules, enforcing dependency rules, and implementing UseCases, Repositories, and DataSources. ## Core Features & Use Cases - Module Structure & Dependency Rules: Defines a recommended layout (app, core, domain, data, presentation, design-system) with strict rules ensuring the domain layer stays pure Kotlin with no framework dependencies. - UseCase and Repository Patterns: Provides templates for suspend and Flow-based UseCases using operator invoke, repository interfaces in domain, and implementations coordinating local and remote DataSources. - Data Layer Implementations: Includes working examples for Room databases, SQLDelight queries, Ktor HTTP clients, mapper extension functions, and DI setup with Koin or Hilt. - Use Case: When starting a new KMP project, apply this Skill to scaffold the module graph, write a GetItemsByCategoryUseCase, wire an ItemRepositoryImpl with Room and Ktor DataSources, and register everything in Koin modules. ## Quick Start Ask the AI to structure a new Android or Kotlin Multiplatform feature module following Clean Architecture with a UseCase, Repository, and Room data source.
