What problem does it solve? Android bugs caused by lifecycle mismatches—such as crashes after rotation, blank screens after back navigation, duplicate requests after recreation, or callbacks updating destroyed views—are hard to trace. This Skill provides a structured workflow to map bugs to lifecycle transitions and identify state ownership mistakes. ## Core Features & Use Cases - Lifecycle Scenario Mapping: Classifies bugs by trigger, including configuration changes, process death, fragment replacement, and navigation back stack restore. - State Ownership Analysis: Determines whether state lives in the right place (ViewModel, SavedStateHandle, Fragment field, or repository) and flags incorrect ownership. - Async Work Inspection: Finds coroutines, Flow collectors, LiveData observers, and callbacks that outlive their lifecycle owner, with optional CodeGraph integration for tracing call sites. - Use Case: A user reports a blank screen after rotating the device during checkout. Use this Skill to trace the state owner, find a collector bound to the wrong scope, and get a fix recommendation plus regression test plan. ## Quick Start Debug why my Fragment shows a blank screen and duplicate network requests after rotating the device.