What problem does it solve? Building location-locked AR experiences on Specs requires wiring LocationAssets, LocatedAtComponent lifecycle events, scan meshes, and activation logic in Lens Studio — a multi-step process where small mistakes (like gating content on onFound, which never fires in the editor) silently break the experience. ## Core Features & Use Cases - Location Asset Setup: Create LocationAsset, LocationMesh, and Location Material via asset-graphql or the Editor API, wire a published Location ID, and build the Custom Location scene node with LocatedAtComponent and RenderMeshVisual. - Activation Framework: Drop-in TypeScript scripts (LocationActivator, ScaleInLocatedObject, AudioLocatedObject, LocationStatusLogger) that gate content on localization events with proximity hysteresis and an editor-testing branch. - Location Groups & Incremental Scans: Link up to 5 nearby locations with CustomLocationGroupComponent, and add viewpoints to existing scans without repositioning content. - Use Case: Build a site-specific AR tour where content appears only when visitors physically arrive at a scanned location, with the scan mesh hidden on device but visible in the editor for placement. ## Quick Start Ask the agent to create a Custom Location node in Lens Studio wired to a published Location ID with content parented under it and the scan mesh hidden on device.
