compose-performance ยท diff
git:20260826.8321e57 to git:20260827.0a83a94
3 added, 1 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
name: compose-performance
description: Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.
---
# Compose performance
## Core principle
Measure one user-visible transition, identify the runtime axis that causes the
work, then apply the smallest correction at the phase or boundary where that
axis begins.
## Procedure
1. Reproduce one concrete transition and capture the observable evidence:
recomposition counts, compiler reports, profiler data, or a clear trace.
2. Classify the primary axis: parameter stability and skipping, State read
phase, or snapshot state written back into an earlier phase.
3. Check for a false lead: a real data change, a correctness defect, or an
unchanged lazy item that is expected to recompose.
4. Read the corresponding focused reference before proposing a change.
5. For review work, pair every finding with the smallest evidence-supported
repair. For a false stability promise, explicitly say to replace mutable
non-snapshot properties with immutable data or snapshot-observable state,
verify that contract, and only then decide whether an annotation remains
needed. For a phase problem, name the layout or draw consumer where the
- changing read or calculation should move. Do not stop at diagnosis.
+ changing read or calculation should move. A cross-phase write proves
+ invalidation or an extra pass; do not claim oscillation or an infinite loop
+ unless evidence shows values repeatedly changing. Do not stop at diagnosis.
6. Change one axis at a time and re-measure the same transition.
7. Finish when the evidence improves at the observed boundary without hiding
state changes, caching stale values, or moving work to a less correct owner.
## Topic router
| Signal | Read |
|---|---|
| Cause is unknown, or several axes may interact | [Diagnosis](references/diagnosis.md) |
| `classes.txt`, `composables.txt`, strong skipping, unstable parameters, or collection stability | [Stability](references/stability.md) |
| Scroll, animation, gesture, layout, or draw State read at frame rate; measured state fed back into composition | [Deferred reads](references/deferred-reads.md) |
| A composable only reads composition locals or accessor-style values | [Composition contracts](references/composition-contracts.md) |
| State ownership or effect lifecycle is the root cause | [Compose state and effects](../compose-state-and-effects/SKILL.md) |