Working Surfacelink · 13 Nov 2026
05
A small toy train runs on a loop of track between a drafting table and a brick workshop, carrying the same set of wooden building blocks in both directions, while a figure seen from behind checks a short list pinned to the carriage, the whole scene drawn with wide empty margins on every side.
UX Collective

In-system design: from code to Figma and back. Prototyping in your real design system

Christine Vallaure · 11 November 2026

How-to · design systems · prototyping · Agent context files

Read the original
Takeaway

Designer Christine Vallaure moves prototypes between code and Figma with an AI agent by naming components identically on both sides and asking for a note of anything invented.

Summary

Christine Vallaure, a designer who teaches design and code through her platform moonlearning, wrote in UX Collective about moving prototypes between code and Figma. She finds that comparing versions side by side on a canvas still beats refining one screen through prompts, so she wanted both surfaces without redrawing. Her method keeps the design system's real components on both sides, so an AI agent can rebuild a code prototype in Figma and send edits back.

Key points
  • Every Figma component carries the code's exact name and properties, so moving a screen is a lookup; when names differ, the agent guesses with confidence.
  • She asks the agent to leave a note beside each prototype listing the real components used, parts built by hand, mismatches and suggested new components. She reads it before the screens.
  • A small file listing every Figma component and its properties replaced a 59,000-character search for one text style, and also shows whether Figma still matches the code.
  • The round trip caught a 21-pixel spacing fault in the code that automated checks had missed. Prototypes stay on a design branch that is never merged, and a developer rebuilds the accepted parts.
Implication

A design system team that matches component names exactly between code and Figma lets an AI agent move work between them without redrawing. This is an inference and is not the author's claim. The piece is one practitioner's workflow, which she describes as still trial and error.

Plays
Design

Name each Figma component and its properties exactly as in the code component library, so an AI agent can rebuild a screen from Figma in code, or back, by looking up parts instead of guessing.

Design

Ask the AI agent for a note beside each prototype listing the components it used, what it built by hand and where Figma and code differ.

Derived by Working Surface from the article; more in the Playbook. Source line: The design branch is never merged into the system.

Source issue

13 November 2026: AI agents earn more freedom when a team limits what they can reach, from data to design components, and adds a check that does not depend on a glance.