figma

原文涵盖的主题

• Figma MCP
• Figma MCP Integration Rules
• Required flow (do not skip)
• Implementation rules
• Asset handling
• Link-based prompting
• References

Use the Figma MCP server for Figma-driven implementation. For setup and debugging details (env vars, config, verification), see references/figma-mcp-config.md. These rules define how to translate Figma inputs into code for this project and must be followed for every Figma-driven change. 1. Run getdesigncontext first to fetch the structured representation for the exact node(s). 2. If the response is too large or truncated, run getmetadata to get the high-level node map and then re-fetch only the required node(s) with getdesigncontext. 3. Run getscreenshot for a visual reference of the node variant being implemented. 4. Only after you have both getdesigncontext and getscreenshot, download any assets needed and start implementation. 5. Translate the output (usually React + Tailwind) into this project's conventions, styles and framework. Reuse the project's color tokens, components, and typography wherever possible. 6. Validate against Figma for 1:1 look and behavior before marking complete. Treat the Figma MCP output (React + Tailwind) as a representation of design and behavior, not as final code style. Replace Tailwind utility classes with the project's preferred utilities/design-sys

这里只展示节选，请以完整原文和当前要求为准。