---
id: figma-handoff
kind: topic
title: "Figma files an agent can read"
atlas_url: https://designsystems.fly.dev/nodes/figma-handoff.md
---

# Figma files an agent can read

Naming, variables, components and auto layout treated as the instructions a machine follows rather than as documentation hygiene.

## Edges

- <- about <- 650+ Google Material 3 Button Variants + Microsoft Fluent 2 Mappings in One Figma Component, Agentic AI, design systems and Figma, Analysis of Variants, Beyond Design Tokens: Building an AI-Ready Figma Handoff, Build Scalable UI in Figma & AI, Building the Next Generation of a Design System With In-House Designers, Claude to Figma: keeping AI-generated UI bound to your design system, Components as Data, Design system contracts: the component lives in neither Figma nor code, Encoding Intent, Figma Handoff to AI Agents, Figma MCP: turning Claude-generated UI into a component library, Full validation loop in a contract-based agentic design system, Learning Agentic Design Systems, Open Platforms, Opinionated Tools, and the Skills Between Them, Spec-Driven UI Component Development, Vibe coding with zero drift: from Figma to Storybook to Production, Why Design System Governance Belongs in Code
- <- focus <- Christine Vallaure, Davy Fung, Dei, Jan Six, Josef Richter, Laura Fehre, Michael Schultz, Nathan Curtis, Phong Trần, Robin Di Capua, Shuaiqi Sun, Surendar Selvaraj, TJ Pitre
- <- ships <- PatternFly

## Sources

- https://christinevallaure.substack.com/p/agentic-ai-design-systems-and-figma