Refer to the standard: @standards/frontend/FIGMA_MCP_USAGE.md Also read @packages/ui/CLAUDE.md for color token mapping and component conventions.
Steps
- Parse the Figma URL from
$ARGUMENTS— extract thefileKeyandnodeId. Convert-to:in the node ID. - Read the standards above for the available tools, adaptation rules, and color usage.
- Call
get_design_contextwith the extractednodeIdandfileKey, usingclientLanguages: "typescript,html,css"andclientFrameworks: "vue". This is always the first tool to call. - Adapt the output to the Modrinth codebase:
- Map Figma color variables to
surface-*/text-*tokens — never use Figma's aliased names directly. - Check
packages/ui/src/components/for existing components that match elements in the design (buttons, cards, modals, inputs, etc.). - Check
packages/assets/styles/variables.scssfor tokens not exposed in Figma. - Match spacing values exactly from the design.
- Map Figma color variables to
- Use
get_screenshotif you need a closer visual reference of specific nodes. - Use
get_variable_defsto verify which design tokens are applied to ambiguous elements. - Build the component as a Vue SFC using Tailwind classes and the project's existing component library.