Builders skip naming design tokens because they think it slows them down.
Handing a layout to Claude Code without locked variables just invents random hex codes and uneven margins. Strict naming and a solid system reduces the UI drift 😅
I hit an $800 NZD usage limit mid-sprint while building with Claude.
When you are in flow and actively shipping, you do not notice the token meter running in the background. The speed is cheap until it suddenly stops.
Teams keep burning tokens asking AI to build basic buttons and inputs from scratch.
Your design system already solved the primitives. Models compound when you point them at messy logic and edge cases.
Why rebuild the button?
Design systems fail the moment an agent has room to guess. Hand Claude Code or Cursor loose spacing tokens and the layout drifts on the first commit.
Prompt engineering never fixes broken token architecture.
I couldn't even get a ticket to my own talk at BNZ today because it sold out.
Prompt tricks do nothing once you build real software. Without locked constraints and structured context, the UI drifts every time. How do you stop the drift?
I spent my first five years as a designer getting really good at the wrong thing.
I obsessed over visual polish and pixel-perfect layouts.
Turns out interfaces fail when the business problem was misunderstood, not because a radius was off.
Software only survives when it understands the messy ways people actually work.
Now that background automation is free, bots that just click buttons and fill out forms are dead. Anyone can build those now.
Clients buy visual clarity, not generative speed.
Claude Design gave me a finished slide in 10 minutes.
Rebuilding the hierarchy in Figma so it was sendable to a board took me 2 hours.
The tool solved the blank canvas. Fixing the cognitive friction was still manual work.
The best product work eliminates user input instead of polishing it.
If a customer is still manually filling out the form, slapping sparkle icons and chatbot sidebars onto the screen is just cosmetic skin. The actual job is restructuring the workflow until the steps disappear.
I built and shipped Design Signal over a weekend using Claude Code.
Without an engineering background, code syntax mattered far less than having the taste to spot when an interface actually felt right.
My grandma gave advice that mirrors product design: you can't evaluate something in isolation.
In Logic Pro, soloing a track sounds pristine until you unmute the rest.
In design, polishing padding and border radius falls apart the second it hits a real screen with messy data.
@mufasa__II Little cat A B C and D E F G and also H I J K and little Cat L M N O and P. Q R and S T U V and lastly little cat W X Y and Z.
Needed a Voom. 😏