What problem does it solve? Debugging a JavaScript Lens that only misbehaves while running — init crashes, missing awaits, callback wiring bugs, runtime data shape issues — is hard without a live debugger. This Skill provides a CLI (lsdbg) that attaches to a running Lens Studio preview or Specs device over the Chrome DevTools Protocol, letting an agent evaluate expressions, set breakpoints, pause/resume execution, inspect runtime state, and profile CPU hot spots. ## Core Features & Use Cases - Live debugging session: lsdbg attach blocks until the VM is live, then supports eval, set-breakpoint, backtrace, locals, eval-on-frame, stepping, and resume against the Hermes VM. - Console and exception visibility: console-log streams buffered output as NDJSON with --wait-pattern matching, and pause-on-exceptions surfaces synchronous throws. - CPU profiling: profile-start / profile-stop return a self-time-ranked hot-function summary for diagnosing jank. - Health diagnosis and recovery: health collapses states like init_throw, preview_idle, and wrong_target into one field, and cleanup --force recovers wedged daemons. - Use Case: A Lens crashes in onAwake before you can interact with it. Set a breakpoint with --reload, wait for the pause, inspect locals and the backtrace, then fix the init code. ## Quick Start Ask the agent to debug your running Lens by attaching with lsdbg, setting a breakpoint on the suspect line with --reload, and evaluating the relevant expressions once paused.
