Brief

Brief — ultraweb showcase (ultraweb-site.vercel.app)

Mode: guided · Scope: flagship · Interview: 1 round, 3 questions, 2026-08-14

Site type & energy budget

Dev-tool product/marketing site that is simultaneously the product demo — the site is built by the pipeline it sells, in a guided session, and ships its complete paper trail. Energy: portfolio-agency boldness ("the site IS the portfolio — spend boldly") on the demo surfaces, SaaS clarity on the decision surfaces (comparison, bill, install). One signature move, everything else disciplined.

Audience

A working developer who already ships with Claude Code — mid-career, evaluates tools by reading the repo before the marketing, has a token budget they actually think about, and decides in one evening whether a plugin earns a slot in ~/.claude. Desktop-first, but first contact is often a phone link from a chat. They distrust: AI-slop aesthetics (they can smell the purple gradient), invented numbers, hype verbs, and any claim they can't click through to verify. Proof they respect: receipts, dated decisions, honest cost, an UNVERIFIED cell where the truth is UNVERIFIED.

Goals

Primary conversion: the two-line marketplace install (/plugin marketplace add blyatiful1/ultraweb → /plugin install ultraweb@ultraweb) — measured by the copy action's prominence, not analytics. Secondary: visit to github.com/blyatiful1/ultraweb. Success: a skeptical developer reads this build's receipts and installs.

Tone

Assured, exacting, dryly self-aware. Tension pair: a pitch that audits itself. README's voice governs: confident studio metaphor, honest about cost, zero hype-slop. Sample sentence: "The site you're reading was built by the thing it's selling — and every decision it made is on file."

Pages

Route names are provisional until copywriting; jobs and set are committed. English only.

• / — the pitch: what it is, where it sits (honest comparison), the guided session in one screen, the live report card (from design/RECEIPTS.json), install CTA. Serves both conversions.
• /session — the guided session in depth: interview → mockup round → checkpoints; the two dials priced in their own units; PROGRESS.md's two clocks; resume; /studio; taste fingerprint + heretic seat. Job: convince the "how much control do I keep" skeptic.
• /skills — the studio floor: full browsable index of all 80 skills (interview R1) by tier/department, 3 subagents with pinned models, the 7 gates, hooks as capability, the 8-client cast. Job: prove depth is real, not a number.
• /craft — why the output isn't slop: taste constitution, the banned list AS QUOTATIONS (the single licensed surface — DIRECTION.md must record the named exception), required list, seven gates incl. the UNVERIFIED third verdict, award-canon (32 dossiers → 25 patterns, 2017–2026), STACK.md's verified-not-remembered discipline. Job: disarm the slop-skeptic.
• /receipts (+ artifact subroutes) — the reading room (interview R1): this build's full report card, per-phase durations, gate table, review ledger, git phase ledger, and the committed artifacts rendered on-site — including the mockup round with the two losing candidates (screenshot + the original throwaway HTML served statically, never rebuilt as components). Job: be the proof; feeds GitHub + install.
• /install — install commands (marketplace + local-clone alt), prerequisites (Claude Code, Node+npm, Playwright MCP as the eyes, Vercel CLI optional, token headroom), the honest bill, iterate/retrofit as the low-cost on-ramps, prose mention + link to the old build's measured receipt (attributed, dated 2026-07-28 — no table, interview R1). Job: close.

Content inventory

• Counts & facts (repo-backed only): v1.7.0 · 80 skills (1 orchestrator + 79 specialists), 8 tiers · 3 subagents (design-judge/Opus 5, pixel-qa/Sonnet 5, stack-doctor/Opus 5) · 7 gates · 6 checkpoints · 2 dials (engagement: hands-off/guided/studio — costs MINUTES; scope: sketch/standard/flagship — relative cost, README's sizing labeled back-of-envelope) · 12 archetypes · award-canon: 32 dossiers, 25 named patterns, 2017–2026 · stack pins verified 2026-07-16 (sections 07-28/07-29), 30-day expiry, refresh script · taste fingerprint: last 10 builds, mandatory heretic seat · dial trigger words from root SKILL.md.
• Comparison row (/): v0/Lovable/Bolt (a page in ninety seconds) and plain Claude Code (improvises from vibes) vs ultraweb — trades speed and tokens for a written taste constitution, an adversarial screenshot critic, and an inspectable paper trail. "Verification is the product." Use a prototype tool to explore; use ultraweb to ship the site you'll defend.
• THIS build's story (/, /receipts): a guided session, named and dated — Phase 0 eyes repair (2026-08-14), interview R1 with the client's three scope answers, the mockup pick at CP2, CP4/CP6 verdicts, every number from design/RECEIPTS.json (regenerated from artifacts as the last pre-ship action; uncountable metrics omitted, never estimated).
• Honesty constraints (binding all pages): old-build table + "no human touch-ups" prose → prose mention + link only, attributed, dated; hooks + /studio activity feed → CORRECTED mid-build (QA.md §CORRECTION): hooks ARE registered and fired here — present as live this-build evidence including the correction story; no invented numbers anywhere — if the repo or this build's artifacts can't back it, it's not on the site.
• Install: the two slash commands verbatim; local marketplace alternative; /reload-plugins; update command; prerequisite list per README §What you need.

Backend: needs

• content-cms — typed build-time content layer: design/* artifacts rendered in the reading room, ROSTER.md transcribed to data, RECEIPTS.json read at build; MDX/typed-collections territory, no runtime CMS.

Backend: rejected

• database/auth — pre-committed: no accounts, no database; static derivation.
• server-actions/email/forms — no forms; conversion is copy-to-clipboard + outbound links.
• payments/storage/api-design — nothing sold, nothing uploaded, no external callers.
• analytics/consent — zero third-party requests, zero cookies (itself a receipt: nothing to consent to); correctable later via iterate.
• AI features — default reject; nothing in the brief demands one.

Assumed facts

• Site identity: lowercase "ultraweb" wordmark, invented by identity (no mark exists — ASSETS.md).
• The human in the loop appears as "the client," decisions dated; footer credit "Built by Iwan Braun" per README.
• Domain stays ultraweb-site.vercel.app; no custom domain work.
• No analytics of any kind (zero third-party requests as a stated performance/privacy receipt).
• AI-crawler policy: allow — being quotable by assistants is distribution for a dev tool (final call recorded in SEO.md, Phase 10).
• Command palette (⌘K) earned by the roster's real content depth — accelerator over nav, never the only path.
• Losing mockups: screenshot on the page + the untouched original HTML served statically, linked ("view the real artifact").
• Route names may be polished by copywriting; page set and jobs are fixed.