Figma
The single source of truth for every Atelier UI component — variables, frames, and token mappings, all in one file.
The Figma file
Atelier UI is the single Figma file for the Atelier UI design system — the component library Atelier ships. It contains two pages and a variable collection that maps 1:1 to the CSS token system.
| Page | Purpose |
|---|---|
Tokens | Variable collection viewer — all 56 design tokens design tokens Named design values (colors, spacings, radii, type scales) stored as variables — so "primary color" has one canonical name instead of a hex code copy-pasted everywhere. In Atelier, tokens live as CSS custom properties like `--ui-color-primary`, and they mirror the variable names in the Figma file 1:1. across Light and Dark modes |
Components | All component frames organized by section — every variant, size, and state |
Token → CSS mapping
Every Figma variable maps directly to a CSS custom property using the same name. When AI references a token from Figma, it uses the identical name in code — no translation needed.
-
color/primary--ui-color-primary -
color/surface-raised--ui-color-surface-raised -
spacing/4--ui-spacing-4 -
spacing/6--ui-spacing-6 -
radius/md--ui-radius-md -
radius/lg--ui-radius-lg
56 variables total: 29 color, 10 spacing, 5 radius, 12 typography. Full list in libs/angular/src/styles/tokens.css.
Component frames
The Components page has one Figma Section per component. Each section shows all variants,
sizes, and states — the complete visual spec.
| Component | Figma section | What it shows |
|---|---|---|
LlmButton | P0 — Core | 3 variants × 3 sizes × 4 states (default / hover / disabled / loading) |
LlmInput | P0 — Core | 3 types × 5 states + error message |
LlmCard | P0 — Core | 3 variants × 4 padding levels |
LlmBadge | P0 — Core | 5 variants × 2 sizes + inline usage example |
| 14 more… | P1 + P2 | Select, Dialog, Tabs, Accordion, Menu, Tooltip, Alert, Checkbox, Toggle, and more |
Using Figma in the workshop
This is how Figma, Storybook, and AI work together to produce component code that matches the design exactly.
Component frames
via MCP
Writes code
Dark mode ready
Open the Figma file — find the component frame
Navigate to the Components page and locate the section for the component you want to build.
Note the variant names and states — these map directly to the component's props.
Note the token values from the variable panel
In the Figma inspect panel (right sidebar, Design tab), hover over fills,
padding, or radius values to see the bound variable name
(e.g. color/primary, spacing/6, radius/lg). These are the exact
CSS token names you’ll use in code.
Ask AI — reference token names and Storybook MCP
Include the Figma token names in your prompt. AI will use the same names in code, and will look up accurate prop names and examples from the Storybook MCP:
Build a settings card using LlmCard with variant="elevated".Match the Figma spec: --ui-color-surface-raised background,--ui-spacing-6 padding, --ui-radius-lg border-radius.Use the storybook-react MCP to check LlmCard props.Ship — the component matches the design
Because Figma variables and CSS custom properties share the same names, there is no gap between what the designer specified and what ships. Light and dark mode work automatically — the tokens resolve to their mode-specific values at runtime.