**必須の前提条件** — `create_new_file` ツールを呼び出す前に必ずこのスキルを呼び出してください。ユーザーが新しいFigmaファイル（デザイン、FigJam、スライド）を作成したいとき、または `use_figma` を呼び出す前に新しいファイルが必要なときにトリガーします。使用法 — `/figma-create-new-file [editorType] [fileName]` （例: `/figma-create-new-file figjam My Whiteboard`、`/figma-create-new-file slides Q3 Review`）。
このスキルは、Figma の `create_new_file` ツールを呼び出すための**必須の前提条件**です。ユーザーが新しいFigmaファイル（デザイン、FigJam、スライド）を作成したいとき、またはAIエージェントが `use_figma` を呼び出す前に新しいファイルが必要なときにトリガーします。 このスキルを常に最初に読み込むことで、`create_new_file` ツールが確実に使えるようになり、エラーや意図しない動作（例：存在しないファイル上での操作）を防ぎます。スキルは `/figma-create-new-file [editorType] [fileName]` という書式で引数を受け取り、例えば `/figma-create-new-file figjam My Whiteboard` のように使います。 対応エディタは `figma`（標準デザイン）、`figjam`（FigJamホワイトボード）、`slides`（Figma Slides）です。ファイル名は自由に指定でき、空白を含む場合は引用符で囲む必要はありません。 このスキルはClaude Code、Cursor、CodexなどのAIエージェント向けに設計されており、開発者はワークフローに統合することで、新しい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、またはスライドファイル）を作成したいとき、または 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".