android-architecture

Files (1)

• SKILL.md

SKILL.md (first lines)

# Android architecture

## Purpose

Keep UI → Presentation → Domain → Data → Infrastructure clear and testable.

## When to load

Architecture phase (with `android-kotlin` and layer skills). Implementation and code review when structure is in scope.

## Inputs

- FR and impact docs.
- Existing Gradle modules and packages.

## Outputs

- `docs/architecture.md` when the change is non-trivial.
- Stack decisions recorded only when new dependencies are justified.

## Rules

Official guides:

- [App architecture](https://developer.android.com/topic/architecture)
- [Recommendations](https://developer.android.com/topic/architecture/recommendations)
- [Data layer](https://developer.android.com/topic/architecture/data-layer)
- [UI layer](https://developer.android.com/topic/architecture/ui-layer)
- [Domain layer](https://developer.android.com/topic/architecture/domain-layer) (optional; use when logic is reused or complex)

Add Hilt, Room, Retrofit/Ktor, Serialization, WorkManager, Paging, DataStore, Navigation Compose **only when the requirement needs them**.

Multi-module example when justified: `app`, `core/*`, `feature/*` — one responsibility per module; do not inflate module count.

**Do not replace** working project architecture without integration analysis.

## Dependencies

- `android-kotlin`

## Validation

- Repositories are the data-layer entry; UI does not call data sources directly.
- ViewModels at screen level; no business logic in Composables.
- `docs/functional-requirements.md` and `docs/architecture.md` stay aligned after UX or stack changes (e.g. design system swap, settings hub split).

### Settings and theme (recurring pattern)

- **Settings hub:** one ViewModel for hub state (toggles + summary subtitles); **detail screens** each with their own ViewModel and use cases.
- **App theme:** optional `ThemeViewModel` at the root observing prefs; settings hub writes via use cases — avoid reading DataStore inside Composables.
- **Navigation:** shared one-shot handling (snackbar, open URL, post-clear navigation) in a small route wrapper; feature subgraph in `NavGraphBuilder` extensions.
- **Use cases in constructor:** inject as `private val` when methods on the ViewModel call them after `init`.

## Anti-patterns

- KMM/CMP stack unless user explicitly requests.
- Global singletons for session state instead of explicit state holders.

From Kapil-SquareNetra/android-agentic-orchestrator, MIT.

More from Kapil-SquareNetra/android-agentic-orchestrator