Back/Product/Figma/Codex
IntermediateProduct

Create a Bidirectional Sync Between Production Code and Figma Designs with AI

Move a running page into Figma as editable design, let the team refine it together, then give the updated frame URL back to a coding agent so it can apply the design to the local codebase.

Create a Bidirectional Sync Between Production Code and Figma Designs with AI

Gui sends a local budget allocation page to Figma for direct manipulation, then Alex copies the updated frame URL and asks Claude Code to bring those changes back into the app.

Before you start

What you need

  • A web app running locally
  • Codex or Claude Code with the Figma MCP connected
  • A Figma file where the team can collaborate
  • A reproducible local page or component

What you’ll make

An editable Figma version of the running page plus a local code update based on the team's revised frame.

Tools used

Step by step

The workflow

Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.

4 steps

Step01

Bring Production Code into Figma

Run the app locally and navigate to the exact page or component you want to edit. With the Figma MCP connected, ask the coding agent to send that live surface to Figma as editable design content.

Example prompt
Send the locally running budget allocation page to Figma as an editable frame. Preserve the current layout, copy, component structure, colors, and responsive state. Place it in [destination file or project] and return the frame URL.
Step02

Collaborate and Refine in Figma

Open the imported frame in Figma and work in the tool built for precise visual editing. Move elements, adjust color and spacing, and invite collaborators into the same file. Keep the updated work in one clearly named frame.

This step allows designers who are not comfortable with prompting or coding to contribute directly to the design sourced from live code.

Step03

Copy the Updated Figma Frame URL

Select the finished frame and copy its direct URL. A frame specific link gives the coding agent a precise design target and avoids ambiguity when the file contains several explorations.

Step04

Push Figma Designs Back to Code

Open the local repository in Claude Code or another agent connected to Figma. Provide the frame URL, name the component to update, and ask it to reconcile the design with the existing code and design system.

Example prompt
Bring the changes from this Figma frame into the budget allocation page in this codebase: [frame URL]. Reuse existing components and design tokens where they match. Update the local implementation to reflect the frame, then summarize the files and visible changes.

What good looks like

  • The imported Figma frame matches the current local page.
  • Designers can edit individual elements and collaborate in the file.
  • The coding agent can read the selected frame URL and update the correct component.
  • The local page reflects the intended Figma changes after the update.

Build your next product with ChatPRD

Turn an idea into a PRD, user stories, and a plan.

Try ChatPRD free

After the steps

Runbook notes

How to recover when the loop fails and where human judgment helps.

Recover

If it goes sideways

The coding agent cannot send the local page to Figma
Confirm the Figma MCP connection and account access, keep the local app running, and provide the exact route or component name.
The wrong Figma frame is applied back to code
Copy the URL from the selected frame, not the whole file, and name the destination page or component in the prompt.
The generated code does not match the revised design
Point out the specific spacing, typography, color, or structure that differs and ask the agent to reconcile that element against the frame and existing design system tokens.

Start shipping
better products.

Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.

Free to start
No credit card
SOC 2 certified
Enterprise ready