コードベースからFigma上にプロフェッショナルなデザインシステムを構築・更新します。変数・トークンの作成、コンポーネントライブラリの構築、単一コンポーネントの生成（バリアントセットや変数バインディングを含む）、テーマ設定（ライト/ダークモード）など、デザインシステムに関連するあらゆる作業を指示します。
このスキルは、コードベースを基にFigma上でプロフェッショナルグレードのデザインシステムを構築・更新するためのものです。具体的には、デザイントークン（変数）の作成、コンポーネントライブラリの構築、バリアントセットと変数バインディングを備えた個々のコンポーネントの生成、テーマ設定（ライト/ダークモード）の実現、ファンデーションの文書化、コードとFigma間のギャップ調整をサポートします。このスキルは「何を」「どの順序で」構築するかを教えるものであり、Figma Plugin APIの呼び出し方（HOW）を教える`figma-use`スキルを補完します。両方のスキルを一緒に読み込むことで、設計システムの効率的かつ高品質な開発が可能になります。単一のコンポーネントでも、プロダクション品質にするためには適切な変数基盤、バリアント状態、デザイントークンバインディングが必要であると強調しており、それらの構築手順を網羅的にガイドします。
npx skills add https://github.com/figma/mcp-server-guide/tree/main/skills/figma-generate-libraryコードベースからFigma上にプロフェッショナルなデザインシステムを構築・更新します。ユーザーが変数/トークンを作成したい、コンポーネントライブラリを構築したい、適切なバリアントセットと変数バインディングを持つ個々のコンポーネントを作成したい、テーマ設定（ライト/ダークモード）を設定したい、ファンデーションを文書化したい、またはコードとFigma間のギャップを調整したい場合に使用します。また、ユーザーがFigma上で任意のコンポーネントを作成または生成するよう依頼した場合（単一のコンポーネントであっても）、プロダクション品質を確保するためには適切な変数基盤、バリアント状態、デザイントークンバインディングが必要であるため、このスキルを使用します。このスキルは 何を どの順序で構築するかを教えます — これは、Plugin APIを どのように 呼び出すかを教える figma-use スキルを補完します。両方のスキルを一緒に読み込む必要があります。
This repo contains 9 individual skills — each has its own dedicated page.
Connects Figma design components to code components using Code Connect. Use when user says "code connect", "connect this component to code", "connect Figma to code", "map this component", "link component to code", "create code connect mapping", "add code connect", "connect design to code", or wants to establish mappings between Figma designs and code implementations. Requires Figma MCP server connection.
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `create_new_file` tool call. NEVER call `create_new_file` directly without loading this skill first. Trigger whenever the user wants a new blank Figma file — a new design, FigJam, or Slides file — or when you need a fresh file before calling `use_figma`. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review)
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
Translates Figma designs into production-ready code with 1:1 visual fidelity. Use when implementing UI from Figma files, when user mentions "implement design", "generate code", "implement component", "build Figma design", provides Figma URLs, or asks to build components matching Figma specs. Requires Figma MCP server connection.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".