/build-website
Agent 1: Client Website Builder (any industry)
Builds and deploys a bespoke Next.js website for a business client in any industry — imported verbatim from the business-studio repo (Phase 2) and adapted for the monorepo.
verified (imported 8396511dd50446c2324c8c5b2a2d90e1e996fb97)v0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #98 — Import business-studio agents · verbatim import from the staged copy; no client data
Shares that number with /new-client, /build-walkthrough, /build-flyover.
Example requests
- “build a website”
- “build the site”
- “redo the website”
- “update the client site”
- “make the hero darker”
What it needs, and what it hands back
Needs connected
- github
- vercel
Better with: openart.
Uses mcp__github__*, Vercel MCP (create_git_project, list_deployments, get_deployment_build_logs), which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- a live site-<business-slug> repo + Vercel deployment
Stops and asks
- logo generation credit spend when no logo exists anywhere
Steps it cannot do through an API, and hands you instead: Vercel dashboard Import fallback if create_git_project is unavailable/denied; GitHub empty-repo creation fallback on a 403.
How it runs
These are the headings of its own written instructions — 332 lines you can read and change.
- Step 0 — Environment check + client folder bootstrap
- Step 1 — Research & collect
- Step 2 — Brand & logo
- Step 3 — Design direction (bespoke per client)
- Step 4 — Build & ship
Trades whose playbook recommends it
Airbnb hostsElectriciansGeneral contractorsRental car companies