How do I install the Android Architecture skill?

Run npx skillmds@latest add comeonoliver/android-architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Android Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Android Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Android Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Android Architecture?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Android Architecture by comeonoliver

Name: Android Architecture
Rating: 4.666666666666667 (3 reviews)
Author: ComeOnOliver

Android Architecture

Standards for Clean Architecture, Modularization, and Unidirectional Data Flow. Use when anyone sets up Android project structure, asks where code belongs in Clean Architecture layers, discusses modularization (feature/core modules), or questions UDF (events up, state down). (triggers: build.gradle.kts, settings.gradle.kts, clean-architecture, module, layers, domain, UDF, unidirectional, feature module, core module, presentation layer, data layer)

ComeOnOliver Updated Sep 8, 2026 61 repo stars

File contents

Android Architecture Standards

Priority: P0 (CRITICAL)

Implementation Guidelines

Layering (Clean Architecture)

Domain: Pure Kotlin (No Android deps). Contains UseCases/Models.
Data: Repository impl, DataSources (API/DB). Maps DTO -> Domain.
UI: ViewModel + Composable. Maps Domain -> UiState.

Modularization

Feature Modules: :feature:home, :feature:profile.
Core Modules: :core:ui (Design System), :core:network, :core:database.
App Module: DI Root and Navigation Guard.

Unidirectional Data Flow (UDF)

Events: UI -> ViewModel (Events).
State: ViewModel -> UI (StateFlow).

Jetpack Compose

Hosting: Are you using setContent in Activity? (No XML Layouts)
State: Is state hoisted to ViewModel using collectAsStateWithLifecycle?
Unidirectional: Are events passed UP and state passed DOWN?
Recomposition: Are Composables stable? (Check for unstable types in parameters)
Navigation: Is Compose Navigation using Type-Safe destinations?

Anti-Patterns

No Logic in Activity: Host Navigation only.
No Repo in UI: Access data exclusively via ViewModel.
No Context in Domain: Keep Logic Pure.

References

Structure & Examples
Jetpack Compose Best Practices

Frequently asked questions