What problem does it solve?
This Skill solves the common pain point of disorganized Android and Kotlin Multiplatform project structure, inconsistent dependency rules, and scattered business logic that makes mobile apps difficult to maintain, test, and scale as codebases grow.
Core Features & Use Cases
- Modular Project Structuring: Define clear, enforceable module boundaries (domain, data, presentation, core) to separate concerns and reduce coupling.
- Clean Architecture Pattern Implementation: Set up pure Kotlin domain layers with UseCases and Repository interfaces, keeping business logic independent of Android or KMP framework dependencies.
- Cross-Platform Data Layer Setup: Configure local data sources with Room (Android) or SQLDelight (KMP), remote sources with Ktor, and implement mapper patterns for seamless data transformation between layers.
- Dependency Injection Configuration: Wire up dependencies using Koin for cross-platform projects or Hilt for Android-only projects, following Clean Architecture dependency rules.
- Use Case Example: If you are building a cross-platform fitness tracking app, use this Skill to structure your domain layer with pure Kotlin UseCases for workout logging, implement repository interfaces in the domain layer, and connect data sources with SQLDelight for local storage and Ktor for syncing with a remote API.
Quick Start
Use the android-clean-architecture skill to structure a new Kotlin Multiplatform project with separate domain, data, and presentation modules that follow strict Clean Architecture dependency rules.