What problem does it solve? Adding UI features to HOT-Step CPP requires navigating undocumented conventions: hand-rolled pushState routing, three coexisting state-store patterns, a single request-assembly function, and strict i18n/Tailwind rules. Missing any one registration step produces silent failures like studios that break on refresh or sliders that do nothing. ## Core Features & Use Cases - Studio Registration Procedure: Walks through the five required edits (import, viewFromUrl, urlForView, renderContent branch, Sidebar NavItem) to add a new studio that survives refresh and back-button navigation. - State & API Patterns: Documents the hand-rolled useSyncExternalStore store template, the zustand globalParamsStore with per-key localStorage persistence, and the per-studio submit-then-poll API client shape. - Failure Diagnosis: Provides a symptom-to-cause table covering routing breaks, snake_case leaks, StrictMode double-invocation, and params dropped by the /lm round trip. - Use Case: You want to add a new "Mastering Studio" panel with a slider wired to a generation parameter. The skill gives the exact files, line references, and golden rules (e.g., wire the param into getGlobalParams(), never extend the LM echo pick-list) to implement it correctly. ## Quick Start Use the ui-feature-dev skill to add a new studio called Mastering Studio with a volume slider wired into the generation request.
