understanding-hot-reload-limits
skydoves/compose-performance-skills / hot-reload/understanding-hot-reload-limits
tells you which Kotlin changes hot-reload , which improves: avoids unnecessary full rebuilds
Details
- judge’s score
- 9/10
- place
- outside the packs
- publisher
- skydoves
- status
- new
- pinned commit
- 1b32f81 on GitHub (new tab)
- skill’s last commit
- Apr 29, 2026
- repo stars
- 516
- main type
- Android
Judgement
Precise triggering and concrete HotSwan know-how (tables, patterns, ART rules). Score reduced: sibling annexes missing, technical claims unsourced (R, data class, reordering).
reservations
- The sibling skills cited (setting-up-compose-hotswan, state, AI loop) are not provided: their consistency cannot be verified.
- Several claims (adding resources and regenerating R, data class properties on API 30, reordering in 1.2.0+) are unsourced; the external references point to a third-party web repo.
- The reasoning about resources ("R class not redefinable") and about lambdas is presented as fact without proof; to be verified against the current HotSwan version.
- Triggering
- 2/2
- Added value
- 2/2
- Precision
- 2/2
- Scope
- 2/2
- Quality
- 1/2
Alerts
no alerts
Neither the static scan nor the judge flagged a risk for this skill.
Original description
Use this skill to teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback. Root cause is Android Runtime (ART) class schema immutability; only method bodies are mutable at runtime, so any change to fields, signature…
added on Oct 19, 2026 · license Apache-2.0