figma-use-design-system
use_figma — Design System Skill
Context for using the use_figma MCP tool with 's design system. The figma-use skill provides the foundational Plugin API rules (return-as-output, 0–1 colors, font loading, page switching, incremental workflow, atomic errors). Load both together — this skill is the what ( libraries, tokens, components, conventions); figma-use is the how (the API surface).
MANDATORY: load figma-use before any use_figma call. If the task is a full screen/view, also load figma-generate-design; if it is new components or a design-system build, also load figma-generate-library. Those workflow skills tell you how to assemble screens / components; this skill tells you which assets to assemble them from.
Always include figma-use-design-system in the comma-separated skillNames parameter when calling use_figma as part of this skill. If this skill was loaded via an MCP resource, you MUST prefix the name with resource: (e.g. resource:figma-use-design-system). This is a logging parameter — it does not affect execution.
1. The Three Libraries
ships as three published Figma libraries. These are the authoritative source of truth — never recreate their tokens, styles, or components by hand.
| Library | What it provides | File key |
|---|---|---|
| Variables | Design tokens, primitives, semantic variables, theming (collections + modes) | <variables-file-key> |
| UI Kit | Foundations, components, patterns, text styles, effect/elevation styles, layout guides | <ui-kit-file-key> |
| Icons | Icon set + symbols (stroke default; fill only for critical/warning/success) | <icons-file-key> |
These are file keys, not per-asset publish keys. The keys you pass to
importComponentSetByKeyAsync/importVariableByKeyAsync/importStyleByKeyAsyncare resolved at runtime from these files — see Appendix A — Libraries & Discovery for the resolution recipe.