android-dev-core

Clean architecture with MVI organizes Android features into domain, data, and presentation layers. MVI (Model-View-Intent) enforces unidirectional data flow through ViewModel and UI State, reducing coupling and making features predictable. This Skill provides templates and base classes to apply these patterns consistently across your project.

Use suspend functions and callbackFlow for coroutine-based async operations in Android. Suspend functions provide readable sequential code, while callbackFlow bridges callback-based APIs into coroutine streams. This Skill includes patterns for integrating these into your ViewModel and data layer.

ViewModel holds UI State and exposes it as an observable stream; the UI observes State changes and emits Intents back to ViewModel. This one-way cycle prevents state mutations from UI, improves testability, and eliminates race conditions. This Skill provides base ViewModel classes and State management patterns ready to use.

Yes. This Skill applies to any Android feature project implementing clean architecture. It standardizes domain, data, and presentation layers across your codebase, lowering the learning curve and reducing inconsistency whether you're building new features or refactoring existing ones.

This Skill adheres to the Android Kotlin Style Guide and API Design Guidelines, with comprehensive in-code documentation and English-to-Chinese annotations. It prioritizes native Android tools and idiomatic Kotlin, ensuring your code is maintainable and consistent with platform best practices.

Standardized base classes, Adapter patterns, and network request templates eliminate boilerplate and decision fatigue. By providing proven architecture upfront, teams skip design debates and jump directly to feature logic, accelerating delivery while maintaining robustness.