What problem does it solve? Starting a Lens Studio, Specs, or Snapchat Lens build requires the right project open, a compatible Lens Studio version, a reachable MCP server, and a signed-in user — and then the request must reach the correct platform workflow. This Skill performs that environment detection, readiness gating, and platform routing automatically so builds never start against a broken or ambiguous setup. ## Core Features & Use Cases - Project Detection and Readiness Gate: Finds the .esproj project at the working directory, verifies Lens Studio 5.22+ is installed and running, probes the MCP server, and enforces a mandatory sign-in check before any build work begins. - Platform Routing: Resolves Specs vs Snapchat from the user's request, the project's targetPlatform, or a blocking question — never guessing — then hands off to the specs-experience-builder subagent or the core Snapchat Lens Studio skills. - Preflight Mode and Blocked Payloads: Supports a preflight_only mode for readiness checks without triggering a build, and emits structured blocked payloads with specific reasons (e.g. mcp_plugin_off, not_signed_in, wrong_project_open) plus suggested next steps when anything fails. - Use Case: You ask your coding agent to "build a Specs game" from a Lens Studio project directory. The router confirms the project is open, MCP is live, and you are signed in, then spawns the Specs builder with a complete handoff payload — or tells you exactly what to fix first. ## Quick Start Ask your agent to build a Specs or Snapchat Lens experience from inside your Lens Studio project directory and let the router prepare the environment and route the request.
