Agent skill

Understanding Hot Reload Limits

by rosuH in rosuH/EasyWatermark

A skill your agent uses to teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback.

Apache-2.0Auto-check passedMobile

Install Understanding Hot Reload Limits

skills CLI
$ npx skills add rosuH/EasyWatermark --skill understanding-hot-reload-limits -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rosuH/EasyWatermark understanding-hot-reload-limits --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rosuH/EasyWatermark.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/understanding-hot-reload-limits .claude/skills/understanding-hot-reload-limits && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
understanding-hot-reload-limits
GitHub stars
1.9k
Used in
1 other repo
Token cost
~2.6k tokens
SKILL.md length
885 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses to teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback.

  • Works in 5 steps: Watch the HotSwan tool window status at… → Read the change diff. Decide: is this a… → If a refactor must change a signature,… → …
  • Teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback
  • SKILL.md covers When to use this skill, When NOT to use this skill, Prerequisites and Boundary tables, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Understanding Hot Reload Limits is an agent skill from rosuH/EasyWatermark. 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, signatures, constructors, interfaces, inline functions, or new resource ids forces a rebuild. Covers the supported-changes table, the rebuild-forcing list, the diff-then-batch workflow that keeps a hot-reload session inside the…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Android development, Root cause analysis and Refactoring. It works with Kotlin and Android. The repository describes itself as: 🔒 🖼 Securely, easily add a watermark to your sensitive photos. 安全、简单地为你的敏感照片添加水印,防止被人泄露、利用. The licence is Apache-2.0.

When your agent uses it

  • Teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback
  • The user asks why did this rebuild?
  • Why isnt this hot reloading?
  • Wants to learn HotSwans boundaries before adopting it

