Android Architecture Clean

When your Android codebase has tangled presentation logic, fat repositories, or ViewModels doing too much, this skill helps you draw clean boundaries between domain, data, and UI layers. It focuses on separating use cases, repositories, and lifecycle-aware presentation models without rewriting your entire app. The workflow is refreshingly pragmatic: map your current stack, inspect what's actually wrong, apply the smallest fix that matters, then validate against real example apps like OrbitTasks. The guardrails are spot on, especially keeping framework code out of domain layers and not mixing architectural cleanup with feature work. If you're wrestling with MVVM that's gotten messy or need to untangle data flows before modularizing, this gives you a structured path forward without the usual over-engineering.