What problem does it solve?
This Skill solves the common issue of disorganized, tightly coupled Android and Kotlin Multiplatform project codebases that become impossible to maintain, test, and scale as teams and feature sets grow, eliminating the technical debt caused by inconsistent architecture choices.
Core Features & Use Cases
- Standardized Module Layout: Provides a proven folder structure with clear separation of domain, data, presentation, and core layers to enforce dependency rules and prevent circular dependencies.
- Ready-to-Use Patterns: Includes copy-paste ready templates for UseCases, Repository interfaces, data mappers, Room/SQLDelight database setups, Ktor network clients, and Koin/Hilt dependency injection wiring.
- Cross-Platform Support: Tailored for both native Android and Kotlin Multiplatform projects, ensuring shared business logic remains pure Kotlin with no framework leakage.
- Use Case Example: A team building a cross-platform fitness tracking app can use this Skill to set up a shared domain layer with pure Kotlin UseCases, separate data layer implementations for Android and iOS, and consistent DI wiring across all modules.
Quick Start
Use the android-clean-architecture skill to set up a new Kotlin Multiplatform project with properly separated domain, data, and presentation modules following Clean Architecture dependency rules.