设计与多媒体

figma-generate-library

试用

把代码库转换成与代码一致的 Figma 设计系统,分阶段推进、每步确认。

它能做什么

按固定阶段顺序从代码库搭建 Figma 设计系统:先做代码与 Figma 文件的勘察并锁定 v1 范围,再建变量与 token,然后搭页面结构,接着逐个创建组件,最后补 Code Connect 映射并做可访问性、命名和绑定审计。每个阶段结束都有用户确认点,需要看到产物并明确批准才继续。构建状态会写入 /tmp/dsb-state-{RUN_ID}.json,上下文被截断后可据此恢复。本技能负责设计系统领域知识和流程编排,Plugin API 语法由 figma-use 技能提供,两者需同时加载。

什么时候用它

  • 把代码库里的 token 和组件提取成 Figma 变量
  • 用语义变量别名到基础变量,搭建明暗主题
  • 按依赖顺序逐个搭建带变体、属性和文档页的组件库
  • 对照代码审计 Figma 文件里的硬编码颜色、缺失 scope 和命名问题

技能文档

Design System Builder — Figma MCP Skill

Build professional-grade design systems in Figma that match code. This skill orchestrates multi-phase workflows across 20–100+ use_figma calls, enforcing quality patterns from real-world design systems (Material 3, Polaris, Figma UI3, Simple DS).

Prerequisites: The figma-use skill MUST also be loaded for every use_figma call. It provides Plugin API syntax rules (return pattern, page reset, ID return, font loading, color range). This skill provides design system domain knowledge and workflow orchestration.

Always pass skillNames: "figma-generate-library" when calling use_figma as part of this skill. This is a logging parameter — it does not affect execution.


1. The One Rule That Matters Most

This is NEVER a one-shot task. Building a design system requires 20–100+ use_figma calls across multiple phases, with mandatory user checkpoints between them. Any attempt to create everything in one call WILL produce broken, incomplete, or unrecoverable results. Break every operation to the smallest useful unit, validate, get feedback, proceed.


2. Mandatory Workflow

Every design system build follows this phase order. Skipping or reordering phases causes structural failures that are expensive to undo.

Phase 0: DISCOVERY (always first — no use_figma writes yet)
  0a. Analyze codebase → extract tokens, components, naming conventions
  0b. Inspect Figma file → pages, variables, components, styles, existing conventions
  0c. Search subscribed libraries → use search_design_system for reusable assets
  0d. Lock v1 scope → agree on exact token set + component list before any creation
  0e. Map code → Figma → resolve conflicts (code and Figma disagree = ask user)
  ✋ USER CHECKPOINT: present full plan, await explicit approval

Phase 1: FOUNDATIONS (tokens first — always before components)
  1a. Create variable collections and modes
  1b. Create primitive variables (raw values, 1 mode)
  1c. Create semantic variables (aliased to primitives, mode-aware)
  1d. Set scopes on ALL variables
  1e. Set code syntax on ALL variables
  1f. Create effect styles (shadows) and text styles (typography)
  → Exit criteria: every token from the agreed plan exists, all scopes set, all code syntax set
  ✋ USER CHECKPOINT: show variable summary, await approval

Phase 2: FILE STRUCTURE (before components)
  2a. Create page skeleton: Cover → Getting Started → Foundations → --- → Components → --- → Utilities
  2b. Create foundations documentation pages (color swatches, type specimens, spacing bars)
  → Exit criteria: all planned pages exist, foundations docs are navigable
  ✋ USER CHECKPOINT: show page list + screenshot, await approval

Phase 3: COMPONENTS (one at a time — never batch)
  For EACH component (in dependency order: atoms before molecules):
    3a. Create dedicated page
    3b. Build base component with auto-layout + full variable bindings
    3c. Create all variant combinations (combineAsVariants + grid layout)
    3d. Add component properties (TEXT, BOOLEAN, INSTANCE_SWAP)
    3e. Link properties to child nodes
    3f. Add page documentation (title, description, usage notes)
    3g. Validate: get_metadata (structure) + get_screenshot (visual)
    3h. Optional: lightweight Code Connect mapping while context is fresh
    → Exit criteria: variant count correct, all bindings verified, screenshot looks right
    ✋ USER CHECKPOINT per component: show screenshot, await approval before next component

Phase 4: INTEGRATION + QA (final pass)
  4a. Finalize all Code Connect mappings
  4b. Accessibility audit (contrast, min touch targets, focus visibility)
  4c. Naming audit (no duplicates, no unnamed nodes, consistent casing)
  4d. Unresolved bindings audit (no hardcoded fills/strokes remaining)
  4e. Final review screenshots of every page
  ✋ USER CHECKPOINT: complete sign-off

3. Critical Rules

