android-domain-delivery
CommunityDeliver lifecycle-safe Android feature changes.
System Documentation
What problem does it solve?
Android feature work often turns into risky, state-destructive changes because lifecycle, permissions, persistence, navigation, and verification are handled inconsistently across the UI, ViewModel, data, and background layers.
Core Features & Use Cases
- Lifecycle-safe implementation playbook: Ensures Compose state, ViewModel StateFlow, coroutine structure, and Flow collection patterns are correct before claiming completion.
- Production-grade persistence and background work: Guides Room migrations (no destructive fallbacks), offline/stale behavior, and WorkManager idempotency, constraints, and retry strategy.
- Permission, navigation, accessibility, and tests: Provides a decision flow for runtime permission UX, typed navigation contracts, TalkBack/semantics requirements, and scoped verification.
Quick Start
Ask for delivery in the smallest owned Android slice by saying: use android-domain-delivery to implement an offline-capable feature in my existing Kotlin + Jetpack Compose Android project, including ViewModel state, Room/WorkManager behavior, permission UX if needed, navigation/back-stack considerations, accessibility checks, and the exact scoped verification command plus a rollback plan.
Dependency Matrix
Required Modules
None requiredComponents
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: android-domain-delivery Download link: https://github.com/vTRKA/supervibe/archive/main.zip#android-domain-delivery Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.