figma-design-system-inventorylisted

One call to inventory an entire Figma design system — variables/tokens (grouped by collection + mode), components and component sets (with property definitions and per-variant visual specs), and styles (color/text/effect with resolved values). Use when you need the whole design-system picture before generating code or auditing coverage — triggers: 'inventory my design system', 'extract all tokens and components', 'what's in this design system', 'dump the design system kit', 'give me every variable, component, and style', 'build a design-system manifest', 'audit my Figma library'. Has a verbosity/scope guard so big files don't blow the response budget. Goes well beyond the native MCP's get_design_context (single-selection) / get_metadata.
whiskfernlowdensitylipoprotein154/figma-console-mcp-skills · ★ 0 · Web & Frontend · score 75

Install: claude install-skill whiskfernlowdensitylipoprotein154/figma-console-mcp-skills

# figma-design-system-inventory — unified tokens + components + styles extraction A single `use_figma` call that walks the whole file and returns a structured kit: **tokens** (every local variable, grouped by collection and mode), **components** (standalone components + component sets, with property definitions and a compact `visualSpec` per variant), and **styles** (paint/text/effect styles with their resolved values). It is the "read everything once" front door for code generation and library audits. ## Skill boundaries - **`use_figma` rules** — load the official **`figma-use`** skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level `await` + `return` (no IIFE, no `figma.closePlugin()`; `console.log` is not returned), inputs inlined as `const` at the top of each script, colors in 0–1 range, load fonts before any text op, `await figma.getNodeByIdAsync(...)`, and **atomic errors** (a failed script applies nothing — read the error, fix, retry). - **The exact shape of each `visualSpec`** → [references/visual-spec.md](references/visual-spec.md). - **One component in unlimited depth** (full tree, reactions, instance refs) → use `figma-deep-component`. **One variant set as a CSS state machine** → use `figma-analyze-component-set`. **Token files on disk** → use `figma-export-tokens`. - This is a **whole-system design capability** the native MCP does not have: `get_design_context` works on a single selection and `get