figma-extractor

Solid

Extract design tokens, styles, component metadata, and screen structure from Figma files via MCP. Use whenever a figma.com URL appears, when someone mentions Figma tokens, variables, design system extraction, screen captures, text styles, shadows, component properties, or library assets. Trigger for phrases like 'get from Figma', 'extract design', 'Figma variables', 'design tokens', 'capture screens', 'get typography from Figma', 'extract shadows', 'find components in library', 'get code syntax for tokens', or any figma.com/design link. Even if the user just pastes a Figma link without instructions, use this skill to parse it and decide what to extract. Covers three extraction depths: Level 1 (quick read-only MCP), Level 2 (deep extraction via Plugin API scripts), Level 3 (library search + component property metadata).

Data & Documents 13 stars 2 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
38
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Figma Extractor Extract design tokens, styles, component metadata, and screen structure from Figma files. Process: **CHECK → PARSE → DISCOVER → EXTRACT → ORGANIZE** Every extracted value carries a source tag — downstream consumers use this for conflict resolution priority. A variable definition is stronger evidence than an inferred applied style. ## Extraction Levels Not every workflow needs every tool. Three levels control extraction depth: ``` Level 1 (Quick): whoami → get_metadata → get_variable_defs → get_design_context → get_screenshot Fast, read-only MCP tools. No Plugin API. Level 2 (Deep): Level 1 + use_figma read-only scripts Adds: collections with modes, codeSyntax, scopes, aliasing chains, text styles, effect styles, paint styles. Level 3 (Targeted): Level 2 + search_design_system + get_context_for_code_connect Adds: library asset discovery, exact component property definitions. ``` The calling workflow determines the level. When in doubt, start at Level 1 and escalate if data is sparse. ## use_figma Safety Boundary Level 2-3 use `use_figma` for **read-only extraction scripts only**. Scripts from `scripts/` are pre-built for this purpose. Rules: - Scripts MUST NOT create, modify, or delete any nodes, variables, or styles - Every script ends with `return { ... }` containing extracted data - If `use_figma` is unavailable → graceful fallback to Level 1 - Pass `skillNam...

Details

Author
app-builders-club
Repository
app-builders-club/mvp-builder
Created
1 years ago
Last Updated
5 days ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category