---
id: "prereq-figma-role"
type: "prerequisite"
source_timestamps: ["00:09:58"]
tags: ["design-tools", "context"]
related: ["concept-the-production-middle", "claim-figma-survival", "entity-product-figma"]
reason: "Familiarity with Figma's primitives (components, variables, modes) is required to understand why it will survive in the 'production middle'."
sources: ["s05-claude-design-30min"]
sourceVaultSlug: "s05-claude-design-30min"
originDay: 5
---
# Prerequisite — Figma's Role in Product Design

## What You Need to Know
[[entity-product-figma-d5]] is **not just a drawing tool**. It is a complex system for managing:

- **Components** — reusable UI building blocks.
- **Variables** — design tokens (colors, spacing, typography) referenced across files.
- **Modes** — variants for theming (light/dark, brand variants, accessibility profiles).
- **Auto-layout, constraints, and shared libraries** at enterprise scale.

These are **proprietary primitives**, not open-web standards.

## Why This Matters
The contrarian point in [[contrarian-figma-not-dead]] and [[claim-figma-survival]] depends on understanding that Figma's moat is not the canvas — it's the design-system management layer that lives on top of the canvas. LLMs trained on the open web have no exposure to these proprietary file structures, which is why [[concept-the-production-middle]] is defensible territory for Figma even as zero-to-one prototyping shifts to AI.
