android-clean-architecture

Organize Android and Kotlin Multiplatform apps into domain, data, and presentation layers.

3|2|Updated Mar 8, 2026

Search Tags:#architecture #android #kotlin #clean-architecture #dependency-injection #multiplatform #domain-models

Ready to run

npx skills add https://github.com/agentmatters/mullai-bot --skill android-clean-architecture-agentmatters

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-clean-architecture
Source: https://github.com/agentmatters/mullai-bot/tree/main/src/Mullai.Skills/Skills/claude-code-everything/android-clean-architecture
Command: npx skills add https://github.com/agentmatters/mullai-bot --skill android-clean-architecture-agentmatters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android development often suffers from tangled codebases as apps grow, making maintenance and testing hard. This skill provides a structured blueprint for organizing Android and Kotlin Multiplatform apps using Clean Architecture, separating concerns into distinct layers and enforcing boundaries.

Core Features & Use Cases

Clear module boundaries: domain, data, and presentation layers with explicit dependencies.
Use case driven design: UseCase-based business logic in domain layer and repositories in data layer.
DI-friendly and testable: facilitate dependency injection with Hilt or Koin and enable isolated unit tests.

Quick Start

Create a new Android project organized into domain, data, and presentation layers and wire dependencies with DI.

Frequently Asked Questions about android-clean-architecture

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

FAQPage Schema

How do I structure an Android app with clean architecture?▼

Structure an Android app with clean architecture by dividing it into domain, data, and presentation layers with explicit dependencies. This blueprint enforces pure domain logic, use case driven design, and repository patterns to ensure your codebase remains testable and maintainable.

Does clean architecture work with Kotlin Multiplatform projects?▼

Yes, clean architecture works with Kotlin Multiplatform projects by providing a blueprint for module structure and data-layer patterns across KMP. It enforces pure domain logic and dependency rules that scale effectively across both Android and KMP environments.

How do I configure dependency injection for Android clean architecture?▼

Configure dependency injection for Android clean architecture by wiring module boundaries with frameworks like Hilt or Koin. This DI-friendly setup facilitates isolated unit tests and enforces explicit dependencies between the domain, data, and presentation layers.

When do I need clean architecture for my Android app?▼

You need clean architecture for your Android app when your codebase becomes tangled and difficult to maintain or test as it grows. It separates concerns into distinct layers, enforcing boundaries that solve maintenance and scalability problems.

What is the best way to organize domain logic in Kotlin?▼

The best way to organize domain logic in Kotlin is using a use case driven design within a dedicated domain layer. This approach enforces pure domain logic, keeping business rules isolated from data and presentation layers for maximum testability.

Why use repository patterns in Android data layers?▼

Use repository patterns in Android data layers to enforce layered data flows and separate data sources from domain logic. This structure ensures your repositories handle data operations while keeping the domain layer pure and easily testable.