What problem does it solve?
Translating Figma mockups into dashboard code by hand often produces inconsistent UI: wrong components, arbitrary spacing values, hardcoded colors, and pages that don't match the surrounding codebase. This Skill reads a Figma design via the Figma MCP and generates React code for the Mercur admin or vendor dashboard that follows the project's design-system conventions exactly.
Core Features & Use Cases
- Design-to-code conversion: Reads Figma nodes via
get_screenshot and get_metadata, then maps each region to the correct @medusajs/ui or @mercurjs/dashboard-shared primitive with the right variant and props.
- Convention enforcement through references: Ships component inventory, spacing/token scale, and structural pattern references covering page archetypes (list, detail, create, edit), section shells,
RouteFocusModal/RouteDrawer hosts, Form.Field forms, DataTable, i18n, and data-testid rules.
- Use Case: A developer shares a Figma URL for a new vendor payout settings screen. The Skill reads the screenshot, identifies it as an edit archetype, and generates a
RouteDrawer page using Form.Field inputs, Medusa UI tokens, translation keys, and matching spacing—then verifies with bun run lint and bun run build.
Quick Start
Share a Figma frame URL and ask the assistant to convert this design into a Mercur admin or vendor dashboard page following the project design system.