What problem does it solve? When a Jetpack Compose screen recomposes too often, developers struggle to answer two questions: which composables get dragged in when a root composable changes, and how many times each composable actually recomposed during a real interaction. This Skill drives the active investigation features of the skydoves/compose-stability-analyzer IntelliJ plugin to answer both. ## Core Features & Use Cases - Cascade Visualizer: Right-click inside any @Composable and run Analyze Recomposition Cascade to render a static call-graph tree (depth-capped at 10, cycle-safe) showing the blast radius of a state change, with per-node stability badges. - Live Recomposition Heatmap: Toggle Recomposition Heatmap to subscribe to adb logcat -s Recomposition:D -T 1 and render color-coded block inlays above each @TraceRecomposition-instrumented composable showing live recomposition counts. - Tool Window Tabs: Use the Explorer tab to survey a module, the Cascade tab for static analysis, and the Heatmap tab for runtime confirmation, with Clear Recomposition Data to reset counters between scenarios. - Use Case: Before refactoring a shared composable, run the cascade to see 12 downstream nodes, instrument the top suspects with @TraceRecomposition, toggle the heatmap during a scroll, and discover only 2 nodes are actually hot—fixing those instead of all 12. ## Quick Start Right-click inside a @Composable function in Android Studio and choose Analyze Recomposition Cascade to see its recomposition blast radius in the Compose Stability Analyzer tool window.
