← back to Claude Webdev Accelerator
ACCELERATOR.md
81 lines
# Claude Web-Dev Accelerator — Playbook
The single playbook a Claude Code session follows to take a client idea from
"link in Slack" to a **prototyped, verified, launch-ready web project** — by
composing the skills and agents already in this stack instead of hand-rolling
each build. Launched from the Idea Board's **🚀 Launch Web-Dev Accelerator**
button (or any "Build new project ▶" action), which opens a fresh session in
this directory pointed at this file.
## North star
Rapidly prototype and launch **high-value client projects**. Optimize for:
time-to-first-clickable-prototype, reuse over rewrite, and a hard verify gate
before anything is shown to a client or made public.
## The pipeline (each phase names the skill/agent that does the work)
### 0 · Intake — turn the idea into a one-paragraph brief
- Capture: who's the client, what outcome, what's the "high value" (revenue,
time saved, deal won), any hard constraints (brand, domain, deadline).
- If the seed is a URL, run **/site-audit** (competitor/reference teardown) and
**/competitors** to find the differentiation vector before building anything.
- Output: `BRIEF.md` in the new project dir. Stop and confirm the brief with
Steve if the outcome or scope is ambiguous — cheap to ask, expensive to guess.
### 1 · Design direction — pick a look, don't invent one blind
- **/mockups `<ref-url>` `<n>`** — N distinct front-page directions, not reskins.
- **four-horsemen** / **/stampede** — elevated graphic variants (Figma · 21st ·
Paper · Canva) when the client needs real creative range.
- **/logo-agent** — tournament-pick a brand mark when one's needed.
- Reference libraries: **dw-fashion-templates** (luxury visual systems),
**interior-designer** + **graphic-designer** (advisory critique).
### 2 · Scaffold — stand the project up
- `scripts/new-project.sh <slug>` — creates `~/Projects/<slug>`, gitifies it
(per the standing rule), drops `.gitignore`, a server, and a product/content
grid honoring the house rules (**sort + density slider**, **admin cards show
created date+time**).
- Storefront/catalog shape → **dw-site-build** conventions + **sort-skill**.
- Distinctive front page → **rotating-hero-page** + **hero-readability-auditor**
(binary contrast gate) then **frontend-design** for the build itself.
### 3 · Build — implement the brief
- Route pure engineering through the cabinet: **vp-engineering** (and its
frontend-developer / fullstack-developer / backend-architect directors).
- Keep commits atomic; commit after every working step (author
`steve@designerwallcoverings.com`). Never push to a remote by default.
### 4 · Verify — prove it works before anyone sees it
- **/5x** — six-way verification that self-heals (HTTP + headless render +
Playwright E2E + Chrome/Safari/Firefox + clickthrough, fixing on each sweep).
- **/cta** — click through every component across real browsers.
- **/contrarian** — adversarial red-team gate; do not call it "done" until it
signs off. **/validation-loop** — re-run the review after applying fixes.
### 5 · Preview — put it in front of Steve
- **/viewer** (or **rotating-hero** demo) on a free port behind basic auth
`admin / DW2024!`. Optionally a **cloudflared tunnel** to a
`<slug>.agentabrams.com` subdomain (same pattern as `ideas.` / `govarbitrage.`)
— gate internal-content previews with basic auth.
### 6 · Launch — GATED, never autonomous
The accelerator scaffolds everything **one switch away from live** and stops.
These are Steve-only and draft to `~/.claude/yolo-queue/pending-approval/`:
- **/deploy** to Kamatera, DNS/domain changes, publishing, send-to-list, any
spend, remote pushes. Surface the exact command; do not run it.
## Hard rails (inherited from the global standing rules)
- Gitify before >3 files. Commit each success. `.gitignore` excludes
`node_modules/`, `.env*`, `tmp/`, `*.log`, `.DS_Store`, `dist/`, `build/`.
- Show the **$ cost** of every paid-API step inline (`$0 (local)` for local work).
- Prefer **local models** (Ollama/ComfyUI) for generation; Replicate is opt-in.
- Every product grid gets sort + density; every admin card gets created date+time.
- Deploy / DNS / publish / spend are **ask-up-front**, not `/dtd`-and-go.
## Files
- `ACCELERATOR.md` — this playbook (the session entry point).
- `scripts/new-project.sh` — scaffold a new gitified client project.
- `templates/` — starter server + grid honoring the house rules.
- `clients/` — per-engagement briefs & notes (gitignored if sensitive).