What problem does it solve? Setting up Compose HotSwan involves coordinating a JetBrains IDE plugin, a Gradle compiler plugin, version catalog entries, and a specific DSL block, and small mistakes like a lowercase extension name or a missing debugOnly flag silently break the workflow or leak diagnostic transformations into release builds. ## Core Features & Use Cases - Canonical Gradle wiring: Provides the exact libs.versions.toml plugin declaration, root apply false pattern, and per-module alias(...) application for the com.github.skydoves.compose.hotswan.compiler plugin. - Production-safe configuration: Enforces the hotSwanCompiler { enabled = true; debugOnly = true } DSL block so HotSwan transformations never ship in release builds. - End-to-end verification: Walks through the HotSwan tool window flow from READY to WATCHING and confirms the first save-to-reload round-trip preserves navigation, scroll, and remember state. - Use Case: A developer who just installed the HotSwan JetBrains Marketplace plugin asks how to wire the Gradle compiler plugin into an existing Compose project and verify hot reload works on a physical device. ## Quick Start Set up Compose HotSwan in my Android project and verify hot reload works on my connected device.
