android-clean-architecture

Structure Android and Kotlin Multiplatform projects with Clean Architecture layers.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sayasaya8039/ZWG_Terminal --skill android-clean-architecture-sayasaya8039
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-clean-architecture
Source: https://github.com/sayasaya8039/ZWG_Terminal/tree/main/.claude/skills/android-clean-architecture
Command: npx skills add https://github.com/sayasaya8039/ZWG_Terminal --skill android-clean-architecture-sayasaya8039

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common issue of disorganized, tightly coupled Android and Kotlin Multiplatform project codebases that become impossible to maintain, test, and scale as teams and feature sets grow, eliminating the technical debt caused by inconsistent architecture choices.

Core Features & Use Cases

  • Standardized Module Layout: Provides a proven folder structure with clear separation of domain, data, presentation, and core layers to enforce dependency rules and prevent circular dependencies.
  • Ready-to-Use Patterns: Includes copy-paste ready templates for UseCases, Repository interfaces, data mappers, Room/SQLDelight database setups, Ktor network clients, and Koin/Hilt dependency injection wiring.
  • Cross-Platform Support: Tailored for both native Android and Kotlin Multiplatform projects, ensuring shared business logic remains pure Kotlin with no framework leakage.
  • Use Case Example: A team building a cross-platform fitness tracking app can use this Skill to set up a shared domain layer with pure Kotlin UseCases, separate data layer implementations for Android and iOS, and consistent DI wiring across all modules.

Quick Start

Use the android-clean-architecture skill to set up a new Kotlin Multiplatform project with properly separated domain, data, and presentation modules following Clean Architecture dependency rules.

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 Kotlin Multiplatform project using clean architecture?

Structure an Android Kotlin Multiplatform project using clean architecture by separating code into domain, data, presentation, and core layers. This enforces dependency rules, prevents circular dependencies, and keeps shared business logic pure Kotlin.

What is the best way to separate pure domain logic from framework-specific code in KMP?

Separate pure domain logic from framework-specific code in KMP by standardizing repository interfaces, UseCases, and data source patterns. This enforces dependency inversion, allowing Android and iOS to share business logic without framework leakage.

Does this clean architecture approach provide templates for dependency injection and network clients?

Yes, this clean architecture approach provides ready-to-use templates for Koin or Hilt dependency injection wiring, Ktor network clients, Room or SQLDelight database setups, repository interfaces, and data mappers.

Can I use clean architecture to restructure tightly coupled Android codebases for better testability?

Yes, you can use clean architecture to restructure tightly coupled Android codebases. It eliminates unstructured code by enforcing dependency inversion and separating domain logic, making projects easier to maintain and test as they scale.

When do I need to standardize repository and UseCase patterns in mobile development?

Standardize repository and UseCase patterns in mobile development when your codebase becomes disorganized and difficult to maintain. This eliminates technical debt from inconsistent architecture choices and standardizes cross-platform data flow design.