What problem does it solve? Android and KMP projects accumulate architectural drift when new code ignores established patterns, producing inconsistent ViewModels, misplaced state, and leaky error handling. This Skill enforces a consistent senior-engineer baseline across all Android and Kotlin Multiplatform work. ## Core Features & Use Cases - Architecture Baseline: Enforces clean architecture with repository pattern, MVVM/MVI selection guidance, Hilt DI, Compose UI, and StateFlow-based state management. - Existing-Pattern Audit: Requires inspecting sibling ViewModels and feature code before adding new events, flows, or navigation mechanisms, preventing architectural inconsistency. - Layered Error Handling & State Modeling: Defines error propagation from data sources through repositories and use cases to ViewModels, plus a four-bucket UiState model separating input, derived, persisted, and transient state. - Use Case: When asked to add a new screen to an existing Android app, the Skill first audits how sibling features wire events and effects, then implements the screen using the project's established MVVM or MVI pattern with proper StateFlow and Channel/SharedFlow semantics. ## Quick Start Ask the assistant to refactor a ViewModel or build a new Compose screen in your Android or KMP project following clean architecture conventions.
