**強制性先決條件** – 在每次呼叫 `create_new_file` 工具之前，你必須先載入此技能。切勿在未載入此技能的情況下直接呼叫 `create_new_file`。當使用者想要建立新的空白 Figma 檔案（新的設計、FigJam 或 Slides 檔案），或在你需要先建立新檔案才能呼叫 `use_figma` 時觸發。使用方式 – /figma-create-new-file [editorType] [fileName]（例如 /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review）
這是一個強制性的必要技能，必須在任何 `create_new_file` 工具呼叫之前載入。其主要目的是確保在建立新的空白 Figma 檔案（包括 Figma 設計、FigJam 白板或 Slides 簡報檔案）時，遵循正確的程序，並避免直接呼叫該工具而未經流程檢查。這個技能支援多種編輯器類型，如 `figma`、`figjam` 和 `slides`，並允許指定自訂的檔案名稱。當使用者需要一個全新的檔案來開始設計或協作，或者需要在後續呼叫 `use_figma` 之前準備好一個檔案時，都應使用此技能。它對於維持工作流程的一致性與正確性至關重要，且通常作為一系列 Figma 相關操作的第一步。
npx skills add https://github.com/figma/mcp-server-guide/tree/main/skills/figma-create-new-file強制性先決條件 – 在每次呼叫 create_new_file 工具之前，你必須先載入此技能。切勿在未載入此技能的情況下直接呼叫 create_new_file。當使用者想要建立新的空白 Figma 檔案（新的設計、FigJam 或 Slides 檔案），或在你需要先建立新檔案才能呼叫 use_figma 時觸發。使用方式 – /figma-create-new-file [editorType] [fileName]（例如 /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review）
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.
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`.
**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".