Back
Process

A design pipeline, run by agents.

I built a multi-agent system that runs the full UI/UX loop in Figma — inspiration, a real design system, screen building, and a scored audit — with me approving every stage and a hard quality bar on the output. Not vibes. A system.

Role
Design + AI systems
Built with
Claude Code · Figma
Agents
4 specialised
Output
Production design system
golden@design — /uiux
~/atlas-app $ /uiux
✓ inspiration direction approved
✓ design-system 47 components · 3-tier tokens
✓ ui-builder dashboard · wireframe → hi-fi
▸ ui-auditor scoring… 92 / 87 / 84
The Pipeline

Four stages, from direction to scored screens.

One agent per stage, each with a single, narrow job — and each one hands its output to the next. I stay the director; the agents do the throughput.

01
02
03
04
you approve
you approve
you approve
01
Inspiration

Set the direction

Reads references — images, Figma, notes — into a written visual direction.

agent · inspiration
02
Design System

Build the system

3-tier tokens, 30+ components with full states, grid, icons — in Figma.

agent · design-system
03
UI Builder

Wireframe → hi-fi

Builds each screen from the system only — low-fi first, then high-fidelity.

agent · ui-builder
04
Audit

Score the work

Grades fidelity, direction-match & UX. Below bar → surgical fixes, re-audit.

agent · ui-auditor
↺ re-audit loop — surgical fix, max 3×
↺ fails audit → surgical fix + re-audit · max 3 attempts
The Agents

Four specialists, one shared system.

Each agent has one job and one contract — a clear input, a clear output. None of them improvise; every screen is built from what’s already approved.

inspiration

Direction-setter

in refs, links, notes
out visual direction doc
design-system

System architect

in approved direction
out tokens + 30 components
ui-builder

Screen builder

in brief + system
out wireframe → hi-fi screen
ui-auditor

Quality gate

in finished screen
out scored report + fixes
Design-system fidelity92
Direction match87
UX quality84
The quality bar

Nothing ships under 80.

Every screen is scored on three axes. If any falls below the bar, the auditor writes precise fixes and sends only those back to the builder — then re-scores.

↳ still failing after 3 attempts? It escalates to me.
The Payoff

Weeks of work, in days.

Same scope on both sides, from direction to QA’d hi-fi. The pipeline doesn’t cut corners; it collapses the production time and shifts the effort to direction and review.

Traditional
~4.5weeks
With pipeline
~3days
≈ 7× less calendar time
Top bar = traditional. Green bar = the same work, with the pipeline.
Visual direction
~1 day → ~1–2 hrs
Design system
~2 weeks → ~½ day
8 screens · wf → hi-fi
~8 days → ~1 day
Design QA + revisions
~3 days → ~½ day

Estimates for a representative 0→1 build, one designer — production time only. Scope and mileage vary.

Why it matters

Speed, without losing the craft.

01

0→1, faster

Direction to a scored, on-system hi-fi screen in a fraction of the usual time — because the system does the throughput.

02

Consistent by construction

Every screen is built from one approved design system, so nothing drifts. The system evolves only with my sign-off.

03

Human-in-the-loop

Approval gates at every stage and a hard quality bar mean I stay the director — the taste and the calls are still mine.

The same rigor, on your product.