The days of recreating your product in Figma are numbered (and that’s a good thing)

Product designer Alexis Vaysse argues that teams should stop redrawing screens in Figma and design them in code with an AI agent, handing over a pull request.

Alexis Vaysse is a product designer who has spent years keeping Figma mockups in line with the coded product, including building AI agents that compare mockups with live screens. He tested a workflow in which a designer instructs an AI agent in a code editor and watches the real screen take shape beside it. He used Claude Code, Anthropic's coding agent, with Astryx, a design system from Meta built for AI agents, and reports a consistent result produced very quickly.

• In the workflow the designer delivers a pull request, and a developer reviews it and connects data and business logic. A purely visual fix needs only that review.
• Working on real components shows cases a mockup hides, such as a 40-character name wrapping onto two lines or an empty list showing its empty state.
• Vaysse lists four conditions: code is the source of truth, and each component has a data file and a usage file written for AI agents. The design system also supplies screen templates, and automated checks reject code that does not use its components and tokens.
• The design system team still designs new components in Figma before coding them. Developers keep the architecture, and product managers keep needs and priorities.

A design team could try this on one existing screen once its design system is documented for AI agents and checked automatically. That order of steps is an inference and is not the author's claim. The piece is one designer's bet, supported by a personal test rather than a team rollout.

Derived by Working Surface from the article; more in the Playbook. Source line: The designer no longer delivers a mockup, but a PR.

31 October 2026: as AI agents produce more of the work, teams move the checking to the people and records closest to the real output.