localwebdevlisted

Build a static "revamp site" for the business in `$ARGUMENTS` and deploy it to its own Cloudflare Pages project. This is John's client-demo pipeline — the goal is a live `<slug>.pages.dev` URL he can flip open on an iPad and use to close the client / justify higher rates. After deploy, record the business in John's CRM (§6). `$ARGUMENTS` = a business URL followed by free-text context (Google reviews, existing site copy, notes). Parse the URL out; treat the rest as source material. If no URL is given, ask for one before proceeding. ## 0. Pick a project slug Derive a short kebab-case slug from the business name (e.g. "Liliana's Hair Salon" → `hairbyliliana` or `lilianas-hair-salon`). This is the Cloudflare Pages project name AND the working dir name. It becomes `<slug>.pages.dev`. Keep it lowercase, alphanumeric + hyphens, ≤ 58 chars. ## 1. Analyze the real business FIRST (agent) Spawn ONE agent (general-purpose) to extract the real brand + business facts. Do not guess or fabricate — a wrong phone number or fake price is worse than omitting it. Have it pull, with exact values and source URLs: - **Logo** image URL(s); download them to the scratchpad and note colors/style. - **Brand colors** (hex) and **fonts** from the live site's CSS/theme config. - **Services & prices** — exact names + amounts. Many small businesses use Square/Fresha/Vagaro; the booking widget's JSON is the authoritative catalog (more reliable than scraping). If prices are "varies", say so. - **Business inf