figma-discover

Convert a Figma frame URL or nodeId into a single JSON blob of variables, regions, and states.

2|5|Updated Oct 24, 2023
One-click install
npx skills add https://github.com/aziontech/webkit --skill figma-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: figma-discover
Source: https://github.com/aziontech/webkit/tree/main/.claude/skills/figma-discover
Command: npx skills add https://github.com/aziontech/webkit --skill figma-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a Figma frame into a structured, token-ready JSON payload so downstream pipelines can generate consistent design system outputs without manually interpreting the frame.

Core Features & Use Cases

  • Design token discovery: Extracts named variables (with resolved values) from the target frame.
  • Component anatomy and behavior: Captures regions (e.g., header/body/footer/actions) and interactive states (default/hover/active/focus/disabled, plus other exposed states).
  • Token pipeline compatibility: Emits a single JSON blob to stdout for immediate consumption by the next step that maps tokens.

Quick Start

Use the figma-discover skill by providing a Figma frame URL (or nodeId) to produce a single JSON blob containing variables, regions, and states.

Frequently Asked Questions about figma-discover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a Figma frame into design tokens for my pipeline?

Extracting design tokens from a Figma frame requires passing a frame URL or nodeId to read its named variables and resolved values. The process outputs a single JSON blob containing component regions and interactive states for immediate pipeline consumption.

What design data is captured during Figma component discovery?

Figma component discovery captures named variables with resolved values, component anatomy regions like header or footer, and interactive states including default, hover, active, focus, and disabled. This data is normalized into a single structured JSON payload.

Can I use Figma MCP calls to extract component states without modifying the file?

Yes, extracting component states uses read-only Figma MCP calls to query the frame. It normalizes the reported design inputs into a JSON blob without generating prose or causing side effects, ensuring the original Figma file remains unmodified.

Does the Figma to JSON output include component anatomy and behavior?

Yes, the JSON output includes component anatomy and behavior by capturing structural regions and interactive states. It extracts these design inputs exactly as Figma reports them during the component discovery and spec creation workflows.

What is the best way to automate design token generation from Figma?

Automating design token generation from Figma is best achieved by converting frame URLs into token-ready JSON payloads. This approach emits standardized JSON output to stdout, allowing the next pipeline step to map tokens without manually interpreting the frame.

Why does the Figma discovery output only emit JSON and no prose?

The Figma discovery output emits only JSON and no prose to ensure token-generation pipelines receive clean, structured data. This prevents parsing errors and allows downstream automation to consume the single JSON blob directly from stdout.