What problem does it solve? Jetpack Compose code that reads frame-rate state (scroll offsets, animations, gestures) during composition triggers unnecessary recompositions, and back-writing observable state from layout or draw into composition causes cascading invalidation across sibling composables. ## Core Features & Use Cases - Deferred state reads: Converts value-form modifiers like Modifier.offset(x = ...) and graphicsLayer(translationY = ...) into block forms that read State.value inside layout or draw callbacks. - Provider lambdas across boundaries: Replaces passing fast-changing values (scroll offsets, drag positions) into child composables with provider lambdas read only in layout/draw phases. - Back-write detection and fixes: Identifies composition-time writes to mutableStateMapOf/mutableStateListOf and layout-to-composition back-writes (e.g., sibling reading onSizeChanged measurements), with fixes like remember(keys) merges and measure-phase constraint decoration. - Use Case: A LazyColumn hero image recomposes on every scroll frame because firstVisibleItemScrollOffset is read in composition; this Skill rewrites it so the offset is only read inside a graphicsLayer block, eliminating the recomposition storm. ## Quick Start Review my Compose screen for state reads happening in composition that should be deferred to layout or draw phases and fix any back-writing patterns.
