Android MVI

Use this skill to implement an opinionated MVI-style screen architecture on top of Google's Android UI layer, ViewModel, Compose state, and unidirectional data flow guidance.

The core rule: Compose renders state and sends user intents. ViewModel/state holder owns screen logic, transforms data into UI state, and emits one-off effects when needed.

Load Only What The Task Needs

• First-time screen setup or choosing file structure: read references/setup.md.
• Refactoring logic out of Compose into ViewModel: read references/refactor-compose-logic.md.
• Designing State, primitives, loading/error/empty states, or mapping domain models: read references/state-contract.md.
• Handling user actions, navigation requests, snackbars, dialogs, and one-off work: read references/intents-and-effects.md.
• Reviewing or testing a screen/ViewModel: read references/testing-and-review.md.
• Fixing common MVI bugs: read references/troubleshooting.md.

Primary official docs: