For TTV members fluent in Claude Code + Skills + Plan Mode. You don't just build a site — you build the kit that builds every site after.
The basic run sheet walks you through one site, prompt by prompt. This is for the next layer up: a single brief instead of five paste-ins, Plan Mode for everything, and a Skills folder you copy to every future project. The kit IS the deliverable.
Hand the designer a brand bible + a brief. It plans, you approve, it builds. No re-explaining your voice every session.
Copy the kit to a new project, drop in a new brand bible, get a new site. Works for your business. Works for client work.
Designer always plans before writing code. You catch wrong directions early — not after 30 minutes of cleanup.
The kit drops 5 Skills into your project's .claude/skills/ folder. Claude Code auto-discovers them. From there, every interaction follows the same shape.
One paragraph. Brand bible + pages wanted + tone direction.
Designer plans sections, components, copy. You approve or refine.
Page by page. Plan-Mode-first each time. Match brand. Log decisions.
"Deploy." Designer commits, pushes, verifies Vercel. Done.
"Design an update." Same shape, every time. Forever.
The basic run sheet is 4 hours, one site. This is the version where you build the toolkit while you build the site. The compounding starts the second time you use it.
Site live + kit set up + Skills installed. Done before lunch.
New brand bible → designer adapts → live URL. Most of the heavy lifting is in the kit, already done.
"Design an update — change X." Plan Mode is instant. Deploy is automatic.
Every Skill is a SKILL.md file with a clear job. Claude Code reads them when relevant. You can invoke them by name or just describe what you want.
Master orchestrator. Routes your request to the right specialist. Always plans first. "Design my site" kicks it off.
Single-page builds. Reads brand bible + components, plans, gets approval, writes the HTML/CSS.
Audits pages against brand voice + anti-patterns. Reports drift. Waits for approval before patching.
Apply a new palette across the site. Updates CSS vars + finds hardcoded colours. Logs the decision.
Git commit + push + verify Vercel auto-deploy. Plans the commit message, gets approval, ships.
CLAUDE.md, design-system.md, components.md, anti-patterns.md, palettes.md, fonts.md, seo-checklist.md. The designer reads from these.
Two of these you'll already have if you've done the basic workshop. The other three are quick.
claude --version to check.gh auth login done so push works.reference/voice-guide.md. The designer will use it as the authoritative voice reference.Skills · reference docs · templates · sample brand bible. Drop it into a folder, run claude, brief the designer.
The non-Claude-Code version. Five paste-in prompts, no Skills required.
Open basic run sheetIf you're new to Claude Skills, start here. Builds the foundation this workshop assumes.
Open Skills 101Bring your live site to monthly coaching calls. Get real feedback. Keep iterating.
Join TTV