
[Insights]
Designingwithanagent:howthissitewasbuilt
This portfolio went from Figma file to production without a traditional developer handoff. Here's what changed in the process, and what stubbornly didn't.
For most of my career, shipping a design meant negotiating it. You drew the thing, then argued with time, budget and whatever stack the developer believed in, until what launched was a compromise wearing your design's clothes. This site is my counter-example: designed in Figma, then built in collaboration with an AI coding agent, with me directing instead of handing off.
The loop is tight in a way handoff never was. I describe the scroll choreography I want, the agent builds it, and I look at it running. Not a static mock, the actual thing. Then I steer. Wrong easing? Say so. Reveal starts too late? Point at it. The distance between taste and implementation collapsed from days to minutes.
“The agent didn't replace the developer conversation. It replaced the waiting between the conversations.”
What didn't change: every decision that matters is still a design decision. The agent will happily build the wrong thing beautifully. Knowing what the hero should feel like, why the grain overlay needs a blend mode, when an animation is one detail too many. That judgment is the job. The tools moved; the taste didn't.
If you're a designer wondering whether this makes you obsolete: it makes you dangerous. You can finally ship what you meant, at the fidelity you meant it, without asking permission from a sprint board.
Curious what agent-driven building could look like for your team?
Happy to walk through the workflow, the tooling and the honest limitations.



