compose-recomposition-performance

Original：🇺🇸 English

Translated

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.

3installs

Sourcechrisbanes/skills

Added on2026-05-12

NPX Install

npx skill4agent add chrisbanes/skills compose-recomposition-performance

SKILL.md Content

View Translation Comparison →

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.