site-launchlisted

# Site Launch Concept → live branded landing page on a real domain, in one pass. This is the codified version of a run that worked end to end; the fiddly API parts are scripts under `scripts/` so you don't re-derive them. **Two standing rules, every run:** - **Confirm before money or DNS.** Buying a domain and changing DNS are outward, hard-to-undo. State what you're about to do and get an explicit yes. - **Verify after every external change** — read it back. `verified:true` from an API is a claim; `curl` the live URL, re-GET the DNS zone, test-submit the form. Motion is not mutation. ## Credentials (never paste in chat) Read from env; keep them in a gitignored file the user sources, e.g. `~/.config/site-launch/env`: ```bash export VERCEL_TOKEN=vcp_... # ACCOUNT token (vcp_), NOT an AI-Gateway key (vck_) — see below export SPACESHIP_API_KEY=... # X-API-Key export SPACESHIP_API_SECRET=... # X-API-Secret (Spaceship needs BOTH) ``` If a key is missing, ask for it and tell the user exactly where to make it. Never echo a key in command output. ## The pipeline ### 1. Frame the concept One line: what it is, who it's for, the single CTA (email signup? book a call? buy?). Everything downstream serves that one job. ### 2. Name + domain → `domain-scout` Invoke the **domain-scout** skill to generate candidates, check availability across TLDs/variants, screen for existing-company collisions, and rank. Present the shortlist; the user picks. Prefer