compose-recomposition-performance

Stars15

Forks0

UpdatedMay 15, 2026 at 17:14

Use when investigating Jetpack Compose recomposition performance, skippable/restartable composables, composables.txt or compiler reports, Layout Inspector recomposition counts, or frame-rate State reads in composition vs layout/draw, and it is not yet clear whether the cause is parameter stability or deferred reads.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

costular

costular/Minitask

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	compose-recomposition-performance
description	Use when investigating Jetpack Compose recomposition performance, skippable/restartable composables, composables.txt or compiler reports, Layout Inspector recomposition counts, or frame-rate State reads in composition vs layout/draw, and it is not yet clear whether the cause is parameter stability or deferred reads.

Compose recomposition performance

Router only — deep fixes live in compose-stability-diagnostics and compose-state-deferred-reads.

Two axes

Parameter stability / skipping — can Compose skip this restartable composable; are arguments stable and comparable?
Where State is read — is frame-rate State read during composition vs layout/draw?

Either axis can dominate; they combine independently.

Route here → focused skill

Primary suspicion	Next skill
Skipping, unstable params, compiler/`composables.txt` churn	`compose-stability-diagnostics`
Frame-rate `State` read phase (composition vs layout/draw)	`compose-state-deferred-reads`
Evidence for both	Apply both skills in parallel

Review order

Decide which axis fits the evidence; open the matching skill.
If unclear, sample both — stability churn vs composition-phase reads of fast State.
Re-measure after changes.

When NOT to apply

Recomposition tracks real data changes, or the bug is correctness not cost.
No profiler / compiler signal suggests a problem.

More from this repository

same repository

compose-modifier-and-layout-style

costular/Minitask

Use when writing or reviewing Jetpack Compose layout APIs, modifier parameters, modifier chain construction, hardcoded root layout decisions, or layout wrappers around a single conditional.

2026-05-1515

compose-side-effects

costular/Minitask

Use when writing or reviewing Jetpack Compose code with LaunchedEffect, DisposableEffect, SideEffect, rememberCoroutineScope, rememberUpdatedState, snapshotFlow, snackbar, navigation, focus requests, analytics, or event Flow collection.

2026-05-1515

compose-slot-api-pattern

costular/Minitask

Use when designing or reviewing a reusable Jetpack Compose component whose visual regions vary by caller, or when primitive content parameters and boolean shape flags are accumulating.

2026-05-1515

compose-stability-diagnostics

costular/Minitask

Use when writing or reviewing Jetpack Compose parameter stability, compiler reports, skippability, unstable UI state classes, collection parameters, or Kotlin 2.0+ strong skipping behavior.

2026-05-1515

compose-state-authoring

costular/Minitask

Use when writing or reviewing Jetpack Compose code with bare local var in a @Composable, remember { mutableStateOf(...) }, mutableStateListOf/mutableStateMapOf, or @ReadOnlyComposable.

2026-05-1515

compose-state-deferred-reads

costular/Minitask

Use when Jetpack Compose code reads scroll, animation, gesture, or other frame-rate State in composition, passes changing values across composable boundaries, or uses value-form layout/draw modifiers.

2026-05-1515

name	compose-recomposition-performance
description	Use when investigating Jetpack Compose recomposition performance, skippable/restartable composables, composables.txt or compiler reports, Layout Inspector recomposition counts, or frame-rate State reads in composition vs layout/draw, and it is not yet clear whether the cause is parameter stability or deferred reads.

Compose recomposition performance

Router only — deep fixes live in compose-stability-diagnostics and compose-state-deferred-reads.

Two axes

Parameter stability / skipping — can Compose skip this restartable composable; are arguments stable and comparable?
Where State is read — is frame-rate State read during composition vs layout/draw?

Either axis can dominate; they combine independently.

Route here → focused skill

Primary suspicion	Next skill
Skipping, unstable params, compiler/`composables.txt` churn	`compose-stability-diagnostics`
Frame-rate `State` read phase (composition vs layout/draw)	`compose-state-deferred-reads`
Evidence for both	Apply both skills in parallel

Review order

Decide which axis fits the evidence; open the matching skill.
If unclear, sample both — stability churn vs composition-phase reads of fast State.
Re-measure after changes.

When NOT to apply

Recomposition tracks real data changes, or the bug is correctness not cost.
No profiler / compiler signal suggests a problem.