Stop letting the code design the page.

Most AI redesigns inherit the page they were meant to rethink. Design Studio moves visual direction into a separate room, then makes the browser the judge.

Claude Code plugin · portable workflow contract for other agent tools

Run 014 / standard budget 4
01 / Framing
Rooted contextSource room

Frame

Product truth, app root, constraints and proof become a small testable brief.

Preserved builds Brief ready

The split is the product.

A single agent designs around whatever code it has already read. Design Studio gives creative judgement and implementation different rooms. The rendered page is their meeting point.

Blind room

No source context
  • Visual Director

    Builds the visual world from product truth, constraints, screenshots and scoped critique.

  • Evaluator

    Uses the rendered product and verified viewports. It reports evidence, not effort.

Source room

Implementation context
  • Planner

    Finds what is already true so the user is not re-interviewed and claims are not invented.

  • Builder

    Chooses technical means, preserves behaviour and implements the selected direction faithfully.

A run has an end.

The loop is for material improvement. A standard run gets four builds. The best eligible iteration receives one fresh finish review and at most one correction batch.

01

Context

Resolve the repository, app and product roots. Record the tools that are available before spending an iteration.

02

Direction

Explore three complete candidates. Unattended selection commits its seed and slot before those candidates are written.

03

Preflight

Deterministic checks catch contrast, overflow, focus and known generated-UI tells. Mechanical rules never award visual quality.

04

Decision

The Evaluator reports observations. The Orchestrator applies the recorded REFINE, PIVOT, SHIP or HALT rules.

05

Evidence

The final site, tokens and design DNA come from the selected build. Earlier iterations remain intact.

See the handoff.

Step through one run. Product truth moves into a source-blind direction, returns as a contract, and is judged in the browser before any build is accepted.

Five interactive steps show product framing in the source room, visual direction in the blind room, implementation in the source room, browser evaluation in the blind room, and final evidence-based selection.

01 / Frame product truth
Blind roomNo source

Visual Director

Turns truth and constraints into a visual contract.

Evaluator

Uses the page and records browser evidence.

Source roomSource allowed

Planner

Finds product truth, roots, proof and constraints.

Builder

Implements the chosen direction without replacing it.

Failure stays visible.

The workflow now records the facts that agents often assume: where the app lives, which tools worked, what step completed, and whether a finding still exists.

Root before run

`roots.json` separates repository, app and product context. Nested projects no longer depend on a package-manager guess.

Anchored

Tools declared

`capabilities.json` records the browser, server, detector, question and image tools. Missing browser access reduces the run before it spends a full budget.

Probed

Seed before options

Unattended runs commit an index before the Visual Director writes three candidates. Candidate order cannot become a hidden preference.

Assigned

Findings are current

Each detector rerun replaces the open snapshot. Fixed findings close, and reintroduced problems open again.

Current

Resume from evidence

`events.jsonl` records step starts, completions and failures. A resumed run validates artifacts and continues from the first incomplete step.

Resumable

Give the design its own room.

Install in Claude Code
/plugin marketplace add George-RD/design-studio
/plugin install design-studio@design-studio
/reload-plugins

/design-studio:create your next surface