android-clean-architecture

Structure Android and Kotlin Multiplatform projects with Clean Architecture modules.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Zenobia000/ai-brainstorming --skill android-clean-architecture-zenobia000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-clean-architecture
Source: https://github.com/Zenobia000/ai-brainstorming/tree/main/.claude/custom-rule%26skill/skills/android-clean-architecture
Command: npx skills add https://github.com/Zenobia000/ai-brainstorming --skill android-clean-architecture-zenobia000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common pain point of unstructured, tightly coupled Android and Kotlin Multiplatform projects that are hard to maintain, test, and scale as features grow, eliminating messy module boundaries and scattered business logic that slow down development.

Core Features & Use Cases

  • Standardized Module Layout: Provides a proven folder structure for domain, data, presentation, and core layers that enforces strict dependency rules and prevents circular dependencies.
  • Production-Ready Patterns: Includes ready-to-use templates for UseCases, Repository interfaces, data mappers, and dependency injection setup with Koin or Hilt, plus concrete examples for Room, SQLDelight, and Ktor integration.
  • Cross-Platform Consistency: Works for both native Android and Kotlin Multiplatform projects, ensuring consistent architecture across iOS and Android codebases. Use Case: A solo mobile developer building a new cross-platform app can use this Skill to set up a maintainable project structure in minutes instead of spending hours configuring module boundaries and dependency rules from scratch.

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 a Kotlin Multiplatform project to follow clean architecture dependency rules?

To structure a Kotlin Multiplatform project with clean architecture, you separate code into domain, data, and presentation modules. This enforces strict dependency rules, prevents circular dependencies, and keeps domain logic free from framework dependencies.

How do I set up dependency injection for Android clean architecture using Koin or Hilt?

Setting up dependency injection for Android clean architecture involves configuring Koin or Hilt to provide UseCases, Repository interfaces, and data sources. This standardizes module boundaries and ensures consistent data mapping between architectural layers.

Can I use clean architecture UseCase and Repository patterns for both native Android and Kotlin Multiplatform?

Yes, you can use clean architecture UseCase and Repository patterns for both native Android and Kotlin Multiplatform. This approach ensures consistent architecture, pure domain logic, and standardized error handling across iOS and Android codebases.

What is the best way to enforce dependency rules between domain and data layers in an Android app?

The best way to enforce dependency rules between domain and data layers is using a standardized module layout. This structure ensures the domain layer remains pure and independent, while the data layer integrates Room, SQLDelight, and Ktor through repository implementations.

How do I integrate Room and SQLDelight in a KMP clean architecture data layer?

To integrate Room and SQLDelight in a KMP clean architecture data layer, you implement repository interfaces in the domain layer and concrete data sources in the data layer. Data mappers translate database entities to domain models, maintaining consistent cross-platform data handling.