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

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