Library readiness needs to be visible without turning enterprise design files into open analytics data.
Design-system teams need earlier signals for AI-assisted handoff, while enterprise file content remains tightly bounded.
Who you’d be doing this for
“Engineering found three missing states after the code review, and now everyone is asking why we didn’t see it earlier.”
Amadou Komolafe · Design Systems Lead
Maintains an enterprise component library used by designers and developers across product teams.
What is at stake
Generated code is exposing inconsistent tokens and missing component states after handoff. You must weigh broad readiness visibility against the limits on enterprise file data.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- shared readiness visibility vs enterprise data boundaries
- early handoff signals vs trustworthy definitions
- pilot speed vs reusable platform patterns
- designer actionability vs engineering predictiveness
Why Figma
Dev Mode, Code Connect, and AI-assisted design workflows depend on component libraries that carry consistent structure into engineering work.
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.