Agentic design is product design where I lead and agents build. I research, plan and decide at every step. The agents take the volume.
Design isn't only what looks good. It's what works, and what gives people the best possible experience. Agents can make almost anything. Knowing what's right is the moat, and that's taste.
What people get wrong
They think it means prompting a screen and shipping whatever comes out. That's generating, not designing.
The real shift is from drawing to directing. I don't build every pixel anymore. I build the system the work happens in, and steer everything that comes out of it. It doesn't replace designers. It replaces the volume work.
From idea to production
Say a flow in the Customerly web app needs work.
Research. I start with the problem, not the screen. How users actually behave, what they tell us, and how the best products solve the same thing. Agents help me gather it. I decide what matters.
Plan. I write down what changes, what stays, and what "better" means here. The agents build what I decided, not their own idea of it.
Build. I prototype in code, inside our design system, and try several directions before picking one. I test it on real devices, not in a mockup.
Ship. I share it in the product sprint, open a PR, the devs review it, and it goes live. Then we watch the analytics and the feedback, and keep refining.
Hours or days, not weeks.
What the agents work from
Every brand I work on has its own operating system, and every part of the product has its own dedicated section inside it. It holds who the product is for, how it works, the design system, the brand and voice, the rules we don't break, and the decisions we've already made.
It's the one source of truth for the whole team, humans and agents. Nobody works from an old version of it.
What I never hand over is the direction.
Where agents fail, and how I catch it
Less than you'd think. With the right context, an agent knows the right solution before it starts, so it doesn't burn time and tokens finding out.
When it does slip, it's the small details, never the core of the work. I catch those on real devices and in review. And when something slips, I fix the system, not just the screen, so it doesn't happen twice.
What stays human
Every decision that matters. What's worth researching, what the plan is, which direction we take, and when it's ready to ship. Agents help at every step, but they don't decide any of it.
Agents made making cheap. Knowing what's good, and what works for real people, is the job now.
What I changed my mind about
I used to think Figma was where design happened. Now it's where I start least.
Building every variation from scratch in Figma was slow, so I explored less than I should have. In code, with agents, I can test several directions in the time one used to take, and pick the best with real behavior in front of me. Optimizations that used to sit in the backlog get shipped now.
Questions
Is agentic design the same as AI-generated design?
No. Generating a screen is one step. Agentic design is the whole loop, from research to production, led by a designer who decides at every step.
Does it replace designers?
It replaces the volume work. Teams still need someone who finds the right solution and owns the experience.
What is a design engineer?
A designer who ships their own work in code. I own the UI end to end, from design system to production, and leave logic and architecture to engineering.