Claude
5177168583
Adds technique-oriented Compose and Kotlin skills from chrisbanes/skills to complement the existing codebase-oriented skills. Codebase skills cover "where is X in Amethyst"; these cover "what is the correct Compose/Kotlin design". Descriptions tagged as technique-layer and cross-links trimmed to the vendored subset. CLAUDE.md skill table updated with a dedicated section. https://claude.ai/code/session_01QE8CjoJXUt7RKtwGgzeMrb
1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| compose-recomposition-performance | 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. Technique-layer skill — complements the codebase-specific compose-expert. |
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
Stateis read — is frame-rateStateread 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.