android-clean-architecture

Enforce Clean Architecture in Android and Kotlin Multiplatform projects.

Updated May 9, 2026
One-click install
npx skills add https://github.com/RambleRainbow/jd --skill android-clean-architecture-ramblerainbow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-clean-architecture
Source: https://github.com/RambleRainbow/jd/tree/main/.claude/skills/android-clean-architecture
Command: npx skills add https://github.com/RambleRainbow/jd --skill android-clean-architecture-ramblerainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common pain point of disorganized Android and Kotlin Multiplatform project structure, inconsistent dependency rules, and scattered business logic that makes mobile apps difficult to maintain, test, and scale as codebases grow.

Core Features & Use Cases

  • Modular Project Structuring: Define clear, enforceable module boundaries (domain, data, presentation, core) to separate concerns and reduce coupling.
  • Clean Architecture Pattern Implementation: Set up pure Kotlin domain layers with UseCases and Repository interfaces, keeping business logic independent of Android or KMP framework dependencies.
  • Cross-Platform Data Layer Setup: Configure local data sources with Room (Android) or SQLDelight (KMP), remote sources with Ktor, and implement mapper patterns for seamless data transformation between layers.
  • Dependency Injection Configuration: Wire up dependencies using Koin for cross-platform projects or Hilt for Android-only projects, following Clean Architecture dependency rules.
  • Use Case Example: If you are building a cross-platform fitness tracking app, use this Skill to structure your domain layer with pure Kotlin UseCases for workout logging, implement repository interfaces in the domain layer, and connect data sources with SQLDelight for local storage and Ktor for syncing with a remote API.

Quick Start

Use the android-clean-architecture skill to structure a new Kotlin Multiplatform project with separate domain, data, and presentation modules that follow strict 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 with Clean Architecture?

To structure a Kotlin Multiplatform project with Clean Architecture, you separate code into domain, data, and presentation modules. This enforces strict dependency rules, keeping your pure Kotlin domain layer independent of framework dependencies.

What is the best way to implement Repository and UseCase patterns in Android?

The best way to implement Repository and UseCase patterns in Android is by defining pure Kotlin UseCases and Repository interfaces in the domain layer. This keeps business logic independent of Android framework dependencies and ensures strict dependency inversion.

Does Clean Architecture work with Koin for dependency injection in KMP projects?

Yes, Clean Architecture works with Koin for dependency injection in KMP projects. You can wire up dependencies using Koin for cross-platform projects or Hilt for Android-only projects, following strict Clean Architecture dependency rules.

How do I set up a data layer with Room and Ktor in an Android Clean Architecture project?

To set up a data layer in an Android Clean Architecture project, configure local data sources with Room and remote sources with Ktor. Implement mapper patterns for seamless data transformation between your data and domain layers.

When should I use SQLDelight instead of Room in a Kotlin Multiplatform architecture?

You should use SQLDelight instead of Room in a Kotlin Multiplatform architecture when you need cross-platform local data source configuration. SQLDelight supports KMP shared modules, whereas Room is primarily targeted for Android-only local storage.