figma-deep-component
Skill83 starsChanged 6 months agoMITView on GitHub
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.
In this repository22 other files it gives its agents.
- figjam-create-contentSkill
- figma-analyze-component-setSkill
- figma-annotationsSkill
- figma-arrange-component-setSkill
- figma-audit-accessibilitySkill
- figma-blame-nodeSkill
- figma-check-design-paritySkill
- figma-commentsSkill
- figma-component-propertiesSkill
- figma-design-system-inventorySkill
- figma-export-tokensSkill
- figma-extract-design-systemSkill
- figma-generate-changelogSkill
- figma-generate-component-docSkill
- figma-import-tokensSkill
- figma-library-variablesSkill
- figma-lint-designSkill
- figma-manage-variablesSkill
- figma-scan-code-accessibilitySkill
- figma-setup-design-tokensSkill
- figma-slidesSkill
- figma-version-historySkill
The file
Files
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_figmarules — load the officialfigma-useskill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-levelawait+return(no IIFE, nofigma.closePlugin();console.logis not returned), inputs inlined asconstat 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) orget_metadata(flat structure) return — it is a design-system code-gen capability layered on top.
Workflow
- Get the node id. From selection (
figma_get_selection), search, or a pasted id. - Choose a depth. Set
const DEPTH(default 10). Deep design components rarely exceed ~6 levels; use a smaller number first to keep the payload manageable, then go deeper if needed. - Run
scripts/deep-component.jsviause_figma(skillNames: "figma-deep-component"). Setconst NODE_IDandconst DEPTHat the top. - Generate code. The returned tree mirrors the DOM you should build. Prefer
boundVariablestoken names (and theircodeSyntax) over raw hex; usemainComponentrefs to reuse imported components; usereactionsto wire up interaction/navigation. - If the payload is too big, lower
DEPTH(nodes past the limit are summarized with achildCount+_depthLimitReachedmarker) or target a smaller sub-node id.
What each node carries
- Identity:
id,name,type,visible. Hidden non-component nodes are marked_hiddenand not recursed. - Layout:
layoutMode, axis sizing/align,padding*,itemSpacing,counterAxisSpacing,layoutWrap, min/max width/height,clipsContent. - Visual:
fills,strokes,strokeWeight,cornerRadius,effects,opacity(only when non-default;figma.mixedvalues are skipped safely). - Typography (TEXT):
characters,fontSize,fontFamily/fontStyle,fontWeight,lineHeight,letterSpacing, alignment, truncation, case, decoration. - Tokens:
boundVariablesresolved to{ id, name, collection, resolvedType, codeSyntax }per bound property. - Instances:
mainComponent(id,name,key,isVariant, set name/id) +componentProperties. - Definitions (COMPONENT/COMPONENT_SET):
componentPropertyDefinitions,variantProperties. - Prototype:
reactions(trigger + action: navigation/transition/destination). - Dev:
annotations(label markdown + categorized properties).
Notes
- Resolved tokens work on ANY plan — the variable lookup is built via the Plugin API, so even
non-Enterprise files get token names instead of opaque
VariableID:aliases. - The root node echoes
_variableMapSizeand_maxDepthUsedfor sanity-checking. - Returns
affectedNodeIds: [NODE_ID]even though this is a read — keeps the convention uniform.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

