What problem does it solve? Debugging Lens Studio Lenses is hard because symptoms like invisible objects, pink materials, or handlers that never fire can originate in rendering, scripting, physics, or tracking layers. This Skill triages a symptom description and routes it to the correct specialist skill or reference document instead of guessing at fixes. ## Core Features & Use Cases - Symptom-based decision tree: Maps visual symptoms (invisible, glitchy, pink material, layout wrong) and runtime symptoms (glued to head, handler not firing, asset not ready, physics drifting) to targeted triage cards in references/known-issues.md. - Specialist routing: Directs TypeScript scripting bugs to lens-api debugging references, Specs subsystem issues (SIK, RSG, SyncKit, VIO/SLAM) to specs-debug, and log reading to lens-log-analysis. - Debugging discipline: Enforces a Step 0 sanity check (Lens compiles, startup log clean, scene wiring complete), pacing rules for guessing vs incremental diagnosis, and a stop-and-ask rule when incremental debugging stalls. - Use Case: A developer reports an object stays glued to the camera. The Skill routes to the known-issues card, which identifies the missing DeviceTracking component or wrong parent transform as the most common cause. ## Quick Start Ask the agent to debug why my Lens Studio object is invisible at runtime using the lens-debug skill.
