Personal Productivity & AI-Augmented WorkPractitioner StoryLenny's Newsletter

From Figma to Claude Code and back | Gui Seiz & Alex Kern (Figma)

Read original

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.

ai-coding-toolscursor-vs-copilotautomation-stacksai-writing-workflows

Three lenses

Builder

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.

Revenue Leader

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.

Contrarian

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

FigmaAnthropic

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 Weekly

More picks

GTM OpsDemand Gen ReportVictor's pick

Trust is the New Currency in B2B Buying: SurveyMonkey, Reddit

These are high % stats showing what we implicitly already know

  • Peer validation (73% trust) now dramatically outweighs traditional vendor marketing (55% trust vendor sites, 39% trust AI chatbots, 36% trust social media) in early-stage B2B buying
  • 83% of B2B buyers complete self-directed research before sales engagement, with high-stakes categories (software, professional services, HR) taking several weeks to months in extended evaluation
  • Search engines serve as navigation layer, not destination—buyers use search to identify options then validate through peer communities like Reddit (121M daily users, 19% YoY growth), creating imperative for authentic community presence
community-led-growthback-to-basics-gtmhuman-first-sales
AI DevelopmentGTM AI Podcast & NewsletterVictor's pick

Claude Channels

The move from user initiated to automated workflows is one of the main transitions with current agentic capabilities IMO

  • Claude Channels (launched March 20, 2026) enables event-driven AI automation via MCP protocol, shifting from pull-based (user-initiated) to push-based (event-triggered) workflows
  • Practical use case: CI/CD failures can trigger autonomous investigation, fix deployment, and resolution without human intervention - reducing 12-hour incident windows to near-zero
  • Technical implementation uses MCP servers connecting Claude Code to messaging platforms (Telegram/Discord at launch), with Bun runtime for 4x faster cold-start performance vs Node
ai-coding-toolsautomation-stackssignal-infrastructure
AI×GTMThe InformationVictor's pick

AWS Accelerates Internal AI Agents Following Staff Cuts

If you think white collar job displacement is a joke, or a distant future concern, this is just one more sign it is most definitely NOT. It's here.

  • AWS is deploying AI agents to handle technical sales support functions previously performed by thousands of specialists
  • The AI automation directly correlates with recent layoffs of hundreds in sales, business development, and technical specialist roles
  • Major cloud provider is using its own AI capabilities to reduce headcount in customer-facing technical roles, signaling broader industry trend
ai-sdr-adoptionautomation-stacksback-to-basics-gtm

This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.