Writing

Essay · 5 min read · 2026

The only designer, and a fleet of agents

Being a design team of one, and learning to delegate to AI without producing slop.

When you're the only designer at a company, "the design" includes things no design school mentions. The product, obviously. But also the marketing site. The brand. The deck the founders take into the room. The booth, the social posts, the favicon, the empty-state copy, and whether the investor page says "AI-powered" too many times. (It did. I cut most of them.)

There is no design team. There is me, and a backlog that's winning.

So I did the thing a sole designer in 2026 has to do: I figured out how to delegate to AI without it producing slop. The trick isn't "make it look good," that gets you the average of the internet, which is exactly what my brand is trying not to look like. The trick is teaching it taste: feeding it the design system, the tokens, the rules I'd give a junior in their first week.

Operating a fleet of agents

Here's what surprised me. The jump in quality didn't come from a smarter model. It came from organization.

What makes it strong is how the work is split up. Anthropic's open-source Design Plugin breaks design into six specialized workflows: design critique, design-systems management, developer handoff, UX copywriting, accessibility review, and research synthesis. Each one carries its own instructions, its own evaluation criteria, its own output format, so the AI only ever makes one kind of judgment at a time.

That's the whole unlock. A model asked to "design this" does everything a little bit. A model asked to only critique, against a checklist, in a fixed format, does that one thing well.

Which, if you've ever managed people, sounds familiar. You don't hand one person the brand, the build, the research, and the QA and expect all four to be great. Turns out agents want the same thing.

I stopped writing prompts. I started writing job descriptions.

It doesn't replace me. What it replaces is the blank page. Being the only designer used to mean being the bottleneck. Now it means being the taste, and letting the taste run a fleet.

The stack I delegate to

A team of one, with a very deep bench.