web-studiolisted

# web-studio Orchestration only — this skill does not itself design or write code. It asks the questions in order, dispatches each stage to the right tool, and enforces the gates. The creative judgment lives in the `the-designer` agent; the build lives in Claude; validation lives in a second model. ## Setup check (once per environment — confirm, don't assume) 1. **The Designer**: confirm `the-designer` is a registered subagent (new files in `~/.claude/agents/` register at session start, not mid-session). 2. **Second model** (stages 4/6 — optional): if the OpenAI Codex CLI is installed, verify with `codex exec --skip-git-repo-check "reply OK" < /dev/null`. Any other model CLI works if it can take a prompt and return text synchronously. **If none is available: run those checks yourself, mechanically, and say so in the receipt** — don't skip them, don't pretend a second model ran. 3. **Image generation** (stage 3 — optional): any CLI/MCP that can generate an image from a text prompt. If it offers a cost-estimate command, always estimate before creating. If none is available, the site ships with CSS/SVG art direction instead of generated media — note it in the receipt. 4. **Fonts**: check the project's font choices against your font guide's license notes before shipping. Never ship a personal-use-only font on a commercial site. 5. **Studio Memory** (see docs/MEMORY.md): ensure `~/.web-studio/` exists with TASTE.md, PATTERNS.md, FAILURES.m