Plugin API basics (from use_figma skill — enforced here too):

  • Use return to send data back (auto-serialized). Do NOT wrap in IIFE or call closePlugin.
  • Return ALL created/mutated node IDs in every return value
  • Page context resets each call — always await figma.setCurrentPageAsync(page) at start
  • figma.notify() throws — never use it
  • Colors are 0–1 range, not 0–255
  • Font MUST be loaded before any text write: await figma.loadFontAsync({family, style})

Design system rules:

  1. Variables BEFORE components — components bind to variables. No token = no component.
  2. Inspect before creating — run read-only use_figma to discover existing conventions. Match them.
  3. One page per component (default) — exception: tightly related families (e.g., Input + helpers) may share a page with clear section separation.
  4. Bind visual properties to variables (default) — fills, strokes, padding, radius, gap. Exceptions: intentionally fixed geometry (icon pixel-grid sizes, static dividers).
  5. Scopes on every variable — NEVER leave as ALL_SCOPES. Background: FRAME_FILL, SHAPE_FILL. Text: TEXT_FILL. Border: STROKE_COLOR. Spacing: GAP. Radii: CORNER_RADIUS. Primitives: [] (hidden).
  6. Code syntax on every variable — WEB syntax MUST use the var() wrapper: var(--color-bg-primary), not --color-bg-primary. Use the actual CSS variable name from the codebase. ANDROID/iOS do NOT use a wrapper.
  7. Alias semantics to primitives — { type: 'VARIABLE_ALIAS', id: primitiveVar.id }. Never duplicate raw values in semantic layer.
  8. Position variants after combineAsVariants — they stack at (0,0). Manually grid-layout + resize.
  9. INSTANCE_SWAP for icons — never create a variant per icon. Cap variant matrices: if Size × Style × State > 30 combinations, split into sub-component.
  10. Deterministic naming — use consistent, unique node names for idempotent cleanup and resumability. Track created node IDs via return values and the state ledger.
  11. No destructive cleanup — cleanup scripts identify nodes by name convention or returned IDs, not by guessing.
  12. Validate before proceeding — never build on unvalidated work. get_metadata after every create, get_screenshot after each component.
  13. NEVER parallelize use_figma calls — Figma state mutations must be strictly sequential. Even if your tool supports parallel calls, never run two use_figma calls simultaneously.
  14. Never hallucinate Node IDs — always read IDs from the state ledger returned by previous calls. Never reconstruct or guess an ID from memory.
  15. Use the helper scripts — embed scripts from scripts/ into your use_figma calls. Don't write 200-line inline scripts from scratch.
  16. Explicit phase approval — at each checkpoint, name the next phase explicitly. "looks good" is not approval to proceed to Phase 3 if you asked about Phase 1.

4. State Management (Required for Long Workflows)

getPluginData() / setPluginData() are NOT supported in use_figma. Use getSharedPluginData() / setSharedPluginData() instead (these ARE supported), or use name-based lookups and the state ledger (returned IDs).

Entity typeIdempotency keyHow to check existence
Scene nodes (pages, frames, components)setSharedPluginData('dsb', 'key', value) or unique namenode.getSharedPluginData('dsb', 'key') or page.findOne(n => n.name === 'Button')
VariablesName within collection(await figma.variables.getLocalVariablesAsync()).find(v => v.name === name && v.variableCollectionId === collId)
StylesNamegetLocalTextStyles().find(s => s.name === name)

Tag every created scene node immediately after creation:

node.setSharedPluginData('dsb', 'run_id', RUN_ID);        // identifies this build run
node.setSharedPluginData('dsb', 'phase', 'phase3');        // which phase created it
node.setSharedPluginData('dsb', 'key', 'component/button');// unique logical key

State persistence: Do NOT rely solely on conversation context for the state ledger. Write it to disk:

/tmp/dsb-state-{RUN_ID}.json

Re-read this file at the start of every turn. In long workflows, conversation context will be truncated — the file is the source of truth.

Maintain a state ledger tracking:

{
  "runId": "ds-build-2024-001",
  "phase": "phase3",
  "step": "component-button",
  "entities": {
    "collections": { "primitives": "id:...", "color": "id:..." },
    "variables": { "color/bg/primary": "id:...", "spacing/sm": "id:..." },
    "pages": { "Cover": "id:...", "Button": "id:..." },
    "components": { "Button": "id:..." }
  },
  "pendingValidations": ["Button:screenshot"],
  "completedSteps": ["phase0", "phase1", "phase2", "component-avatar"]
}

Idempotency check before every create: query by name + state ledger ID. If exists, skip or update — never duplicate.

Resume protocol: at session start or after context truncation, run a read-only use_figma to scan all pages, components, variables, and styles by name to reconstruct the {key → id} map. Then re-read the state file from disk if available.

Continuation prompt (give this to the user when resuming in a new chat):

"I'm continuing a design system build. Run ID: {RUN_ID}. Load the figma-generate-library skill and resume from the last completed step."


5. search_design_system — Reuse Decision Matrix

Search FIRST in Phase 0, then again immediately before each component creation.

search_design_system({ query, fileKey, includeComponents: true, includeVariables: true, includeStyles: true })

Reuse if all of these are true:

  • Component property API matches your needs (same variant axes, compatible types)
  • Token binding model is compatible (uses same or aliasable variables)
  • Naming conventions match the target file
  • Component is editable (not locked in a remote library you don't own)

Rebuild if any of these:

  • API incompatibility (different property names, wrong variant model)
  • Token model incompatible (hardcoded values, different variable schema)
  • Ownership issue (can't modify the library)

Wrap if visual match but API incompatible:

  • Import the library component as a nested instance inside a new wrapper component
  • Expose a clean API on the wrapper

Three-way priority: local existing → subscribed library import → create new.


6. User Checkpoints

Mandatory. Design decisions require human judgment.

AfterRequired artifactsAsk
Discovery + scope lockToken list, component list, gap analysis"Here's my plan. Approve before I create anything?"
FoundationsVariable summary (N collections, M vars, K modes), style list"All tokens created. Review before file structure?"
File structurePage list + screenshot"Pages set up. Review before components?"
Each componentget_screenshot of component page"Here's [Component] with N variants. Correct?"
Each conflict (code ≠ Figma)Show both versions"Code says X, Figma has Y. Which wins?"
Final QAPer-page screenshots + audit report"Complete. Sign off?"

If user rejects: fix before moving on. Never build on rejected work.


7. Naming Conventions

Match existing file conventions. If starting fresh:

Variables (slash-separated):

color/bg/primary     color/text/secondary    color/border/default
spacing/xs  spacing/sm  spacing/md  spacing/lg  spacing/xl  spacing/2xl
radius/none  radius/sm  radius/md  radius/lg  radius/full
typography/body/font-size    typography/heading/line-height

Primitives: blue/50 → blue/900, gray/50 → gray/900

Component names: Button, Input, Card, Avatar, Badge, Checkbox, Toggle

Variant names: Property=Value, Property=Value — e.g., Size=Medium, Style=Primary, State=Default

Page separators: --- (most common) or ——— COMPONENTS ———

Full naming reference: naming-conventions.md


8. Token Architecture

ComplexityPattern
< 50 tokensSingle collection, 2 modes (Light/Dark)
50–200 tokensStandard: Primitives (1 mode) + Color semantic (Light/Dark) + Spacing (1 mode) + Typography (1 mode)
200+ tokensAdvanced: Multiple semantic collections, 4–8 modes (Light/Dark × Contrast × Brand). See M3 pattern in token-creation.md

Standard pattern (recommended starting point):

Collection: "Primitives"    modes: ["Value"]
  blue/500 = #3B82F6, gray/900 = #111827, ...

Collection: "Color"         modes: ["Light", "Dark"]
  color/bg/primary → Light: alias Primitives/white, Dark: alias Primitives/gray-900
  color/text/primary → Light: alias Primitives/gray-900, Dark: alias Primitives/white

Collection: "Spacing"       modes: ["Value"]
  spacing/xs = 4, spacing/sm = 8, spacing/md = 16, ...

9. Per-Phase Anti-Patterns

Phase 0 anti-patterns:

  • ❌ Starting to create anything before scope is locked with user
  • ❌ Ignoring existing file conventions and imposing new ones
  • ❌ Skipping search_design_system before planning component creation

Phase 1 anti-patterns:

  • ❌ Using ALL_SCOPES on any variable
  • ❌ Duplicating raw values in semantic layer instead of aliasing
  • ❌ Not setting code syntax (breaks Dev Mode and round-tripping)
  • ❌ Creating component tokens before agreeing on token taxonomy

Phase 2 anti-patterns:

  • ❌ Skipping the cover page or foundations docs
  • ❌ Putting multiple unrelated components on one page

Phase 3 anti-patterns:

  • ❌ Creating components before foundations exist
  • ❌ Hardcoding any fill/stroke/spacing/radius value in a component
  • ❌ Creating a variant per icon (use INSTANCE_SWAP instead)
  • ❌ Not positioning variants after combineAsVariants (they all stack at 0,0)
  • ❌ Building variant matrix > 30 without splitting (variant explosion)
  • ❌ Importing remote components then immediately detaching them

General anti-patterns:

  • ❌ Retrying a failed script without understanding the error first
  • ❌ Using name-prefix matching for cleanup (deletes user-owned nodes)
  • ❌ Building on unvalidated work from the previous step
  • ❌ Skipping user checkpoints to "save time"
  • ❌ Parallelizing use_figma calls (always sequential)
  • ❌ Guessing/hallucinating node IDs from memory (always read from state ledger)
  • ❌ Writing massive inline scripts instead of using the provided helper scripts
  • ❌ Starting Phase 3 because the user said "build the button" without completing Phases 0-2

10. Reference Docs

Load on demand — each reference is authoritative for its phase:

Use your file reading tool to read these docs when needed. Do not assume their contents from the filename.

DocPhaseRequired / OptionalLoad when
discovery-phase.md0RequiredStarting any build — codebase analysis + Figma inspection
token-creation.md1RequiredCreating variables, collections, modes, styles
documentation-creation.md2RequiredCreating cover page, foundations docs, swatches
component-creation.md3RequiredCreating any component or variant
code-connect-setup.md3–4RequiredSetting up Code Connect or variable code syntax
naming-conventions.mdAnyOptionalNaming anything — variables, pages, variants, styles
error-recovery.mdAnyRequired on errorScript fails, multi-step workflow recovery, cleanup of abandoned workflow state

11. Scripts

Reusable Plugin API helper functions. Embed in use_figma calls:

ScriptPurpose
inspectFileStructure.jsDiscover all pages, components, variables, styles; returns full inventory
createVariableCollection.jsCreate a named collection with modes; returns {collectionId, modeIds}
createSemanticTokens.jsCreate aliased semantic variables from a token map
createComponentWithVariants.jsBuild a component set from a variant matrix; handles grid layout
bindVariablesToComponent.jsBind design tokens to all component visual properties
createDocumentationPage.jsCreate a page with title + description + section structure
validateCreation.jsVerify created nodes match expected counts, names, structure
cleanupOrphans.jsRemove orphaned nodes by name convention or state ledger IDs
rehydrateState.jsScan file for all pages, components, variables by name; returns full {key → nodeId} map for state reconstruction

常见问题

能不能一次调用就把整套设计系统建完?
不能。文档明确说明这不是一次性任务,单次调用会产出破损或无法恢复的结果。一次构建通常需要 20–100+ 次 use_figma 调用,阶段之间必须经过用户确认。
还需要安装别的技能吗?
需要。每次调用 use_figma 都必须同时加载 figma-use 技能,它提供 Plugin API 的语法规则;本技能只提供设计系统领域知识和流程编排。
代码和 Figma 里的定义不一致时怎么处理?
会在确认点把两个版本都展示出来,由用户决定以哪边为准。被否决的工作不会在此基础上继续搭建。
构建中途中断了怎么接着做?
状态会写到 /tmp/dsb-state-{RUN_ID}.json,并在每轮开始时重新读取。恢复时先跑一次只读扫描,按名称重建页面、组件、变量和样式的 key 到 ID 映射,再继续未完成的步骤。

相关技能

以 AI 机器人身份加入视频会议,提供语音、虚拟形象与屏幕共享四种模式。

作者 johnpatternai22 次安装8 星标

docx

官方

用脚本和 XML 创建、编辑、读取并批注 Word 的 .docx 与 .dotx 文件。

作者 Anthropic197.6k 星标

pdf

官方

用 Python 和命令行完成 PDF 的读取、提取、合并、拆分、旋转、水印、生成、加密与 OCR。

作者 Anthropic197.6k 星标

搭建、重构和排查由 MCP 服务器加 widget UI 组成的 ChatGPT Apps SDK 应用。

作者 OpenAI28.8k 星标

用已发布的设计系统组件、变量和样式,在 Figma 中搭建或更新整页界面。

作者 OpenAI28.8k 星标

OpenAI 的更多技能

浏览全部技能

搭建、重构和排查由 MCP 服务器加 widget UI 组成的 ChatGPT Apps SDK 应用。

作者 OpenAI28.8k 星标

用已发布的设计系统组件、变量和样式,在 Figma 中搭建或更新整页界面。

作者 OpenAI28.8k 星标

figma-use

官方

在 Figma 文件里通过 Plugin API 执行 JavaScript,并给出避免脚本报错的规则与参考资料。

作者 OpenAI28.8k 星标

hatch-pet

官方

把概念、品牌线索或参考图做成可校验的 8x9 动画 Codex 宠物图集,含 QA 图和 pet.json 打包。

作者 OpenAI28.8k 星标

imagegen

官方

为项目生成或编辑位图素材,从主视觉到透明背景抠图都能产出。

作者 OpenAI28.8k 星标

基于 OpenAI 官方开发者文档给出可引用的答案,并覆盖 Codex 自身用法与模型迁移指导。

作者 OpenAI28.8k 星标