'figma' 검색 결과

Figmaデザインをノード情報を活用してレビューし、該当箇所に個別コメントを投稿する。Use when (1) ユーザーがFigmaデザインのレビューを依頼した時 (2) 実装者目線、エンジニア視点でのフィードバックが必要な時 (3) デザインに対してFigma上にコメントを残したい時。padding/margin、色のコントラスト、グリッド整合性などベーシックなデザインチェックも実施。Requires Figma MCP connection and FIGMA_TOKEN environment variable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read-first Figma gateway via Figma MCP: analyze designs, implement Figma-to-code for 1–3 screens, extract design tokens, produce a Figma Evidence Packet for planning handoff, screenshot fallback. Advanced operations (Code Connect, canvas writes, design-system/library patterns) are gated references loaded only on explicit intent. Triggers: 'figma', 'design link', 'implement this design', 'design tokens', 'produce a Figma Evidence Packet'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implements SwiftUI Views from Figma designs using Figma MCP tools (figma:get_design_context, figma:get_screenshot, figma:get_variable_defs, figma:get_metadata). Splits large designs into appropriately-sized components, respects existing codebase conventions, and adds previews for each component. Use when implementing SwiftUI from Figma design URLs (e.g., figma.com/design/...), converting designs to code, or building iOS UI from Figma mockups. Do NOT call Figma MCP tools directly without reading this skill first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn feature requirements into test plans, step-by-step manual tests, regression suites for checking existing features, and reproducible bug reports. The skill also supports comparing implemented interfaces with Figma designs and documenting visual differences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan tests for a new feature
• Write manual checkout test cases
• Organize regression checks before a release

Turn Figma designs into React and TypeScript components using coderio. The workflow uses design thumbnails to guide layout, extracts component structure and data, and generates code and assets for integration into an application.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a React interface from a Figma design
• Organize component structure and input data
• Generate components while checking the design thumbnail

Turn a Figma file or design image into a working interface using the project's existing components and design tokens, its shared visual settings. Compare the implementation with the design and report differences, missing states, and parts awaiting backend connections.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implement an interface from a Figma design
• Build a screen from a supplied design image
• Reuse existing components and shared visual settings

SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design reusable Figma components, flexible layouts, and shared design systems. Get guidance on managing colors and spacing, supporting themes and screen sizes, and preparing clear specifications and assets for developers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organizing reusable components and their variants
• Building layouts that adapt to different screen widths
• Managing shared colors, spacing, and light or dark themes

Extract design tokens, text styles, and variables from a Figma design system and produce a design-tokens.json plus ready-to-use QML singletons. Use this skill whenever someone wants to pull their design system out of Figma — whether they say "export tokens from Figma", "get design tokens", "set up my design system", "read our Figma design system", "get Figma variables into QML", "pull our color palette from Figma", "import design tokens", "extract colors/typography/spacing from Figma", or similar. Trigger this skill at the start of any design-system workflow that involves a Figma source.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Translate Figma designs into production-ready SwiftUI code with 1:1 visual fidelity using the Figma MCP workflow. Trigger when the user provides Figma URLs or node IDs and wants iOS/SwiftUI implementation, asks to implement a design or component from Figma for an iOS app, or references Figma selections in the context of an Xcode/SwiftUI project. Also trigger when user asks to inspect Figma designs for iOS planning, fetch design tokens for SwiftUI, or convert Figma assets for Xcode. Requires a working Figma MCP server connection. Do NOT trigger for web/React implementations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, implement, or review native Mac interfaces using SwiftUI or AppKit. Organize panes, remove unnecessary containers, and apply restrained Liquid Glass effects while checking resizing, interaction states, and accessibility, including designs supplied through Figma.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a native Mac app interface
• Reviewing screens with too many cards and borders
• Implementing a Figma design in SwiftUI

Save and manage product references and design preferences for future Product Design work. Keep product URLs, Figma files, screenshots, brand assets, and other context available, and review or update what has already been saved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up Product Design with initial references
• Save Figma files and product URLs for future work
• Keep screenshots and brand references available

