Android architecture

Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/android-architecture

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install

npx -y skills add ComeOnOliver/skillshub --skill android-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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)

SKILL.md

1.8 KB, 337 tokens by cl100k_base, as published. Nobody here has run it

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<UiState>).

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.