April 18, 2026
Pixels vs. Code: choose your fighter
Thoughts and Feelings Around Claude Design
Figma fatigue explodes as Claude’s “back-to-code” pitch splits designers
TLDR: Claude Design’s code-first approach sparked a huge debate: fans say it cuts through Figma’s complexity and puts design back in real code, while skeptics warn the whole design-tool space is a graveyard. Why it matters: it’s a fight over how teams actually build products—and who owns the source of truth.
Designers didn’t just react to Claude Design—they stormed the stage. The thread lit up with 732+ comments (link) as folks argued whether this new, code‑first tool is the future or just another shiny distraction. The take that set the room on fire: as artificial intelligence learns from code, the “source of truth” moves back to code—and all of Figma’s layers-on-layers start to look like a maze.
One loud camp cheered, dunking on Figma’s bloat and clunky feel. User mojuba basically screamed “to hell with Figma”, complaining it’s a heavy, sluggish app and wishing someone would just fix Sketch already. Others swooned at Claude’s “truth to materials” vibe—build in the real stuff, not a picture of it—with klueinc arguing Anthropic’s control over the model could make the tool feel like it has built‑in expert taste.
But skeptics crashed the party. sebmellen sighed that the design-tool world “died” when InVision pivoted, warning this space is brutally hard. And operatingthetan threw a grenade: design, front‑end, UX, and product are basically one job now, so tools won’t save you.
Meanwhile, the memes flew: people joked about “Prop Props,” eye‑rolled Figma’s endless variables, and revived the essay’s “time to be a sheep farmer” line. Verdict? It’s a vibe war—pixels vs. code—and nobody’s backing down.
Key Points
- •The author tested Claude Design and argues design tooling is moving back toward code as the primary source of truth.
- •Figma introduced complex primitives (components, styles, variables, props) that made automation difficult and created specialized system-wrangling roles.
- •Figma’s canonical-file strategy helped it beat Sketch but its proprietary, under-documented format hindered programmatic access and AI relevance.
- •Maintaining parity between code and Figma is burdensome; even Figma’s own design system files exhibit complex, hard-to-debug indirection.
- •The author positions Figma Make as reinforcing Figma’s system, while Claude Design embodies a code-aligned, 'truth to materials' approach.