What problem does it solve? Writing code for Lens Studio's ExecuteEditorCode tool is error-prone: the Editor API differs from Lens Scripting, interfaces have strict namespace rules, and common operations have dedicated tools that should be preferred. This Skill provides the contract, access patterns, gotchas, and reference snippets needed to write correct Editor API TypeScript on the first attempt. ## Core Features & Use Cases - Decision rules: Routes tasks to dedicated tools (scene-graphql, asset-graphql) when appropriate and reserves ExecuteEditorCode for bulk operations, custom traversals, and atomic multi-step mutations. - API access patterns: Documents pluginSystem.findInterface(Editor.Model.IModel) entry points and await import("LensStudio:<Name>") module loading, including the hidden-module rule. - Gotcha prevention: Encodes critical rules such as vec3-only transforms, Euler-degree rotations, ComponentNameMap keys, and JSON-serializable return values. - Reference library: Ships working snippets for asset operations, scene object operations, camera/rendering, presets, and project lifecycle (open, save, export, Lens metadata). - Use Case: When asked to create 64 scene objects in a grid or rename assets in bulk, consult this Skill to produce a single correct EEC snippet instead of guessing API signatures from editor.d.ts. ## Quick Start Ask the agent to write an ExecuteEditorCode snippet that creates a grid of scene objects in the current Lens Studio project.
