The publishing handoff is preserving active work while losing the approved asset state.
Figma Make needs uninterrupted previews, while publication needs proof that generated code reflects the approved workflow.
Who you’d be doing this for
“I approved the updated asset, then the preview showed the old one in front of engineering.”
Kazuki Ogawa · Staff Product Designer
She approves visual workflow states before her team uses generated code in a production-bound interface.
What is at stake
Published previews are showing earlier asset versions after a newer workflow state was approved. You must weigh uninterrupted design-to-code work against a publish path that cannot prove what it rendered.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- publish continuity vs verified workflow state
- shared-platform stability vs product-specific containment
- rapid containment vs audit-ready controls
- agent output velocity vs human review
Why Figma
Figma Make and the Figma Design Agent depend on a shared publishing path that turns AI-generated work into customer-visible experiences.
Written with these in mind
Not your kind of problem? 51 more at Figma, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.