android-patterns

Clean Architecture with MVI organizes code into Domain, Data, and Presentation layers with unidirectional data flow: state represents UI, events capture user actions, and effects trigger side effects. This Skill provides ViewModel, UseCase, and Repository templates to enforce dependency rules and consistent contracts across your Kotlin and Compose projects.

Coroutines and Flow patterns manage background work and state updates in Compose without blocking the UI thread. This Skill covers Flow usage for reactive updates, coroutine scope management in ViewModels, and patterns to safely collect state for recomposition optimization.

Mapper patterns convert Data Transfer Objects from API responses into domain model objects, maintaining type safety and decoupling layers. This Skill provides mapper templates and contracts that standardize these transformations across your feature modules.

Yes. This Skill provides standardized patterns specifically for Kotlin 2.0 and Jetpack Compose projects, including Compose-specific state handling, recomposition optimization, and coroutine integration with modern Kotlin language features.

Inconsistent patterns emerge when teams lack shared contracts and templates for layers, ViewModels, and dependencies. This Skill resolves that by providing ready-to-use architecture guidance, dependency rules, and code review standards for MVI and Clean Architecture.

Presentation depends on Domain; Domain depends on Data; Data never depends upward. This unidirectional flow prevents circular dependencies and keeps business logic testable. This Skill enforces these rules through contract structures and template examples.