← ClaudeAtlas

figma-ticketslisted

Converts Figma page/frame comments into structured design tickets. This skill should be used when the user provides a Figma URL and wants to extract comment threads and turn them into actionable design/UX tickets. Triggers on phrases like "figma tickets", "turn these comments into tickets", "extract tickets from Figma", or when /figma-tickets is invoked with a Figma link.
madebysan/claude-figma-skills · ★ 0 · Data & Documents · score 72
Install: claude install-skill madebysan/claude-figma-skills
# Figma to Ticket ## Purpose Extract all comment threads from a Figma page or frame and convert them into structured design/UX tickets, saved as a markdown file on the Desktop. This bridges QA feedback living in Figma comments with an actionable ticket backlog. ## SCOPE CONSTRAINT Only produce **design and UX tickets**. Output must exclusively cover: screens, flows, UI components, interaction patterns, visual states, motion, copy, and layout. **NEVER** create tickets for backend logic, APIs, databases, data models, or infra. If eng work is required, add one line in Dependencies: `"Requires: [brief eng need]"`. **NEVER** modify Figma comments — do not resolve, delete, or edit any comments. This skill is read-only against Figma. ## Workflow ### Step 1: Validate Figma Connection Before starting, verify the Figma MCP connection: 1. Run `figma_get_status` to check WebSocket connectivity 2. If not connected, instruct the user to open the Desktop Bridge plugin in Figma Desktop (Plugins > Development > Figma Desktop Bridge) 3. Do not proceed until the connection is confirmed ### Step 2: Parse the Figma URL Extract from the provided Figma URL: - **fileKey** — the alphanumeric ID in the URL path (e.g., `cXLeGNOjpN5bvXrlHE9aRm`) - **node-id** — from the `node-id` query parameter (e.g., `7345-17056`) Use `figma_navigate` to connect to the file if not already connected. ### Step 3: Identify the Target Page/Frame Use `figma_get_file_data` with the extracted node ID to determ