A Claude Code plugin · guided design session

The site you're reading was built by the thing it's selling.

A short scoping interview, three mockups you pick from, then the full pipeline to a production Next.js site — 80 skills, 3 subagents, 7 screenshot-verified gates. Every decision it made is on file.

Phase 0 preflight 16:42–16:47, eyes verified.
Phase 1 brief + interview 16:47–16:56, 1 round, 3 questions.
Phase 2 running — you are reading candidate C of this build's own mockup round.

Read the whole paper trail →

claude — ~/my-site guided

~/my-site ❯ /plugin marketplace add blyatiful1/ultraweb
  Marketplace added.

~/my-site ❯ /plugin install ultraweb@ultraweb
  ultraweb v1.7.0 — 80 skills, 3 subagents, 7 gates.

~/my-site ❯ /ultraweb build me a website for my studio
  Guided session. Two decisions are yours: what the site is,
  and how it looks. Nothing expensive runs before you approve
  a mockup.

  Scoping interview — 4 questions, every one skippable:
   1  How many case studies ship at launch?
   2  Contact form, or a mailto and a calendar link?
   3  Does the studio publish writing?
   4  One language, or German and English?

  Answer any of them, or say "skip — I'll decide".

~/my-site ❯

Commands verbatim. Responses paraphrased from the plugin's actual first turn — no invented output, no dashboard that doesn't exist. In the built site this frame is typeable, with tab-complete over the real commands; where scripting is off, it degrades to exactly this transcript.

The guided session

Three decisions stay yours. The rest is the studio's job.

A pipeline that asks you about everything is a questionnaire, not a studio. A pipeline that asks you about nothing ships something you have to argue with. ultraweb puts the human exactly where real studios put the client: heavy at discovery and design approval, thin during production, back for acceptance.

01 / INTERVIEW

Questions built from your prompt

Up to four, generated from what your prompt left open — scope and substance, never colors. Every question carries a marked default: skip it and the answer is decided, logged, and traceable.

02 / MOCKUPS

Three candidates, one tab

Three deliberately contrasting archetypes rendered as throwaway static HTML. Pick one, mix named elements across them, or send the round back. Phase 3 and everything expensive after it waits for an Approved line — that is the gate, not a formality.

you are inside step 02 right now

03 / CHECKPOINTS

Reviews on the real thing

First-page review on the built homepage at 375 and 1440, then preflight acceptance after every gate is green. You are the acceptance test, never the first QA.

Engagement dial

priced in minutes of your time — the plugin's own checkpoint budget

hands-off "just build it" · no stops, nothing waits on you 0 min

guided the default · direction approval, first-page review, preflight ~30 min

studio "check in with me at every step" · all six checkpoints ~43 min

2 + 10 + 3 + 5 + 8 + 15 across the six checkpoints. Re-settable mid-build: "stop asking me" moves the dial down, and the move is logged. A session that cannot reach a human auto-passes instead of stalling.

Scope dial

priced in relative cost — no token count is claimed here

sketch two candidates, one judge round less

standard the pipeline as written baseline

flagship five judge rounds, set-piece eligible — this build more

Sizing is back-of-envelope and the README says so. Gates never weaken to fit the dial: a sketch build still passes gate-code and gate-antislop in full.

The studio floor

Eighty skills, and you can read every one of them.

80skills

3subagents

7gates

tastethe design constitution: first-grade bar, banned list, required list, heuristics→ judgment

briefone prompt into a full creative brief; guided mode runs the scoping interview→ design/BRIEF.md

directionone archetype from a catalog of 12, one signature move, an explicit "we will not" list→ design/DIRECTION.md

mockupthree throwaway HTML candidates and the pick / mix / revise round→ design/mockups/*.html

tokensthe whole system as Tailwind v4 @theme tokens — the one file every component reads→ app/globals.css

herofirst-viewport sections: variants, headline scale, CTA hierarchy, above-fold cost→ sections/hero.tsx

navigationheaders and mobile menus, active states, the mobile menu as a designed moment, skip-link→ layout/header.tsx

copywritingevery string on the site; headlines that earn their size; bans dead startup copy→ copy in code

gate-visualscreenshot, judge against DIRECTION.md, fix the worst issue, repeat→ design/QA.md

shipenv audit, build and start smoke test, deploy, verify the live URL→ live site

10 of 80 shown · the built site puts the full index behind ⌘K as an accelerator, never as the only path — browse all 80 by tier

Three subagents, models pinned in the skill files

design-judgeOpus 5scores screenshots against DIRECTION.md and the constitution, returns ranked defects

pixel-qaSonnet 5drives the browser: screenshots at 375 / 768 / 1440, console errors, layout breaks

stack-doctorOpus 5repairs builds and dependency conflicts without downgrading the pinned stack

Install

Two lines, inside Claude Code.

Then say what you want built. The interview starts; nothing expensive runs before you approve a mockup.

1 · add the marketplace

/plugin marketplace add blyatiful1/ultraweb

2 · install the plugin

/plugin install ultraweb@ultraweb

then · start a session

/ultraweb build me a website for my studio

Read the source first →

needs Claude Code
needs Node + npm
needs Playwright MCP — the eyes
optional Vercel CLI, for preview URLs

Cloning locally instead, or updating an install? The install page carries the alternative route and /reload-plugins.