mavericks-mvi

Implement Mavericks MVI ViewModels with Hilt and Compose subscriptions.

3|Updated Apr 12, 2026

Search Tags:#android #state-management #compose #viewmodel #mvi #hilt #mavericks

Ready to run

npx skills add https://github.com/ujffdi/mavericks-mvi-skills --skill mavericks-mvi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mavericks-mvi
Source: https://github.com/ujffdi/mavericks-mvi-skills/tree/main/skills/mavericks-mvi
Command: npx skills add https://github.com/ujffdi/mavericks-mvi-skills --skill mavericks-mvi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mavericks MVI integration can be verbose and error-prone; this guide provides a structured approach to implementing ViewModel, State, Hilt DI registration, Compose/Fragment subscriptions, Async requests, and DeliveryMode one-shot events.

Core Features & Use Cases

Guidance for designing MavericksState and MavericksViewModel
Examples of Compose, Fragment subscriptions, and Hilt registrations
Handling Async requests, event delivery, and lifecycle

Quick Start

Create or initialize a Mavericks MVI setup in your Android project and begin wiring ViewModel, State, and events.

Frequently Asked Questions about mavericks-mvi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up Mavericks MVI with Hilt dependency injection in an Android app?▼

Mavericks MVI handles state management in Android by applying deterministic execution with execute and onEach, enforcing lifecycle-aware state updates. It manages Async data flows and DeliveryMode one-shot events to ensure UI state remains consistent and predictable.

How do I handle Async data flows and one-shot events using Mavericks MVI?▼

Mavericks MVI handles Async data flows and events by utilizing DeliveryMode for one-shot events and deterministic execution. This ensures async requests are managed lifecycle-aware, preventing state inconsistencies and event loss during configuration changes.

Can I use Mavericks MVI with Jetpack Compose for state subscriptions?▼

You should use Mavericks MVI when you need to streamline complex ViewModel creation, state management, and Hilt DI registration. It solves verbose and error-prone integration by enforcing structured guidelines for testing, error handling, and lifecycle-aware execution.

What is the best way to test Mavericks ViewModel state and one-shot events in Android?▼

The best way to test Mavericks ViewModel state is by following its structured guidelines for testing and error handling. This involves verifying deterministic execution, state transitions, and DeliveryMode one-shot event delivery to ensure lifecycle-aware reliability.