Component inspection is fast, while approved guidance remains scattered across the workspace.
Developers need implementation context at the point of inspection, and design-system owners need that context to stay accurate and bounded.
Who you’d be doing this for
“I got three messages today asking why the same button has two approved states.”
Deepak Sharma · Design Systems Lead
Maintains the component library and answers implementation-context questions from developers using shared design files.
What is at stake
Developers are reopening libraries and asking designers for guidance that exists but is hard to locate. You have to weigh retrieval usefulness against workspace boundaries and reviewer confidence.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- developer speed vs. guidance accuracy
- retrieval breadth vs. workspace boundaries
- model flexibility vs. auditable behavior
- adoption signals vs. reviewer confidence
Why Figma
Dev Mode and Figma's MCP place the collaborative canvas directly inside the design-to-code path for enterprise design systems.
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.