What problem does it solve? When a user shares a Figma link, an AI agent often guesses at the wrong tool, hits a login wall in a simple browser, or retries weak fallbacks without diagnosing the real blocker. This Skill defines the local routing rules for reading Figma designs through the Figma MCP server first, with a clearly defined authenticated browser fallback. ## Core Features & Use Cases - Figma MCP routing: Reads design files, node context, specs, and copy through the Figma MCP tools exposed in the session, handling fileKey, branchKey, and node-id URL forms. - Blocker taxonomy: Classifies failures precisely as tool unavailable, unsupported URL, missing input, or auth/access issues instead of blindly retrying. - Authenticated fallback: Uses extension-backed Playwright MCP with an authenticated Chrome session when the MCP route fails, avoiding unauthenticated simple-browser dead ends. - Use Case: A designer shares a Figma URL with a node-id and asks whether the implemented UI matches. The Skill reads the node specs via Figma MCP, then hands off to a UI validation workflow for comparison. ## Quick Start Read the Figma design at this URL and extract the specs and copy for the selected node.