From Figma to Claude Code and back | Gui Seiz & Alex Kern (Figma)
Why I picked this
Visual design has been the holdout — the creative domain where AI felt most suspect. Designers could point to taste, spatial reasoning, the ineffable craft of making things feel right. But Figma's own team just demonstrated something more interesting than 'AI does design now.' They've shown how AI collapses the middle phase of design work entirely. Not the strategic thinking at the front (what should this do?) or the craft refinement at the end (does this feel right?), but the rushed execution phase where designers frantically translate concepts into pixels under deadline pressure. That's the part Claude Code now handles.
What makes this worth attention: it's Figma practitioners showing their actual workflow, not a vendor pitch. Gui and Alex walk through bidirectional sync between design files and production code via MCP — meaning the Figma file and the shipped product stay coupled, not divergent artifacts. The 90% AI-generated code metric matters less than the structural insight: when your codebase is organized for AI legibility, the tool becomes genuinely useful rather than a novelty that generates plausible-looking garbage.
The frontier isn't 'can AI design' but 'what does design work become when execution speed approaches zero?' Figma's answer: designers move upstream to planning and downstream to craft, spending time on the parts that actually require human judgment. The frantic middle — where most design work currently happens — compresses into minutes instead of days. That's a workflow transformation, not a feature add.
Three lenses
The MCP integration is the real story here — bidirectional sync means I can iterate in code and have design files update automatically, or vice versa. That's not a workflow improvement, that's eliminating an entire class of version control problems that have plagued product teams for a decade.
Show me the designer who's actually shipping 90% AI-generated code to production at scale, not in a demo. The workflow looks elegant until you hit edge cases, accessibility requirements, or the reality that most codebases aren't 'properly structured' for AI legibility. I need to see this deployed across a 50-person product org before I believe the efficiency gains translate.
Notice what they're not saying: how many iterations it took to get Claude to generate usable code, how much prompt engineering expertise is required, or what happens when the AI hallucinates a component that looks right but breaks accessibility. The 90% metric is meaningless without knowing the denominator — 90% of what kind of code, for what kind of features, with how much human correction?
“AI has shifted design work upstream to planning and downstream to craft, eliminating the rushed middle phase of execution”
Key takeaways
- Figma's MCP enables bidirectional sync between design files and production code, eliminating static handoffs and version drift
- AI coding tools enable 90% code generation when codebase is properly structured, with custom skills automating pre-flight checks and CI monitoring
- Design workflow is bifurcating: AI handles rushed middle execution phase while humans focus on strategic planning (upstream) and quality craft (downstream)
People mentioned
- Gui Seiz, Designer @ Figma
- Alex Kern, Engineer @ Figma
Companies
Key metrics
- •90% of code written by AI
Why this matters for operators: Product teams rethinking design-engineering handoffs and evaluating whether their codebase structure enables or blocks AI coding tool adoption
I cover AI×GTM intelligence like this every Wednesday.
Get STEEPWORKS WeeklyMore picks
Humans will keep inventing new reasons why we must stay in the loop with agents
- Human resistance to full AI autonomy is not purely technical—it's psychological and organizational; companies will rationalize keeping humans in decision loops even when agents are capable
- The 'human-in-the-loop' requirement may become a self-perpetuating narrative rather than a genuine necessity, driven by organizational risk aversion and change resistance
- Product leaders at scale (Notion) are observing this pattern, suggesting it's a widespread phenomenon across enterprise AI adoption, not isolated to specific use cases
Comp plans for consumption pricing
- Consumption pricing fundamentally breaks traditional SaaS comp models—requires rethinking sales incentive structures around usage vs. contract value
- Four distinct contract structures exist (pay-as-you-go, uncommitted, committed, hybrid), each requiring different compensation mechanics and sales behaviors
- Enterprise consumption-based deals create tension: customers want flexibility, sales teams need predictability for quota attainment—comp design must bridge this gap
3 revenue motions your AI is only half wired into
- Model parity has arrived: OpenAI/Claude now trade evenly on core tasks, making 'better AI' a non-differentiator—the edge shifts to integration depth into existing revenue motions
- Waste is quantified: teams paying $17K-$37K/month for AI seats that never touch pipeline generation; real cost is opportunity cost of unused capacity, not subscription fees
- Lean teams have a structural advantage: cannot out-buy larger competitors on model access, but can out-embed them by wiring AI 1 revenue motion deep (pipeline → content → deals) with proprietary deal context competitors haven't seen
This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.