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.

skills.sh installs: 331
GitHub stars: 14
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add krutikjain/android-agent-skills --skill android-architecture-clean --agent claude-code

Installs into .claude/skills of the current project.

Files

Android Architecture Clean

When To Use

Use this skill when the request is about: clean architecture in android, split use cases and repositories, untangle presentation and data layer.
Primary outcome: Apply clean architecture boundaries, use cases, repositories, and lifecycle-aware presentation models in Android projects.
Handoff skills when the scope expands:
android-modularization
android-state-management

Workflow

Map the request to the current Android stack, module boundaries, and minimum supported API level.
Inspect the existing implementation for implicit assumptions, duplicate helpers, and outdated patterns.
Apply the smallest change that improves correctness, readability, and long-term maintainability.
Validate the result against the relevant showcase app path and repo benchmarks.
Hand off adjacent work to the next specialized skill only after the core foundation is stable.

SKILL.md on GitHub