figma-deep-component — unlimited-depth tree with resolved tokens

Walk one node (usually a COMPONENT / COMPONENT_SET / INSTANCE, but any node works) recursively to a depth you choose, capturing at every level: layout (auto-layout, padding, spacing, sizing), visual properties (fills, strokes, stroke weight, corner radius, effects, opacity), typography for text nodes, boundVariables resolved to token names + code syntax, INSTANCE main-component references (including whether the main is a variant and its set), prototype reactions, and dev-mode annotations. This is the richest single-component read for high-fidelity code generation.

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).
• Whole-file inventory (all tokens/components/styles at once) → use figma-design-system-inventory.
• Variant set as a CSS state machine (per-state diffs, pseudo-class mapping) → use figma-analyze-component-set.
• This depth of tree + resolved tokens + reactions is not what the native MCP's get_design_context (rendered single-selection summary) or get_metadata (flat structure) return — it is a design-system code-gen capability layered on top.

Workflow