No more excuses for sloppy design.
Good UI is table stakes.
Published Nov 19, 2025 · Around 2 minutes to read
I used to spend a lot of time with dev teams managing pixels. My designs would always be slightly off during implementation: the spacing, colors, typography wouldn't exactly match what I had in Figma. And we'd go back and forth on JIRA subtasks fixing them.
Design systems helped fix this gap. But you needed a champion, some effort up front, and someone to maintain it. And we never had enough resources.
Closing the gap between design and dev is a perfect use case for AI. There are a couple of things I saw this week that solidified my belief:
-
Improving frontend design through Skills. AI is getting more precise with its outputs, which means the quality of your specs are more important than ever: Claude blog post
-
Agentic IDEs like Cursor let you interact with live states. The value of design is in tons of cheap exploration before expensive software writing. Software prototyping is becoming a lot cheaper now, and there's little reason for us to keep mocking up pictures of software. Sketching by hand or moving pixels around is still faster though, I'll admit that.
The floor for design quality has been raised. The problem now is that even if you follow all the "good" design rules, your designs will look statistically average (boring):
"When you ask an LLM to build a landing page without guidance, it will almost always conform to Inter fonts, purple gradients on white backgrounds, and minimal animations."
And in a changing world, playing it safe is the riskiest thing you can do.
--
P.S. I'm excited to try Google's agentic IDE: Antigravity. You can be more specific in asking for design changes like "make this gap 30px" or "make this pop."
P.P.S. Another large type footer in the Antigravity landing page! Love it. Props to Mike K for pointing this out.
READ NEXT