designfigma-to-code

name: design.figma-to-code description: Implement a Figma design using shadcn/ui components. Use when converting Figma URLs to React code. argument-hint: '[figma-url]' allowed-tools: - mcp__figma-remote-mcp__get_design_context - mcp__figma-remote-mcp__get_screenshot - mcp__figma-remote-mcp__get_variable_defs - mcp__figma-remote-mcp__get_metadata - Read - Write - Edit - Bash - Glob - Grep

Figma to Code Implementation

Implement the Figma design at $ARGUMENTS using shadcn/ui components.

Note: All shadcn/ui components are already installed and available at apps/web/src/components/ui/. Import them directly (e.g., import { Button } from '@/components/ui/button'). Avoid other components.

Step 1: Parse Figma URL

Extract from URL https://figma.com/design/:fileKey/:fileName?node-id=:nodeId:

• fileKey: The file identifier
• nodeId: Convert 123-456 to 123:456 format

Step 2: Fetch Design Context

mcp__figma-remote-mcp__get_design_context(
  fileKey: "<fileKey>",
  nodeId: "<nodeId>",
  clientLanguages: "typescript",
  clientFrameworks: "react,nextjs"
)

Also get screenshot and metadata:

mcp__figma-remote-mcp__get_screenshot(fileKey, nodeId)
mcp__figma-remote-mcp__get_metadata(fileKey, nodeId)

Step 3: Analyze Component Types (CRITICAL)

Check data-name attributes in Figma output - don't assume from visuals!

Red Flags - Verify Before Coding:

• Multiple similar elements in a row (could be Tabs, not Buttons)
• Elements sharing a container background (grouped component)
• Active/inactive states (selection component)

Step 4: Extract Variants & Props

For shadcn Figma libraries, extract props from attributes only:

What to LOOK AT:

• CSS variable names: --general/primary, --general/secondary
• data-name for component type
• Text: Use get_variable_defs — map Figma text styles (e.g. heading 2, paragraph/regular) to Typography variants (see reference.md)

What to IGNORE:

• Pixel values in generated code (px, py, gap, rounded)
• These are internal implementation details

Priority Order:

1. data-name with variant (e.g., "Button/Secondary/sm")
2. CSS variable names → variant (--general/secondary → variant="secondary")
3. Omitted = default

Typography: NEVER use hardcoded Tailwind for text. Always use <Typography variant="…" /> from @/components/ui/typography. Map Figma variable names (e.g. heading 2, paragraph-bold) to Typography variants (e.g. h2, paragraph-bold).

Step 5: Build the Component

import { Button } from '@/components/ui/button'
import { Card, CardContent } from '@/components/ui/card'

type MyComponentProps = {
  // typed props
}

export function MyComponent({ ...props }: MyComponentProps) {
  return (
    // Implementation
  )
}

Styling Guidelines:

DO:

• Use shadcn variants (variant="outline", size="sm")
• Use Typography with variants for all text — never raw Tailwind for typography
• Use Tailwind for layout only: flex, grid, gap-*, p-*
• Match layout ratios from Figma exactly (e.g., grid-cols-2 for 50/50 split, or specific column ratios)
• Prefer using wrapper classes for layout, to use pure shadcn components without added tailwind classes
• Use CSS variables from shadcn for colors

DON'T:

• Add custom colors (bg-blue-500)
• Override shadcn styles
• Hardcode pixel values
• Wrap icons in divs inside buttons (icons should be direct children)
• Hardcode Tailwind for text

Step 6: Create Storybook Stories

Place story files next to the component they document (e.g., MyComponent.stories.tsx next to MyComponent.tsx).

Simple Component Stories

For shadcn/ui components and simple UI components that don't need API mocking:

import type { Meta, StoryObj } from '@storybook/react'
import { MyComponent } from './MyComponent'

const meta = {
  title: 'Components/MyComponent',
  component: MyComponent,
} satisfies Meta<typeof MyComponent>

export default meta
type Story = StoryObj<typeof meta>

export const Default: Story = {
  args: {
    // component props
  },
}

Story Guidelines

• Use descriptive story names (Default, WithError, Loading, etc.)
• Include all important component states and variations
• Extract and apply the Figma frame's background color to the story wrapper for visual consistency, ideally using tailwind classes
• For screens with subcomponents, create stories for each:

  MyScreen/
  ├── MyScreen.stories.tsx
  ├── HeaderCard.stories.tsx
  └── DataTable.stories.tsx
  

Note: For pages/widgets that need Redux state and API mocking, use createMockStory from @/stories/mocks (see AGENTS.md for details).

Step 7: Verify

yarn workspace @safe-global/web type-check
yarn workspace @safe-global/web storybook

Project Notes

• Components Path: apps/web/src/components/ui/
• Utility Path: apps/web/src/utils/cn.ts
• Icon Library: lucide-react

See reference.md for detailed component mappings and patterns.