kotlin-android-architecture

name	kotlin-android-architecture
description	Use this skill to statically review Android app architecture correctness: ViewModel lifecycle and scoping across configuration changes, SavedStateHandle persistence across process death, lifecycle-aware Flow collection (repeatOnLifecycle/collectAsStateWithLifecycle/flowWithLifecycle), and unidirectional data flow with a single source of truth. Reads source only; it never runs or instruments the app.
allowed-tools	Read Grep Glob
metadata	{"author":"github: Raishin","version":"0.1.0","updated":"2026-07-21","category":"architecture","lifecycle":"experimental"}

kotlin-android-architecture

Purpose

This skill decides whether Android app architecture is safe to ship. An architecture is safe only when ViewModel state survives configuration changes without leaking a Context/View reference, state that must survive process death is persisted via SavedStateHandle, Flow collection tied to the UI pauses while backgrounded, and state flows down from a single source of truth while events flow up without back-channel mutation.

Trigger conditions

• A user provides ViewModel, SavedStateHandle, or Flow-collection source and asks whether it correctly survives configuration change or process death.
• A user is diagnosing lost state after rotation or backgrounding, a memory leak tied to a ViewModel, or a Flow that keeps running in the background.
• A user asks how to structure state ownership and one-shot events between a ViewModel and its UI.

When not to use

• The concern is Compose recomposition performance/stability or accessibility — route to .