Skip to content
Development
Skill

/android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow

From plugin
agent-skills-standard
538200 skills1 MCP
Install
$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill android-architecture --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/android-architecture

Context preview

The summary Claude sees to decide when to auto-load this skill.

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow

SKILL.md

android-architecture.SKILL.md
name: android-architecture
description: Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.
metadata:
  triggers:
    files:
      - "build.gradle.kts"
      - "settings.gradle.kts"
    keywords:
      - clean-architecture
      - module
      - layers
      - domain
      - UDF
      - unidirectional
      - feature module
      - core module
      - presentation layer
      - data layer

Android Architecture Standards

**Priority: P0 (CRITICAL)**

1. Layer Your Project (Clean Architecture)

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

See [structure & examples](references/implementation.md) for Clean Architecture layer examples.

2. Modularize by Feature and Core

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

See [structure & examples](references/implementation.md) for module configuration.

3. Enforce Unidirectional Data Flow (UDF)

  • **Events**: UI -> ViewModel (user actions flow UP).
  • **State**: ViewModel -> UI (`StateFlow<UiState>` flows DOWN).

4. Verify Jetpack Compose Integration

  • **Hosting**: Use `setContent` in Activity (No XML Layouts).
  • **State**: Hoist state to ViewModel using `collectAsStateWithLifecycle`.
  • **Recomposition**: Ensure Composable parameters `@Stable` or `@Immutable`.
  • **Navigation**: Use Compose Navigation with 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.

Verification

  • [ ] Domain layer has zero Android framework imports.
  • [ ] Each feature module compiles independently.
  • [ ] State flows one-way: Events UP, State DOWN.
  • [ ] `./gradlew build` succeeds.

References

  • [Structure & Examples](references/implementation.md)
  • [Jetpack Compose Best Practices](references/compose-standards.md)
Read more
Ships withagent-skills-standard

The portable SDLC standards layer for AI coding agents. Sync once, then work in your own runtime.

Get the whole plugin

Other skills on agent-skills-standard.