为自然搜索排名提供站点审计、内容撰写与竞品分析。
设计与多媒体
figma-implement-design
试用把 Figma 画板转成仓库里的代码,视觉上与设计稿逐像素对齐。
它能做什么
一套七步流程:从 Figma 链接中解析 fileKey 和 nodeId(使用 figma-desktop MCP 时也可直接取当前选中节点),通过 Figma MCP server 拉取结构化设计上下文和截图,下载返回的图片与图标资源,再把输出改写成项目自己的框架、组件和设计 token。最后按清单逐项校验布局、字体、颜色、交互态、响应式行为、资源渲染和无障碍。超出范围的请求(在 Figma 里改节点、生成整页设计稿、Code Connect 映射、编写 agent 规则文件)会转交给对应的兄弟技能。
什么时候用它
- 按 Figma 节点链接实现单个组件
- 根据 Figma 画板搭建完整仪表盘布局
- 把 Figma 的颜色和间距值映射到现有设计系统
- 上线前拿实现结果与 Figma 截图逐项比对
技能文档
Implement Design
Overview
This skill provides a structured workflow for translating Figma designs into production-ready code with pixel-perfect accuracy. It ensures consistent integration with the Figma MCP server, proper use of design tokens, and 1:1 visual parity with designs.
Skill Boundaries
- Use this skill when the deliverable is code in the user's repository.
- If the user asks to create/edit/delete nodes inside Figma itself, switch to figma-use.
- If the user asks to build or update a full-page screen in Figma from code or a description, switch to figma-generate-design.
- If the user asks only for Code Connect mappings, switch to figma-code-connect-components.
- If the user asks to author reusable agent rules (
CLAUDE.md/AGENTS.md), switch to figma-create-design-system-rules.
Prerequisites
- Figma MCP server must be connected and accessible
- User must provide a Figma URL in the format:
https://figma.com/design/:fileKey/:fileName?node-id=1-2:fileKeyis the file key1-2is the node ID (the specific component or frame to implement)
- OR when using
figma-desktopMCP: User can select a node directly in the Figma desktop app (no URL required) - Project should have an established design system or component library (preferred)
Required Workflow
Follow these steps in order. Do not skip steps.
Step 1: Get Node ID
Option A: Parse from Figma URL
When the user provides a Figma URL, extract the file key and node ID to pass as arguments to MCP tools.
URL format: https://figma.com/design/:fileKey/:fileName?node-id=1-2
Extract:
- File key:
:fileKey(the segment after/design/) - Node ID:
1-2(the value of thenode-idquery parameter)
Note: When using the local desktop MCP (figma-desktop), fileKey is not passed as a parameter to tool calls. The server automatically uses the currently open file, so only nodeId is needed.
Example:
- URL:
https://figma.com/design/kL9xQn2VwM8pYrTb4ZcHjF/DesignSystem?node-id=42-15 - File key:
kL9xQn2VwM8pYrTb4ZcHjF - Node ID:
42-15
Option B: Use Current Selection from Figma Desktop App (figma-desktop MCP only)
When using the figma-desktop MCP and the user has NOT provided a URL, the tools automatically use the currently selected node from the open Figma file in the desktop app.
Note: Selection-based prompting only works with the figma-desktop MCP server. The remote server requires a link to a frame or layer to extract context. The user must have the Figma desktop app open with a node selected.
Step 2: Fetch Design Context
Run get_design_context with the extracted file key and node ID.
get_design_context(fileKey=":fileKey", nodeId="1-2")
This provides the structured data including:
- Layout properties (Auto Layout, constraints, sizing)
- Typography specifications
- Color values and design tokens
- Component structure and variants
- Spacing and padding values
If the response is too large or truncated:
- Run
get_metadata(fileKey=":fileKey", nodeId="1-2")to get the high-level node map - Identify the specific child nodes needed from the metadata
- Fetch individual child nodes with
get_design_context(fileKey=":fileKey", nodeId=":childNodeId")
Step 3: Capture Visual Reference
Run get_screenshot with the same file key and node ID for a visual reference.
get_screenshot(fileKey=":fileKey", nodeId="1-2")
This screenshot serves as the source of truth for visual validation. Keep it accessible throughout implementation.
Step 4: Download Required Assets
Download any assets (images, icons, SVGs) returned by the Figma MCP server.
IMPORTANT: Follow these asset rules:
- If the Figma MCP server returns a
localhostsource for an image or SVG, use that source directly - DO NOT import or add new icon packages - all assets should come from the Figma payload
- DO NOT use or create placeholders if a
localhostsource is provided - Assets are served through the Figma MCP server's built-in assets endpoint
Step 5: Translate to Project Conventions
Translate the Figma output into this project's framework, styles, and conventions.
Key principles:
- Treat the Figma MCP output (typically React + Tailwind) as a representation of design and behavior, not as final code style
- Replace Tailwind utility classes with the project's preferred utilities or design system tokens
- Reuse existing components (buttons, inputs, typography, icon wrappers) instead of duplicating functionality
- Use the project's color system, typography scale, and spacing tokens consistently
- Respect existing routing, state management, and data-fetch patterns
Step 6: Achieve 1:1 Visual Parity
Strive for pixel-perfect visual parity with the Figma design.
Guidelines:
- Prioritize Figma fidelity to match designs exactly
- Avoid hardcoded values - use design tokens from Figma where available
- When conflicts arise between design system tokens and Figma specs, prefer design system tokens but adjust spacing or sizes minimally to match visuals
- Follow WCAG requirements for accessibility
- Add component documentation as needed
Step 7: Validate Against Figma
Before marking complete, validate the final UI against the Figma screenshot.
Validation checklist:
- Layout matches (spacing, alignment, sizing)
- Typography matches (font, size, weight, line height)
- Colors match exactly
- Interactive states work as designed (hover, active, disabled)
- Responsive behavior follows Figma constraints
- Assets render correctly
- Accessibility standards met
Implementation Rules
Component Organization
- Place UI components in the project's designated design system directory
- Follow the project's component naming conventions
- Avoid inline styles unless truly necessary for dynamic values
Design System Integration
- ALWAYS use components from the project's design system when possible
- Map Figma design tokens to project design tokens
- When a matching component exists, extend it rather than creating a new one
- Document any new components added to the design system
Code Quality
- Avoid hardcoded values - extract to constants or design tokens
- Keep components composable and reusable
- Add TypeScript types for component props
- Include JSDoc comments for exported components
Examples
Example 1: Implementing a Button Component
User says: "Implement this Figma button component: https://figma.com/design/kL9xQn2VwM8pYrTb4ZcHjF/DesignSystem?node-id=42-15"
Actions:
- Parse URL to extract fileKey=
kL9xQn2VwM8pYrTb4ZcHjFand nodeId=42-15 - Run
get_design_context(fileKey="kL9xQn2VwM8pYrTb4ZcHjF", nodeId="42-15") - Run
get_screenshot(fileKey="kL9xQn2VwM8pYrTb4ZcHjF", nodeId="42-15")for visual reference - Download any button icons from the assets endpoint
- Check if project has existing button component
- If yes, extend it with new variant; if no, create new component using project conventions
- Map Figma colors to project design tokens (e.g.,
primary-500,primary-hover) - Validate against screenshot for padding, border radius, typography
Result: Button component matching Figma design, integrated with project design system.
Example 2: Building a Dashboard Layout
User says: "Build this dashboard: https://figma.com/design/pR8mNv5KqXzGwY2JtCfL4D/Dashboard?node-id=10-5"
Actions:
- Parse URL to extract fileKey=
pR8mNv5KqXzGwY2JtCfL4Dand nodeId=10-5 - Run
get_metadata(fileKey="pR8mNv5KqXzGwY2JtCfL4D", nodeId="10-5")to understand the page structure - Identify main sections from metadata (header, sidebar, content area, cards) and their child node IDs
- Run
get_design_context(fileKey="pR8mNv5KqXzGwY2JtCfL4D", nodeId=":childNodeId")for each major section - Run
get_screenshot(fileKey="pR8mNv5KqXzGwY2JtCfL4D", nodeId="10-5")for the full page - Download all assets (logos, icons, charts)
- Build layout using project's layout primitives
- Implement each section using existing components where possible
- Validate responsive behavior against Figma constraints
Result: Complete dashboard matching Figma design with responsive layout.
Best Practices
Always Start with Context
Never implement based on assumptions. Always fetch get_design_context and get_screenshot first.
Incremental Validation
Validate frequently during implementation, not just at the end. This catches issues early.
Document Deviations
If you must deviate from the Figma design (e.g., for accessibility or technical constraints), document why in code comments.
Reuse Over Recreation
Always check for existing components before creating new ones. Consistency across the codebase is more important than exact Figma replication.
Design System First
When in doubt, prefer the project's design system patterns over literal Figma translation.
Common Issues and Solutions
Issue: Figma output is truncated
Cause: The design is too complex or has too many nested layers to return in a single response.
Solution: Use get_metadata to get the node structure, then fetch specific nodes individually with get_design_context.
Issue: Design doesn't match after implementation
Cause: Visual discrepancies between the implemented code and the original Figma design. Solution: Compare side-by-side with the screenshot from Step 3. Check spacing, colors, and typography values in the design context data.
Issue: Assets not loading
Cause: The Figma MCP server's assets endpoint is not accessible or the URLs are being modified.
Solution: Verify the Figma MCP server's assets endpoint is accessible. The server serves assets at localhost URLs. Use these directly without modification.
Issue: Design token values differ from Figma
Cause: The project's design system tokens have different values than those specified in the Figma design. Solution: When project tokens differ from Figma values, prefer project tokens for consistency but adjust spacing/sizing to maintain visual fidelity.
Understanding Design Implementation
The Figma implementation workflow establishes a reliable process for translating designs to code:
For designers: Confidence that implementations will match their designs with pixel-perfect accuracy. For developers: A structured approach that eliminates guesswork and reduces back-and-forth revisions. For teams: Consistent, high-quality implementations that maintain design system integrity.
By following this workflow, you ensure that every Figma design is implemented with the same level of care and attention to detail.
Additional Resources
常见问题
- 使用前需要准备什么?
- 需要已连接可访问的 Figma MCP server,以及一个 https://figma.com/design/:fileKey/:fileName?node-id=1-2 格式的 Figma 链接;如果用 figma-desktop MCP,也可以在桌面端打开文件后直接选中节点,不必提供链接。项目最好已有设计系统或组件库。
- 它会修改 Figma 文件吗?
- 不会,它只读取。产出物是用户仓库里的代码。在 Figma 中新建、修改、删除节点,生成整页设计稿,编写 Code Connect 映射,或编写 CLAUDE.md/AGENTS.md 规则,这些需求会分别交给 figma-use、figma-generate-design、figma-code-connect-components 和 figma-create-design-system-rules 处理。
- Figma 的设计值和项目 token 冲突时怎么处理?
- 优先使用项目 token 以保持一致性,再最小幅度调整间距或尺寸来贴合视觉效果。凡是刻意偏离设计稿的地方,都要求在代码注释里写明原因。
- 设计上下文返回内容过大被截断怎么办?
- 先用 get_metadata 拿到高层节点结构,从中找出需要的子节点,再逐个用 get_design_context 单独拉取。
相关技能
以 AI 机器人身份加入视频会议,提供语音、虚拟形象与屏幕共享四种模式。
docx
官方用脚本和 XML 创建、编辑、读取 Word 文档,并支持修订与批注。
用 Python 库和命令行工具读取、编辑、合并、拆分、生成 PDF,并对扫描件做 OCR。
按文档优先流程搭建 ChatGPT Apps SDK 项目,产出 MCP 服务端、widget 界面和工具规划。
用已发布的设计系统组件、变量和样式,在 Figma 中搭建或更新完整页面,而不是手画硬编码的方块。
OpenAI 的更多技能
浏览全部技能按文档优先流程搭建 ChatGPT Apps SDK 项目,产出 MCP 服务端、widget 界面和工具规划。
用已发布的设计系统组件、变量和样式,在 Figma 中搭建或更新完整页面,而不是手画硬编码的方块。
把代码库里的设计系统按阶段搬进 Figma,每一步都先经你确认再继续。
在 Figma 文件里执行 JavaScript,通过 Plugin API 创建、修改和读取节点。
把概念、品牌线索或参考图做成可校验的 8x9 动画 Codex 宠物图集,并打包成 pet.json。
imagegen
官方在 Codex 中生成或编辑位图,从主视觉、精灵图到透明背景抠图都能处理。