**必須の前提条件** — すべての `use_figma` ツール呼び出しの前に、このスキルを必ずロードしてください。`use_figma` を直接呼び出さないでください。これをスキップすると、一般的でデバッグが難しいエラーが発生します。ユーザーが書き込み操作や、Figma ファイルコンテキスト内で JavaScript 実行を必要とするユニークな読み取り操作（ノードの作成/編集/削除、変数やトークンのセットアップ、コンポーネントとバリアントの構築、オートレイアウトや塗りの変更、プロパティへの変数のバインド、プログラムによるファイル構造の検査など）を行いたい場合にトリガーします。
このスキルは、Figma API の `use_figma` ツールを使用するための必須の前提条件です。`use_figma` を呼び出す前に必ずこのスキルをロードする必要があります。これを怠ると、ノードの作成/編集/削除、変数やトークンの設定、コンポーネントやバリアントの構築、オートレイアウトや塗りの変更、プロパティへの変数のバインド、ファイル構造のプログラムによる検査など、Figma ファイルコンテキスト内での書き込み操作や JavaScript 実行を必要とするユニークな読み取り操作で、一般的でデバッグが難しいエラーが発生します。このスキルは、AI エージェント（Claude Code など）と Figma 設計環境の間のギャップを埋め、信頼性が高く一貫した API の使用を保証するために設計されています。これにより、正しいコンテキストと設定が適用され、不必要な障害を防ぎます。すべての Figma 操作にとって重要な安全策として機能します。
npx skills add https://github.com/figma/mcp-server-guide/tree/main/skills/figma-use必須の前提条件 — すべての use_figma ツール呼び出しの前に、このスキルを必ずロードしてください。use_figma を直接呼び出さないでください。これをスキップすると、一般的でデバッグが難しいエラーが発生します。ユーザーが書き込み操作や、Figma ファイルコンテキスト内で JavaScript 実行を必要とするユニークな読み取り操作（ノードの作成/編集/削除、変数やトークンのセットアップ、コンポーネントとバリアントの構築、オートレイアウトや塗りの変更、プロパティへの変数のバインド、プログラムによるファイル構造の検査など）を行いたい場合にトリガーします。
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.
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. Also use when the user asks to create or generate any component in Figma — even a single one — since components require proper variable foundations, variant states, and design token bindings to be production-quality. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.
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`.
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".