android-clean-architecture

Structure Android and Kotlin Multiplatform projects with clean architecture patterns.

Updated Jun 22, 2026

Search Tags:#clean architecture #dependency injection #android #kotlin #module structure

Ready to run

npx skills add https://github.com/hector-manny/bussbot --skill android-clean-architecture-hector-manny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-clean-architecture
Source: https://github.com/hector-manny/bussbot/tree/main/.cursor/skills/android-clean-architecture
Command: npx skills add https://github.com/hector-manny/bussbot --skill android-clean-architecture-hector-manny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires room, sqldelight, ktor, koin, hilt, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexity of structuring Android and Kotlin Multiplatform projects, providing guidelines for clean architecture and best practices.

Core Features & Use Cases

Module Structure: Defines a recommended layout and dependency rules for projects.
UseCase and Repository Patterns: Implements UseCases and Repositories for business operations and data persistence.
Data Layer: Covers the design and implementation of the data layer using Room, SQLDelight, and Ktor.
Dependency Injection: Offers instructions for setting up Koin and Hilt for DI in different modules.
Error Handling: Provides guidelines for implementing robust error handling with Result and Try patterns.

Quick Start

Apply the android-clean-architecture skill to your new project to establish a clean architecture foundation.

Frequently Asked Questions about android-clean-architecture

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

FAQPage Schema

What is clean architecture for Android and Kotlin Multiplatform projects?▼

Clean architecture for Android and Kotlin Multiplatform projects separates code into structured layers with strict dependency rules, defining module layouts, UseCases, and Repositories to isolate business logic from data persistence and UI frameworks.

How do I structure Android modules using clean architecture?▼

To structure Android modules using clean architecture, apply a recommended layout that enforces dependency rules across layers, separating UseCases for business operations from the data layer handling network requests and database persistence.

Does this clean architecture approach work with both Koin and Hilt for dependency injection?▼

Yes, this clean architecture approach works with both Koin and Hilt for dependency injection, offering specific setup instructions and patterns to inject dependencies across different modules in Android and Kotlin Multiplatform apps.

Can I use Room and SQLDelight in the same Kotlin Multiplatform data layer?▼

Yes, you can use Room and SQLDelight in the same Kotlin Multiplatform data layer. The architecture guidelines cover designing and implementing data persistence operations using both database frameworks alongside Ktor for network operations.

What is the best way to handle errors in Android clean architecture?▼

The best way to handle errors in Android clean architecture is by implementing Result and Try patterns. These provide robust error handling mechanisms to manage failures across UseCases, Repositories, and data layer operations.

When do I need UseCases and Repositories in Android module structure?▼

You need UseCases and Repositories in your Android module structure when isolating business operations and data persistence. UseCases handle specific business logic, while Repositories manage data access from Room, SQLDelight, or Ktor network sources.