🔄
QualityShell

Preserving State Across Reloads

by skydoves

Preserving State Across Reloads is a Quality skill for Claude Code, published by skydoves in compose-performance-skills.

492 stars17 forkson skydoves/compose-performance-skillsAdded 2026/08/26+1% in starsRepository updated 2026/06/16
agent-skillsandroidclaudeclaude-codecomposecompose-performancejetpack-composekotlinllm-toolsrecompositionskydoves
Install in seconds
Install Preserving State Across Reloads
Copy Preserving State Across Reloads into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/skydoves/compose-performance-skills/tree/main/hot-reload/preserving-state-across-reloads ~/.claude/skills/preserving-state-across-reloads

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/skydoves/compose-performance-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
hot-reload/preserving-state-across-reloads/SKILL.md in skydoves/compose-performance-skills
Installs to
~/.claude/skills/preserving-state-across-reloads
Collection
One of 25 skills cataloged from this repository
Category
Quality1354 skills

What Preserving State Across Reloads does

Preserving State Across Reloads explains how Compose HotSwan’s three reload tiers affect scroll, dialogs, lazy items, remember values, ViewModel state, and SavedInstanceState. Use it to keep edits in tier 1 or hoist UI state when a reload escalates.

Preserving State Across Reloads is cataloged under Quality on DirSkills. Preserving State Across Reloads comes from a repository tagged agent-skills, android, claude, claude-code and compose.

Documentation

README

Preserving State Across Reloads: keep edits inside HotSwan tier 1

Compose HotSwan applies every hot reload through three escalating tiers. Tier 1 (targeted recomposition) preserves the most: scroll position, navigation back stack, remember and rememberSaveable values, ViewModel state, lazy layout items, dialog and bottom sheet state. Tier 2 (composition reset) disposes and recreates compositions, dropping per-composable remember. Tier 3 (Activity.recreate()) restarts the Activity and only state held by ViewModel or SavedInstanceState survives.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Preserving State Across Reloads

  • What else does skydoves publish alongside Preserving State Across Reloads?

    Preserving State Across Reloads is one of 25 skills that DirSkills catalogs from skydoves/compose-performance-skills, the repository it ships in. Its siblings there include Auditing Compose Performance, Avoiding Subcomposition Pitfalls and Choosing DerivedStateOf. Each one is a separate skill with its own page in this directory, installs the same way Preserving State Across Reloads does, and is maintained by skydoves in that same repository. The rest of the collection is listed on the skydoves/compose-performance-skills page.

  • How does Preserving State Across Reloads compare to other Quality skills?

    Preserving State Across Reloads ranks #1225 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Preserving State Across Reloads against them. Open each page to compare what they document and how they install.

More from skydoves/compose-performance-skills

Preserving State Across Reloads is one of 25 skills cataloged on DirSkills from skydoves/compose-performance-skills.

See all 25 skills
🔍
5d ago

Auditing Compose Performance

Auditing Compose Performance runs a Measure → Diagnose → Fix → Verify workflow for broad Jetpack Compose slowdowns. Use it for perf audits, sprint kickoffs, and written reports when you need baseline metrics, causes, fixes, and verification.
Quality
49217
🧩
5d ago

Avoiding Subcomposition Pitfalls

Avoiding Subcomposition Pitfalls explains when SubcomposeLayout, BoxWithConstraints, or Scaffold cause repeated measure-phase composition in Jetpack Compose. Use it to replace unnecessary subcomposition with cheaper layout primitives or tune it when subcomposition is required.
Frontend
49217
🧩
5d ago

Choosing DerivedStateOf

Choosing DerivedStateOf helps decide when Jetpack Compose derivedStateOf reduces recompositions and when it is just overhead. It covers input-vs-output frequency, required remember wrapping, stale captures, and snapshotFlow for one-shot side effects.
Frontend
49217
🌊
5d ago

Collecting Flows Safely

Collecting Flows Safely helps migrate Compose screens from collectAsState() to collectAsStateWithLifecycle() and tame high-frequency flows with conflate(), distinctUntilChanged(), and snapshotFlow. Use it when background collection, unstable Flow parameters, or chatty streams are causing wasted work or extra recompositions.
Quality
49217
📜
5d ago

Configuring Lazy Prefetch

Configuring Lazy Prefetch tunes Jetpack Compose lazy-layout cache windows and nested prefetch for heavy scrolling. Use it when dropped frames come from composition work, especially with LazyLayoutCacheWindow or inner lazy layouts.
Frontend
49217
🛠️
5d ago

Configuring R8 For Compose

Configuring R8 For Compose explains how to set up minification for a Jetpack Compose app with R8 full mode, resource shrinking, and minimal keep rules. Use it when enabling release shrinking, fixing missing keeps, or checking why Compose does not need blanket keep rules.
DevOps
49217