android-kotlin-architecture

What problem does it solve?

AI coding agents frequently generate Kotlin and Jetpack Compose Android code that compiles but follows poor architectural practices, leading to race conditions from improper state updates, broken unidirectional data flow, unmaintainable module structures, and scattered business logic that is hard to test and scale.

Core Features & Use Cases

• Strict MVI/MVVM Enforcement: Mandates unidirectional data flow with immutable UiState, UiEvent, and UiEffect contracts, plus atomic ViewModel state updates via _state.update to eliminate race conditions.
• Clear Module Structure Rules: Defines standard feature and core module layouts to prevent circular dependencies and keep large codebases scalable across Android, Kotlin Multiplatform, and Compose Multiplatform projects.
• UseCase Placement Guidance: Provides explicit rules for when to extract business logic into UseCases, separating UI logic from domain logic to improve testability and reusability.
• Anti-Pattern Blocklist: Explicitly bans common harmful patterns like direct _state.value assignment, God ViewModels, and improper Flow collection, with clear fixes for each.

Quick Start

Use the android-kotlin-architecture skill to structure your new Compose feature following MVI patterns with proper ViewModel state management and module separation.