Figma

Figma Integration Skill

Figma MCP integration patterns for klara-theme design-to-code workflows.

When Active

• Working in libs/klara-theme/
• Using Figma MCP tools (get_design_context, get_variable_defs, etc.)
• Documenting components from Figma designs
• Mapping design tokens between Figma and klara-theme
• Validating implementations against Figma designs

MCP Tool Reference

Tool Usage Pattern

1. get_design_context(nodeId)  → design representation
2. get_variable_defs(nodeId)   → token extraction
3. get_screenshot(nodeId)      → visual reference
4. Convert to klara-theme patterns
5. Validate against screenshot

Golden Rules

1. Be explicit — Specify exactly which tools and nodes you want. Do not ask vaguely for "tokens."
2. Never implement from get_metadata alone — Always follow with get_design_context for the nodes you are building.
3. Treat get_design_context output as a representation — It returns React+Tailwind; you must convert to klara-theme patterns (forwardRef, theme-ui-label, token mapping).
4. Avoid large selections — Work in small chunks. If truncated, use get_metadata to identify sub-nodes, then fetch each with get_design_context.
5. Prefer reuse — Check src/lib/components/ before creating anything new.
6. Always validate visually — Call get_screenshot and compare against your implementation.

Token Mapping

klara-theme uses a 3-layer token system:

Figma Variable → CSS Variable Mapping

Figma variables map to klara-theme CSS variables via theme-constants.ts:

// Figma: "color/background/primary" → CSS: "--klara-bg-primary"
// Figma: "spacing/md" → CSS: "--klara-spacing-md"

When extracting tokens from get_variable_defs:

1. Identify the Figma variable name
2. Look up the corresponding CSS variable in theme-constants.ts
3. Map to the correct token layer

Anti-Truncation Strategy

Large Figma selections may truncate. Handle with:

1. Work in small chunks — Select individual components, not entire frames
2. Fallback pattern:
   • If get_design_context truncates → call get_metadata for structure
   • Extract child node IDs from metadata
   • Call get_design_context on each child separately
3. Progressive extraction — Start with the parent, then drill into children

Visual Validation

After implementation, always validate:

1. Call get_screenshot(nodeId) for the Figma design
2. Compare against your implementation visually
3. Check for:
   • Layout alignment
   • Spacing consistency
   • Color accuracy
   • Typography matching
   • State variations (hover, focus, disabled)

Drift Categories

If differences found, categorize as:

• Intentional: Design evolved, implementation is correct
• Bug: Implementation error, needs fix
• Enhancement: Design improvement not yet implemented

Aspect Files

Related Resources

• klara-theme docs: libs/klara-theme/CLAUDE.md
• ui-lib-dev skill: ui-lib-dev — Component pipeline (plan, implement, audit, fix, document)
• Schemas: libs/klara-theme/figma-data/schema/
  • component-data.schema.json — Figma component data structure
  • component-mapping.schema.json — Prop mapping structure
• Manifest: libs/klara-theme/figma-data/manifest.json — Component tracking

Output Formats

Component Data (.figma.json)

{
  "componentKey": "button",
  "componentSetNodeId": "1:2592",
  "variants": [...],
  "tokens": {...},
  "extractedAt": "2025-01-15T10:00:00Z"
}

Prop Mapping (.mapping.json)

{
  "componentKey": "button",
  "props": {
    "variant": {
      "figmaProperty": "Type",
      "values": { "primary": "Primary", "secondary": "Secondary" }
    }
  }
}