figma-code-connect은(는) 무엇을 하나요?
Figma Code Connect 템플릿 파일을 생성하고 유지 관리하여 Figma 컴포넌트를 코드 스니펫에 매핑합니다. 사용자가 Code Connect, Figma 컴포넌트 매핑, 설계-코드 변환에 대해 언급하거나 .figma.ts 또는 .figma.js 파일을 생성/업데이트하도록 요청할 때 사용합니다.
Figma Code Connect 템플릿 파일을 생성하고 유지 관리하여 Figma 컴포넌트를 코드 스니펫에 매핑합니다.
이 스킬은 Figma Code Connect를 위한 템플릿 파일(.figma.ts 또는 .figma.js)을 생성하고 유지 관리하는 작업을 자동화합니다. 디자이너와 개발자 간의 간극을 줄여주며, Figma 컴포넌트를 실제 코드 구현과 직접 연결하여 설계-코드 변환(design-to-code translation) 과정을 간소화합니다. 주로 프론트엔드 개발 환경에서 사용되며, React, Vue 등 다양한 UI 라이브러리와 호환됩니다. 사용자가 Code Connect, Figma 컴포넌트 매핑, 또는 .figma 파일 생성을 요청할 때 이 스킬이 활성화되어, 일관된 인터페이스로 코드 스니펫을 정의하고 업데이트할 수 있도록 지원합니다.
npx skills add https://github.com/figma/mcp-server-guide/tree/main/skills/figma-code-connectFigma Code Connect 템플릿 파일을 생성하고 유지 관리하여 Figma 컴포넌트를 코드 스니펫에 매핑합니다. 사용자가 Code Connect, Figma 컴포넌트 매핑, 설계-코드 변환에 대해 언급하거나 .figma.ts 또는 .figma.js 파일을 생성/업데이트하도록 요청할 때 사용합니다.
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.
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`.
**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".