figma-deep-componentlisted

Extract a single Figma component (or any node) as a full recursive tree to N levels deep — every child's layout, fills/strokes/effects, typography, resolved bound variables (token names + code syntax), INSTANCE mainComponent references, prototype reactions, and annotations. Use when you need maximum-fidelity data to generate production code for ONE component — triggers: 'get the full component tree', 'deep extract this component', 'give me everything about this node for code gen', 'resolve all the tokens in this component', 'what instances does this component nest', 'extract reactions/prototype links', 'high-fidelity component spec'. Resolves bound variables to token names on ANY plan. Far deeper than the native MCP's get_design_context / get_metadata.
whiskfernlowdensitylipoprotein154/figma-console-mcp-skills · ★ 0 · Web & Frontend · score 75

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

# 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`