android-clean-architecture

Files (1)

• SKILL.md

SKILL.md (first lines)

# Android Clean Architecture

This is not a standalone Clean Architecture guide. Load [`clean-architecture-core`](../clean-architecture-core/SKILL.md) first; this skill adds Android/Kotlin module, package, DI, and platform-boundary details only.

## Quick start

1. Apply the layer, dependency-direction, and review rules from `clean-architecture-core`.
2. Use this adapter only to translate those rules into Android Gradle modules, Kotlin packages, Hilt bindings, Retrofit/OkHttp boundaries, and Android platform adapters.
3. If the task is only ViewModel, UiState, Compose screen wiring, or one-shot presentation effects, pair with `android-clean-presentation-architecture` before applying presentation details.

## Module Boundaries

Discover the project's Gradle modules, Kotlin source sets, dependency declarations,
and active architecture role mappings. Preserve an adopted layout; roles do not
require a new module or a fixed folder tree. Kotlin `internal` is a compilation
module boundary, not package-private visibility.

Map source sets as well as module ownership. Repeated package names do not prove
the dependency direction, and a role outside lint activation has not been checked.

## Roles

- `app-shell` owns Android Application/activity entry and Hilt composition.
- If the project has a shared database role, data adapters may depend on it.
  Database code does not depend on data implementations, features, or AppShell;
  pure domain policy does not depend on the database. Otherwise keep persistence
  inside the existing data adapter boundary.
- Network/platform roles own Android client qualifiers and native capabilities.

Apply the required core's **Semantic Layers** for all other role ownership.

## Hilt DI

- Use `@HiltAndroidApp` on the `Application`.
- Use `@AndroidEntryPoint` on activity/fragment hosts.
- Use `@HiltViewModel` for ViewModels.
- Put `@Provides` for third-party builders/factory logic.
- Put `@Binds` for interface-to-implementation mappings.
- Keep Retrofit/OkHttp construction at the network adapter/composition edge.
- Keep API providers and repository bindings at the data adapter/composition edge.
- An adopted application use-case `@Inject constructor` needs no redundant Hilt
  module. This is application wiring metadata, not permission for Hilt or Android
  types inside pure domain policy. Use external factories for a fully pure action.
- Assisted ViewModel factories pass only route values; other dependencies stay
  normal Hilt injections.

## Data Boundary

Keep Retrofit interfaces and their outbound DTOs in the owning data/network
adapter. Discover the existing binding locations rather than moving files to
match an example layout. Apply the required core's **Repository And Source
Boundary** and **Mapping Boundary**, including their recorded exceptions.

## Presentation Boundary

For ViewModel, UI state, route wiring, or Compose rendering, load
`android-clean-presentation-architecture` through the core's **Required
Application** rule. That skill owns Android state/lifecycle/stateless-rendering
rules; this adapter does not select presentation work for a data-only change.

## Review Additions

```text
android-clean-architecture: applied
gradle-module-boundary: pass|fail
kotlin-package-boundary: pass|fail
hilt-composition-root: pass|fail
repository-impl-direct-api-service: pass|fail
remote-data-source-boundary: pass|fail
feature-api-public-contract-only: pass|fail
viewmodel-dependency-boundary: usecase|single-context-repository|mixed|no-domain-dependency|fail|n/a
compose-route-screen-split: pass|fail|n/a
```

`viewmodel-dependency-boundary` records which allowed shape the ViewModel used:
`usecase` for use cases only, `single-context-repository` for a direct repository
interface from one context, `mixed` when both appear, `no-domain-dependency` when
the ViewModel injects only platform/UI abstractions, `fail` for a repository
implementation, data source, or API service, and `n/a` when no ViewModel changed.

## Evidence Basis

Hilt Android docs, Android ViewModel docs, Android UI layer docs, Compose state
docs, StateFlow and SharedFlow docs.

From chonamdoo/agent-flow, MIT.

More from chonamdoo/agent-flow