android-domain-delivery

Lifecycle-safe state management in Jetpack Compose requires correct ViewModel StateFlow exposure and Flow collection patterns to prevent state destruction. The Skill verifies Compose state, coroutine structure, and ViewModel alignment before delivery.

Room migration without destructive fallback requires explicit schema updates and offline-first behavior planning. The Skill guides Room migrations, stale data handling, and WorkManager idempotency to ensure production-grade persistence and background work.

WorkManager jobs need idempotency, constraints, and retry strategy to ensure lifecycle-safe background execution. The Skill provides a playbook for WorkManager configuration, preventing duplicate or state-destructive jobs during Android feature delivery.

Yes, it works for existing Kotlin Android projects by enforcing scoped command verification and explicit rollback plans. The Skill ensures strict scope control and requires evidence-first output before completing feature changes.

Delivering offline-capable Android features requires combining Room persistence, WorkManager jobs, permission UX decision flows, and typed navigation contracts. The Skill coordinates these layers to maintain state and lifecycle safety across the entire feature slice.

You should use a lifecycle-safe delivery playbook when feature changes risk state destruction across UI, ViewModel, data, or background layers. The Skill enforces permission checks, accessibility semantics, and rollback planning when proof or required approvals are missing.