Android Clean Architecture
Clean Architecture for Android and Kotlin Multiplatform: module layout, strict dependency rules, UseCases, Repositories, and data layer patterns.
- What
- Clean Architecture for Android and Kotlin Multiplatform: module layout, strict dependency rules, UseCases, Repositories, and data layer patterns.
- Cost
- Free
- Needs
- Use "Android Clean Architecture" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: an architecture skill for structuring Android and Kotlin Multiplatform projects so they stay testable as they grow. It prescribes a module layout (app, core, domain, data, presentation, design-system, plus optional feature modules) with strict dependency rules: domain is pure Kotlin and must never depend on data, presentation, or any framework. You get the UseCase and Repository patterns with repository interfaces living in domain and implementations in data, data layer design with Room, SQLDelight, and Ktor, data flow guidance between layers, and dependency injection setup with Koin or Hilt. The domain-never-depends-on-data rule is the load-bearing wall: it keeps business logic unit-testable without Android on the classpath. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; a multi-module setup has real upfront cost, so tiny apps may find it heavy; the KMP notes assume Kotlin fluency. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Android Clean Architecture" with your Muse. Prerequisites: an Android or Kotlin Multiplatform project to structure. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/android-clean-architecture/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Audit my module structure against these dependency rules. Flag every violation, domain depending on data first." 3. For new features: "Scaffold this feature following the module layout and UseCase/Repository patterns, Koin for DI." Tip: ask for the dependency graph in text form before moving files; it catches cycles early. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets into a chat, and review anything Muse proposes before it changes your code.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.