sproutkit-code 1.3.0 → 1.5.0

package/dist/commands/sproutkit-book.md

@@ -0,0 +1,18 @@
+---
+description: Build a booking site (for a lead, or any business by name)
+argument-hint: "<leadId> | \"Business Name, Town\" [--standalone]"
+allowed-tools: Bash(sproutkit *)
+---
+Build a booking site. The operator asked: $ARGUMENTS
+
+Use `sproutkit book`. Notes:
+- A lead id adds booking onto a site Sproutkit already built (same domain, /book).
+- `--standalone` gives a booking site on its OWN url — for a client who already
+  has their own website and just needs bookings.
+- A business NAME instead of an id works even if they aren't a lead yet: it looks
+  them up, reads their site, and builds a booking page in one shot.
+- `--archetype slots|reservation|enquiry`, `--instructions "…"`, `--email owner@x`.
+
+Booking sites include a client `/admin` panel. The result carries `adminUrl` and
+`adminPassword` — ALWAYS pass both on to the operator. The password is shown only
+at build time, so if you swallow it the client can't log in.

package/dist/commands/sproutkit-build.md

@@ -0,0 +1,18 @@
+---
+description: Build a demo website for a lead
+argument-hint: "<leadId> [--multipage] [instructions]"
+allowed-tools: Bash(sproutkit *)
+---
+Build a site. The operator asked: $ARGUMENTS
+
+Use `sproutkit build <leadId>`. Notes:
+- `--multipage` gives real separate pages instead of one long scroll.
+- Put any styling or content steer in `--instructions "…"`.
+- `--skip-qa` only if they want speed over polish.
+- No lead id given? Show `sproutkit list --status discovered` and ask which one.
+
+Every generated site carries a DEMO banner by design — that's what stops clients
+using the free preview as their real site. Don't try to remove it here; that's
+what `/sproutkit-handover` does once they've paid.
+
+When it's done, give the operator the live URL.

package/dist/commands/sproutkit-find.md

@@ -0,0 +1,15 @@
+---
+description: Find local businesses with no website (or no online booking)
+argument-hint: "[area] e.g. Leeds LS1, or \"Swansea --no-booking\""
+allowed-tools: Bash(sproutkit *)
+---
+Find new leads. The operator asked for: $ARGUMENTS
+
+Run `sproutkit find` with that area. Notes:
+- Default finds businesses with NO website. If they mention booking, WhatsApp
+  bookings, or "has a site already", add `--mode no_booking` instead.
+- Pass `--categories` only if they named specific trades.
+- Results stream in as each category returns, so let it finish before summarising.
+
+Then report how many were found and the most promising few, with a one-line
+reason each. Don't build anything yet.

package/dist/commands/sproutkit-handover.md

@@ -0,0 +1,22 @@
+---
+description: Hand a finished site to a paying client (removes the DEMO banner)
+argument-hint: "<leadId> [--domain thesalon.co.uk]"
+allowed-tools: Bash(sproutkit *)
+---
+Hand over a site. The operator asked: $ARGUMENTS
+
+This is the PAID-DELIVERABLE step. It removes the DEMO banner from a live site,
+attaches the client's domain, and marks the lead won. The banner is what stops a
+client using a free preview as their real site, so:
+
+1. Confirm the operator is telling you this client has PAID or signed off. If
+   that isn't explicit, ask — don't infer it from the site looking finished.
+2. Then run `sproutkit handover <leadId> --yes` (add `--domain x.co.uk` if given).
+   The command refuses without `--yes` by design.
+
+Afterwards, relay the whole credentials sheet verbatim: site URL, /admin panel
+and password, booking page and its password, and any DNS records the client has
+to set at their registrar. That output is the client handover — don't summarise
+the passwords away.
+
+To re-check whether a domain's DNS has propagated, run the same command again.

package/dist/commands/sproutkit-leads.md

@@ -0,0 +1,16 @@
+---
+description: Show current leads and their stage
+argument-hint: "[filter] e.g. site_built, or Leeds"
+allowed-tools: Bash(sproutkit *)
+---
+Leads:
+
+!`sproutkit list --compact 2>/dev/null`
+
+The operator asked to see: $ARGUMENTS
+
+Every lead is listed above (one JSON object per line, nothing truncated).
+
+Show the matching leads as a compact table — id, name, town, stage, and whether
+they have a site / booking page. If they didn't narrow it down, group by stage.
+Read-only: don't build, contact, or change anything.

package/dist/commands/sproutkit-outreach.md

@@ -0,0 +1,17 @@
+---
+description: Prepare outreach messages for leads with a built site
+argument-hint: "[--ids 3,5] [--channel sms|whatsapp|email]"
+allowed-tools: Bash(sproutkit *)
+---
+Prepare outreach. The operator asked: $ARGUMENTS
+
+This CONTACTS REAL BUSINESSES and moves leads to Contacted, so:
+
+1. First run `sproutkit list --status site_built --json` and show exactly who is
+   about to be contacted, with a count.
+2. Ask the operator to confirm before running `sproutkit outreach`.
+3. Only then run it. Never add `--ids` you invented — use the ones they gave.
+
+Routing is per-lead automatically: mobile number → SMS/WhatsApp, otherwise email
+(harvesting the address if needed). Only pass `--channel` if they asked for a
+specific one.

package/dist/commands/sproutkit-pipeline.md

@@ -0,0 +1,20 @@
+---
+description: Run the full pipeline — build then prepare outreach, in parallel
+argument-hint: "[x3] [--book] [--limit 10]"
+allowed-tools: Bash(sproutkit *)
+---
+Run the pipeline. The operator asked: $ARGUMENTS
+
+This builds sites AND prepares outreach to real businesses, for many leads at
+once. Before running:
+
+1. Show which leads are queued (`sproutkit list --status discovered --json`) and
+   the count.
+2. Confirm with the operator.
+3. Run `sproutkit pipeline x<N>` where N is the concurrency they asked for
+   (default 3). Add `--book` to include a booking page, `--limit`/`--ids` to
+   scope it.
+
+It prints a live board and can be stopped with the stop key. When it finishes,
+report how many succeeded, and pass on any client admin panel credentials it
+printed.

package/dist/commands/sproutkit.md

@@ -0,0 +1,15 @@
+---
+description: Sproutkit — show the pipeline and what to do next
+allowed-tools: Bash(sproutkit *)
+---
+Current pipeline:
+
+!`sproutkit list --compact 2>/dev/null`
+
+Setup check:
+
+!`sproutkit doctor 2>&1 | tail -20`
+
+Summarise the pipeline for the operator in a few lines: how many leads at each
+stage, and the single most useful next action. Mention any setup problem the
+doctor output reveals. Don't run anything else unless asked.