**MANDATORY prerequisite** — you MUST invoke this skill BEFORE calling the `get_design_context` Figma MCP tool. You MUST trigger this skill whenever the user wants to implement, build, port, or code up a Figma design as code. Example prompts (not exhaustive) are 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'design to code'. This skill provides critical instructions and steps to the agent on how to correctly implement Figma designs in code and must NOT be skipped.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Figma REST API / Plugin API / Widget API / Code Connect / MCP Server / Dev Mode リファレンス OAuth / PAT / Plan Access Token, files, folders, variables, VariableComposedColor, webhooks, SCIM, Dev Resources, activity-logs, library-analytics FrameNode, TextNode, ComponentNode, figma.variables, figma.codegen, figma.ui, textWrapStyle, variable fonts Widget useSyncedState, useSyncedMap, usePropertyMenu, AutoLayout Code Connect template files (.figma.ts) / legacy parser / custom parsers / register / Storybook (React / SwiftUI / Compose / HTML) MCP Code to Canvas, Write to Canvas, html_to_figma, generate_image, get_motion_context, generative plugins / shaders, Figma Weave

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a Figma design, screenshot, or written description for usability, visual hierarchy, consistency, and accessibility. Receive specific findings, explanations, and prioritized improvements, with feedback tailored to the design stage and intended users.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing an early screen design
• Checking navigation and onboarding usability
• Finding inconsistent colors, spacing, and typography

Review a Figma design, screenshot, or written description for usability, visual hierarchy, consistency, and accessibility. Receive specific findings, explanations, and prioritized improvements, with feedback tailored to the design stage and intended users.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing an early screen design
• Checking navigation and onboarding usability
• Finding inconsistent colors, spacing, and typography

Extract component metadata from a Figma design system and generate production-ready QML controls. Use this skill whenever someone wants to turn Figma components into QML files — whether they say "generate components from Figma", "create QML controls based on a design system", "convert Figma components to QML", "build the component library", "extract button/input/checkbox from Figma", or anything similar. Requires design-tokens.json and QML design system singletons to already exist (from the token extraction skill). Uses Figma MCP to inspect components one at a time and maps variants, states, sizing, and token usage to idiomatic Qt Quick Controls 2 patterns. Trigger this skill at the component generation step of any QML design-system workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bidirectional Figma skill — read designs and write back to Figma. READ: extract tokens, map Vue/Reka UI components, translate Auto Layout to Tailwind. WRITE: push components, screens, and design tokens from code to Figma. Requires /figma:figma-use skill before every use_figma call.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides context about the regelrecht Figma design system and helps with Figma-related tasks like component lookups and design comparisons. Use this skill proactively when: implementing UI components, looking up Figma node IDs, comparing code with Figma designs, downloading Figma assets, or working with design tokens. Activate automatically when user mentions Figma, design system, component styling, or asks about RR-Components.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Agentic design-to-build pipeline that turns a Figma design into a built WordPress site using the Figma MCP server (read side) and the Elementor MCP server (write side) attached as MCP Apps on an NV oOS assistant. Covers the 7-stage pipeline (Scope → Read → Plan → Tokenize → Build → Verify → Handoff), the normative stage rules (get_design_context first, tokenize before build, drafts only, never publish, Figma read-only), the build-manifest contract (schema + example in reference/build-manifest.md), the design-file contract (frame/section/variable naming in reference/design-file-contract.md), assistant wiring (figma + elementor MCP Apps, OAuth + application passwords, host allowlist), safety rules, and troubleshooting. Use when asked to build or create a site, page, or landing page from a Figma design, to wire Figma MCP or Elementor MCP for design-to-build work, to approve or produce a build manifest, or to debug a failed design-to-build run.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Translate Figma designs into production-ready application code with 1:1 visual fidelity. Use for Figma URLs, node IDs, implementation requests, or components that must match Figma specs; use the local `figma` skill for general Figma MCP context and setup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

**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)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.