What problem does it solve? Server-rendered jsgui3 pages sometimes fail to come alive in the browser: clicks do nothing, persisted fields never hydrate, and the console fills with cryptic warnings like "Missing context.map_Controls" or "&&& no corresponding control". This Skill explains the real runtime path from SSR HTML to client activation so you can pinpoint and patch the exact failure point. ## Core Features & Use Cases - Activation Path Tracing: Walks through the full client boot sequence (Client_Page_Context creation, pre_activate reconstruction, depth-first activate) so you know exactly where hydration breaks. - Data Bridge Decoding: Explains how data-jsgui-fields hydrates _persisted_fields and how data-jsgui-ctrl-fields wires named child controls like this.btn or this.status. - Warning Triage & Patching: Interprets common console warnings and offers safe patch strategies, from silencing known-noise logs to registering missing control types and handling whitespace text nodes. - Use Case: Your SSR docs viewer renders fine but the collapsible nav and sortable column headers are inert. Use this Skill to confirm the bridge attributes exist, discover the ctrl_fields binding failed, and apply the validated manual DOM query pattern in activate(). ## Quick Start Ask the AI to debug why my jsgui3 server-rendered page renders correctly but its buttons do not respond to clicks after client activation.
