Everything I wrote about PMs and strategic designers in Throwing Away the Prototype lands on front-end developers and UX/UI designers too. But the implication isn’t “learn to code faster before AI takes your job.”
UI implementation didn’t get marginally cheaper. It got structurally cheaper. The cost curve changed shape. The gap between design intent and a working first draft collapsed from days to hours for standard patterns.
Where AI removes work: state wiring, boilerplate routing, form logic, test scaffolding, CSS alignment.
Where AI fails: accessibility edge cases, performance under load, complex state management, and consistent interaction contracts across dozens of screens. AI can build a filter component. It can’t ensure that filter behaves like the nine other filters in the product.
That’s where the constraint moved, and where the value of implementation and design moved up the stack.
A different unit of work
Front-end composability is a different unit of work. Instead of building screens one at a time, I’m defining which UI states are allowed across hundreds of screens I’ll never touch directly. What can vary, and what can’t. Buttons can be primary, secondary, or ghost. Not 47 custom variants. Tables can filter and sort, but the interaction pattern stays consistent.
I’m defining the interaction vocabulary that both humans and agents use. When a PM prompts an agent to “add a filter to this table,” the agent needs guardrails. Without composability work, it invents a new pattern every time. With it, the result is consistent.
When a PM opens Lovable and describes a feedback form, they’re relying on component libraries that work, interaction patterns that make sense, and accessibility standards that hold. Someone built those foundations. That someone is you.
I did a version of this before agents. As a senior UX designer at Confirmit, I built a unified design system for our reporting products, dashboards and text analytics, so that what design specified and what front-end development shipped stayed consistent. Agents make that job mandatory. A weak component, copied a thousand times by an agent, becomes the product.
The new discipline is building infrastructure that lets non-engineers ship front-end safely, so that when five different people push UI changes, the result coheres instead of conflicts.
This is where UX/UI designers gain leverage. You already think in systems. Design tokens, component libraries, interaction patterns. That’s the vocabulary. The shift is from producing artifacts to producing the constraints that guide artifact production.
Value isn’t in how many screens I build. It’s in how many good screens I enable others to build.
My pace now is an analytics dashboard in four hours, a release-automation system in three days, an app a twenty-person team maintained for years rebuilt in two afternoons. This happens when iteration loops compress and I stop being precious about reverting. In critical infrastructure, the screens that matter are the ones an operator can trust at 2 a.m. Composability is how those screens stay trustworthy after an agent has touched them.
Also in February: The Death of Front-end Development · Throwing Away the Prototype · Two Paths for Interface Work
Daniel Arevalo is Product Experience Lead at Omny Security. He builds AI-native tools and writes about design, product leadership, and what it means to direct systems that execute at a speed humans never had before.