Example prompts

  • “why did this rebuild?”
  • “why isn”
  • “, wants to learn HotSwan”
  • “/understanding-hot-reload-limits”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Watch the HotSwan tool window status at the moment of save. A schema change surfaces as a "falling back to incremental build" status. That…
  2. Read the change diff. Decide: is this a body-only change, or a schema change (signature, constructor, interface, field, new resource id…
  3. If a refactor must change a signature, batch it. First make the body-only changes that get the screen to a working visual state and…
  4. For inline functions, drop inline for the duration of iteration. Refactor the function out of inline while iterating, hot-reload as…
  5. For new resource ids, batch all id additions first, accept one rebuild, then iterate on values. Editing Updated Title (existing id)…

What it can do on your machine

Read from SKILL.md and the folder at commit 61223db. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are kotlin and xml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • source.android.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Understanding Hot Reload Limits loads about 2.6k tokens when it runs. Until then it costs about 212 tokens; SKILL.md has 885 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~212
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rosuH/EasyWatermark at commit 61223db, republished under its Apache-2.0 licence (© rosuH). 885 words, ~2,640 tokens.

Download SKILL.mdSave it as .claude/skills/understanding-hot-reload-limits/SKILL.md (or your agent's skills folder).
name
understanding-hot-reload-limits
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, signatures, constructors, interfaces, inline functions, or new resource ids forces a rebuild. Covers the supported-changes table, the rebuild-forcing list, the diff-then-batch workflow that keeps a hot-reload session inside the fast path, and the inline-function and new-resource-id pitfalls. Trigger when the user asks "why did this rebuild?", "why isn't this hot reloading?", wants to learn HotSwan's boundaries before adopting it, or when reviewing a refactor that risks pushing a hot-reload session into a full rebuild.
license
Apache-2.0. See LICENSE for complete terms.
metadata.author
Jaewoong Eum (skydoves)
metadata.keywords
jetpack-compose, performance, hot-reload, hotswan, art, class-redefinition, iteration, developer-experience

Understanding Hot Reload Limits: stay inside the fast path

Android Runtime (ART) enforces strict rules for class redefinition: a redefined class must have an identical schema (fields, method signatures, interfaces) as the previous version. Only method bodies are mutable at runtime. HotSwan automatically detects schema changes and falls back to a full incremental build, so failures are not silent. Knowing the boundary in advance is what keeps an iteration loop sub-second instead of multi-second.

When to use this skill

  • The developer asks "why did this trigger a full rebuild?", "why isn't this hot reloading?", or "what does HotSwan support?".
  • A PR review surfaces a refactor (parameter change, constructor change, interface extraction, new resource id) that would push a hot-reload session into a rebuild.
  • The developer is planning a session and wants to order edits so the slow ones happen at the end.
  • The developer reports an inline fun change that "didn't reload" and is debugging.

When NOT to use this skill

  • Setup or first-run troubleshooting. See ../setting-up-compose-hotswan/SKILL.md.
  • Pure state-preservation question (the reload happened but state was lost). See the state-preservation sibling skill.
  • Configuration of the AI iteration loop or MCP server. See the AI-loop sibling skill.

Prerequisites

  • HotSwan installed and verified per ../setting-up-compose-hotswan/SKILL.md (tool window status WATCHING, body-only edit reloads in under one second).
  • Familiarity with the Kotlin compiler's distinction between method-body changes and class-schema changes.

Boundary tables

Hot-reloadable (no rebuild)
ChangeNotes
Composable function bodytext, colors, modifiers, layout, control flow inside the function
Non-composable function bodyViewModel methods, mappers, utilities, repositories
Adding a new composablesame file or new file
Reordering composablesHotSwan 1.2.0+
Resource value changesstrings.xml value, colors.xml value, dimens.xml value
Extension functionsincluding suspend, including vararg
Adding data class propertiesAPI 30+ only
Numeric, string, float literal patchescompiled separately for fastest reload
Forces full rebuild (fallback)
ChangeReason
Adding or removing function parametersmethod signature changes
Constructor changesparameter list, default values, init blocks affecting fields
Interface or superclass changesclass hierarchy is part of the schema
Adding new resource idsnew R.string, R.drawable, R.id entries require generated R class regeneration
Inline functionsexpanded at every call site; no discrete unit to swap
Lambda count change inside a functioninternal lambda class renumbering
Removing a previously defined functionmethod table shrinks; schema changes
Adding data class properties below API 30constructor schema change without ART support

Workflow when a change does not hot-reload

  1. Watch the HotSwan tool window status at the moment of save. A schema change surfaces as a "falling back to incremental build" status. That is the explicit signal, not a silent failure.
  2. Read the change diff. Decide: is this a body-only change, or a schema change (signature, constructor, interface, field, new resource id, inline body, lambda count)?
  3. If a refactor must change a signature, batch it. First make the body-only changes that get the screen to a working visual state and hot-reload them. Then, in a separate save, change the signature and accept the rebuild as the last step of the session.
  4. For inline functions, drop inline for the duration of iteration. Refactor the function out of inline while iterating, hot-reload as needed, and restore inline before commit. If iteration is rare or the perf characteristic must be preserved, accept the rebuild.
  5. For new resource ids, batch all id additions first, accept one rebuild, then iterate on values. Editing <string name="title">Updated Title</string> (existing id) hot-reloads; adding <string name="brand_new_id">...</string> does not.
Show full SKILL.md (311 more words)Show less

Patterns

Pattern: function-body change (fast path) vs signature change (rebuild)
kotlin
// RIGHT (body-only change, hot-reloads)
@Composable
fun Greeting() {
    Text("Hello, World", color = Color.Blue)
}
kotlin
// WRONG for the fast path (signature change, forces rebuild)
@Composable
fun Greeting(name: String) {
    Text("Hello, $name")
}
// WRONG because: adding a parameter changes the method signature, which violates ART's class
// schema constraint. To stay inside the fast path, introduce the parameter with a default value
// in one save (still a rebuild; accept it once), then iterate on the body across subsequent saves.
Pattern: adding a new composable (fast path) vs changing a constructor (rebuild)
kotlin
// RIGHT (new composable in the same file, hot-reloads on HotSwan 1.2.0+)
@Composable
fun SecondaryAction() {
    Text("New")
}
kotlin
// WRONG for the fast path (constructor change)
data class User(val id: Long, val name: String, val age: Int)
// WRONG because: adding `age` extends the constructor. On API 30+ HotSwan supports adding
// data class properties; below API 30 the schema change forces a rebuild. When targeting older
// minSdk, batch property additions and accept a rebuild for each.
Pattern: inline function body change (rebuild)
kotlin
// WRONG for the fast path
inline fun <T> Modifier.observer(value: T, body: (T) -> Modifier): Modifier = body(value)
// WRONG because: inline functions are expanded at every call site at compile time. There is no
// discrete unit to swap, so editing the inline body forces a full rebuild of every call site.
// Drop `inline` for the duration of iteration, or accept the rebuild.
kotlin
// RIGHT for the fast path (non-inline variant during iteration)
fun <T> Modifier.observer(value: T, body: (T) -> Modifier): Modifier = body(value)
Pattern: resource value change (fast path) vs new resource id (rebuild)
xml
<!-- RIGHT: value change on an existing id, hot-reloads -->
<string name="title">Updated Title</string>
xml
<!-- WRONG for the fast path: new id, forces rebuild -->
<string name="brand_new_id">Hello</string>
<!-- WRONG because: adding a new string id grows the generated R class. R class regeneration
     is a schema change that ART cannot redefine in place. -->
Pattern: lambda count change (rebuild)
kotlin
// RIGHT (body change inside the existing lambda, hot-reloads)
@Composable
fun Row() {
    Button(onClick = { log("tapped") }) { Text("Tap") }
}
kotlin
// WRONG for the fast path (adds a second lambda, renumbers inner lambda classes)
@Composable
fun Row() {
    Button(onClick = { log("tapped") }) { Text("Tap") }
    Button(onClick = { log("second") }) { Text("Second") }
}
// WRONG because: a Kotlin function's compiled lambdas are anonymous classes named like
// Row$lambda$1, Row$lambda$2. Adding a lambda renumbers them and changes the class table,
// which is a schema change. The fix is to add the second composable as a separate top-level
// function (which is supported), then call it from Row once the structural change has rebuilt.

Mandatory rules

  • MUST consult the boundary tables before suggesting a change to a composable that the developer is iterating on. Suggesting a parameter add when the developer wanted speed wastes the iteration loop.
  • MUST NOT claim a change will hot-reload without checking it against the supported-changes table above.
  • MUST NOT disable HotSwan to "force a clean rebuild". Use Gradle's :app:clean for a clean build; HotSwan auto-falls-back when needed and turning it off costs the next round-trip.
  • MUST treat new resource ids and inline-function body changes as rebuild-forcing on every Android API level. The data-class-property exception is API 30+ only.
  • PREFERRED: order an iteration session so body-only edits come first and signature, constructor, interface, or new-resource-id changes are batched at the end.
  • PREFERRED: when a refactor needs a parameter add, introduce it once with a default value (accept the rebuild), then iterate on the body across subsequent saves.

Verification

  • A body-only change to a composable hot-reloads on save with the tool window status remaining WATCHING.
  • Adding a parameter to a composable triggers the fallback status in the tool window.
  • Adding a new <string> resource triggers the fallback; editing an existing <string> value does not.
  • Editing the body of an inline function triggers the fallback; converting it to a non-inline function and editing the body hot-reloads.
  • Adding a property to a data class hot-reloads on a device running API 30+; on API 29 and below it triggers the fallback.

References

© rosuH, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/understanding-hot-reload-limits of rosuH/EasyWatermark.

Open the folder on GitHubat commit 61223db

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in rosuH/EasyWatermark, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Understanding Hot Reload Limits next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Understanding Hot Reload Limits compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Understanding Hot Reload Limits this skillrosuH/EasyWatermark1.9k1 repos~2.6kAutomated safety check: PassApache-2.0
Architecture Overclocknekomangaorg/Neko2.8k—~1.4kAutomated safety check: PassApache-2.0
Architecture Renovatornekomangaorg/Neko2.8k—~1.2kAutomated safety check: PassApache-2.0
Android Gradle Build Logicrcosteira79/android-skills153—~959Automated safety check: PassMIT
Android Maps Ktxgooglemaps/android-maps-ktx360—~897Automated safety check: PassApache-2.0
Task Workflowikarenkov/Modo343—~2.4kAutomated safety check: PassNone

Similar skills

  • Architecture Overclock

    nekomangaorg/Neko

    Resolves deep, structural performance bottlenecks in the Kotlin Android codebase.

    2.8k GitHub stars~1.4k tokensUpdated yesterday
    MobileAuto-check passed
  • Architecture Renovator

    nekomangaorg/Neko

    Resolves deep architectural debt in the Kotlin Android codebase through macro-level refactoring.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    MobileAuto-check passed
  • Android Gradle Build Logic

    rcosteira79/android-skills

    Sets up Android Gradle convention plugins in a build-logic composite build, including the version catalog wiring and shared configuration that are easy to get wrong.

    153 GitHub stars~959 tokensUpdated 21 days ago
    MobileAuto-check passed
  • Android Maps Ktx

    googlemaps/android-maps-ktx

    Provides idiomatic Kotlin extension (KTX) patterns, reactive Flow event streams, and multi-subscriber shareIn rules for Google Maps SDK for Android and its Utility Library.

    360 GitHub stars~897 tokensUpdated 3 days ago
    MobileAuto-check passed
  • Task Workflow

    ikarenkov/Modo

    Spec-driven workflow for non-trivial work. An agent skill from ikarenkov/Modo.

    343 GitHub stars~2.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed
  • Code Steward

    nekomangaorg/Neko

    Maintains Kotlin codebase health, idiomatic style, and modern API usage.

    2.8k GitHub stars~977 tokensUpdated yesterday
    MobileAuto-check passed

More from rosuH/EasyWatermark

All 28 skills in this repo
  • Deferring State Reads

    rosuH/EasyWatermark

    A skill your agent uses to push frequently-changing Jetpack Compose state reads (scroll position, animation values, drag offsets) out of the Composition phase and down into Layout or Draw using…

    1.9k GitHub starsUsed in 1 repo~3.8k tokens
    Auto-check passed
  • Diagnosing Compose Stability

    rosuH/EasyWatermark

    A skill your agent uses to diagnose Jetpack Compose stability problems by enabling and reading the Compose Compiler Reports (classes.txt, composables.txt, composables.csv, module.json).

    1.9k GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check passed
  • Generating Baseline Profiles

    rosuH/EasyWatermark

    A skill your agent uses to generate and measure Jetpack Compose Baseline Profiles end-to-end with the AGP 8.2+ Baseline Profile Generator module and the Macrobenchmark harness.

    1.9k GitHub starsUsed in 1 repo~5k tokens
    Auto-check passed
  • Migrating To Modifier Node

    rosuH/EasyWatermark

    A skill your agent uses to author new custom Jetpack Compose modifiers and migrate legacy ones from Modifier.composed { } to Modifier.Node + ModifierNodeElement<T.

    1.9k GitHub starsUsed in 1 repo~5k tokens
    Auto-check passed
  • ML Kit Genai Prompt API

    rosuH/EasyWatermark

    Analyzes Android codebases to implement ML Kit GenAI Prompt API.

    1.9k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Stabilizing Compose Types

    rosuH/EasyWatermark

    A skill your agent uses to fix unstable Jetpack Compose types once a stability diagnosis has identified them.

    1.9k GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed

Works with

Questions about Understanding Hot Reload Limits

What does Understanding Hot Reload Limits do?

A skill your agent uses to teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback. Understanding Hot Reload Limits is an agent skill from rosuH/EasyWatermark. 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.

When should I use Understanding Hot Reload Limits?

Understanding Hot Reload Limits fits situations like: teach Claude exactly which Kotlin and Compose changes hot-reload under Compose HotSwan and which trigger a full incremental rebuild fallback; the user asks why did this rebuild?; why isnt this hot reloading?; wants to learn HotSwans boundaries before adopting it.

How do I install Understanding Hot Reload Limits in Claude Code?

Run `npx skills add rosuH/EasyWatermark --skill understanding-hot-reload-limits -a claude-code`. Or copy the skill folder (.agents/skills/understanding-hot-reload-limits in rosuH/EasyWatermark) into .claude/skills/understanding-hot-reload-limits in your project. Claude Code loads it when a task matches its description.

How do I install Understanding Hot Reload Limits in Codex?

Run `npx skills add rosuH/EasyWatermark --skill understanding-hot-reload-limits -a codex`. Or copy the skill folder (.agents/skills/understanding-hot-reload-limits in rosuH/EasyWatermark) into .agents/skills/understanding-hot-reload-limits in your project. Codex loads it when a task matches its description.

Can I use Understanding Hot Reload Limits in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rosuH/EasyWatermark --skill understanding-hot-reload-limits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/understanding-hot-reload-limits, .gemini/skills/understanding-hot-reload-limits, .github/skills/understanding-hot-reload-limits and .opencode/skills/understanding-hot-reload-limits in your project.

What does Understanding Hot Reload Limits need to run?

SKILL.md names no scripts, command-line tools or credentials: Understanding Hot Reload Limits is instructions for the agent only.

Does Understanding Hot Reload Limits access the network?

SKILL.md names 2 domains. As links in the text: github.com and source.android.com. This is read from the text; nothing was executed.

Is Understanding Hot Reload Limits safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Understanding Hot Reload Limits use?

Understanding Hot Reload Limits is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Understanding Hot Reload Limits use?

About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Understanding Hot Reload Limits?

Skills that share tags, products or a category with Understanding Hot Reload Limits: Architecture Overclock (nekomangaorg/Neko, 2.8k stars), Architecture Renovator (nekomangaorg/Neko, 2.8k stars), Android Gradle Build Logic (rcosteira79/android-skills, 153 stars) and Android Maps Ktx (googlemaps/android-maps-ktx, 360 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Understanding Hot Reload Limits?

rosuH (a GitHub user) maintains it in rosuH/EasyWatermark, which has 1,895 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 10, 2026.

Source: rosuH/EasyWatermark on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.