skill-android-loto-orchestrator

Structure an offline-first Android app by separating domain, data, and UI layers using clean architecture and Compose. Keep domain logic pure Kotlin, use Room for local persistence, sync with WorkManager, and apply Hilt for dependency injection to ensure scalable and testable code.

The best way to plan end-to-end feature implementation is to define the minimum scope including use cases, repository contracts, persistence strategies, UI state, and regression tests. This approach enforces clear layer contracts and offline-first data flow for robust MVVM architecture.

Dependency injection with Hilt in a clean architecture setup works by exposing clear contracts across separated domain, data, and UI boundaries. Hilt manages dependency provision to avoid main-thread blocking and centralize business rules, ensuring fast and testable offline-first performance.

Yes, you can use Room and WorkManager for offline-first data flow without blocking the main thread. Read from Room for immediate local access, sync data in the background with WorkManager, and maintain performance guardrails by keeping domain logic pure Kotlin.

You should keep domain logic pure Kotlin in an Android clean architecture project to centralize business rules and maintain testability. Pure Kotlin domain layers enforce clear separation from UI and data concerns, preventing main-thread blocking and ensuring scalable offline-first behavior.