What problem does it solve? Lens Studio agent work fails silently when tools are misused: raw HTTP workarounds bypass MCP tools, wrong-phase surfaces cause no-ops, and mixed-surface patching leaves orphaned scene state. This Skill centralizes the hard rules, cross-runtime orchestration patterns, and verification recipes that prevent those failures. ## Core Features & Use Cases - Hard Rules for MCP Usage: Enforces VirtualScene-first scene writes, bare tool naming across Claude Code, Codex, and Cursor runtimes, and correct unit/coordinate conventions (centimeters, right-handed, degrees vs radians). - See-and-Fix Verification Loop: Defines a canonical recipe using RecompileTypeScriptTool, RunAndCollectLogsTool, and CaptureRuntimeViewTool to visually validate builds, including a blind-spot checklist for animation, heavy scenes, and silent failures. - Editor API Delegation Guidance: Specifies when to load the editor-api skill inline versus delegating to the editor-api-specialist subagent, with rules for writing actionable delegation instructions. - Use Case: While building a Spectacles Lens, an agent consults these field notes to choose VirtualScene over scene-graphql mutations, run the platform init skill before previewing, and verify the result with a two-timestamp capture loop. ## Quick Start Ask the agent to load the lens-studio-field-notes skill before starting any Lens Studio scene construction or debugging task.
