compose-recomposition-performance

What problem does it solve? Jetpack Compose UIs can recompose far more often than necessary, causing jank and wasted frames, but the root cause is rarely obvious. This Skill triages recomposition regressions by separating three distinct causes—parameter stability, where State is read, and cross-phase back-writing—so you stop applying fixes that do not reduce recomposition counts. ## Core Features & Use Cases - Three-axis diagnosis: Classifies issues into parameter stability/skipping, frame-rate State read phase (composition vs layout/draw), and back-writing snapshot state across phases. - Routing to focused skills: Directs each suspected cause to the right deep-dive skill (compose-stability-diagnostics, compose-state-deferred-reads, compose-side-effects) instead of guessing. - False-lead detection: Lists common fixes that do not reduce recomposition, such as remember-wrapping unchanged inputs or hoisting without stabilizing lambda captures. - Use Case: After a focus move in a lazy list causes every visible row to recompose, use this Skill to determine whether the cause is cross-row measurement back-writing before blaming parameter stability. ## Quick Start Ask the assistant to investigate why your Compose screen recomposes excessively during scrolling or focus changes and have it classify the cause using the three recomposition axes.