Repository pushes are ready to ship while component lineage remains hard to judge.
Designers need room to iterate from approved files, while engineers need generated changes to retain recognizable component structure.
Who you’d be doing this for
“I showed the same button in the file, then the review asked why it became a one-off component.”
Bruno Mendoza · Staff Product Designer
Maintains product flows in a shared design system and uses generated projects to make engineering handoff more concrete.
What is at stake
A release candidate hides shared-component drift behind previews that look correct. You must weigh fast design-to-code handoffs against a review boundary engineers can trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast repository pushes vs. reviewable component lineage
- designer exploration vs. component-system coherence
- visible previews vs. maintainable generated structure
- release timing vs. verified AI warnings
Why Figma
Figma Make connects Figma files to production code, so unclear component lineage reaches the same review queue as customer code.
Written with these in mind
Not your kind of problem? 45 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.