create-ailk 0.6.1 → 0.7.0

package/templates/.claude/skills/{provision-config → setup-deploy}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: provision-config
+name: setup-deploy
 description: Emit deploy configuration for an AILK consumer site — `vercel.json`, `.env.example`, and `RUNBOOK.md`. Vercel-only at v1; other platforms reject with a clear "not yet supported" message. Use when the user asks "set up Vercel", "provision deploy config", "what env vars do I need for production?", "I'm ready to ship to Vercel", or otherwise asks about pre-deploy file setup. The RUNBOOK includes the three named persistence-upgrade paths for leads.jsonl (Vercel KV / Supabase / Postgres-via-`@working-theory/database`).
 ---
 
-# provision-config
+# setup-deploy
 
 Emit `vercel.json`, `.env.example`, and `RUNBOOK.md` at the consumer's
 project root, ready for a Vercel deploy. Vercel is the only valid
@@ -64,7 +64,7 @@ Skip this skill when:
 Default platform is `vercel`. If the consumer asks for any other
 platform, respond:
 
-> "`provision-config` is Vercel-only at v1. Netlify / Cloudflare /
+> "`setup-deploy` is Vercel-only at v1. Netlify / Cloudflare /
 > Render / Fly / self-host support are tracked at the upstream repo —
 > file an issue at <https://github.com/working-theory-labs/ai-launch-kit/issues>
 > if your platform is missing.
@@ -100,7 +100,7 @@ Wait for the consumer's choice per file. Do not blindly overwrite.
 **Merge logic — `.env.example`:** if a var listed in
 `references/env-vars-template.md` is **missing** from the existing
 file, append it (with comment) at the bottom under a "## Added by
-provision-config" section. Vars already present are not modified.
+setup-deploy" section. Vars already present are not modified.
 
 **Merge logic — `RUNBOOK.md`:** if any of the three named
 persistence sections (Vercel KV, Supabase,
@@ -144,7 +144,7 @@ NextAuth secrets.
 After write, count the declared vars and confirm the count matches
 the template's expected count. If a var the consumer's site uses
 (grep `process.env.X` from a quick scan) is missing from the
-template, add it under "## Added by provision-config" — never silently
+template, add it under "## Added by setup-deploy" — never silently
 omit a var the consumer needs.
 
 ### Step 6 — Emit `RUNBOOK.md`
@@ -168,7 +168,7 @@ runbook has these sections:
    RDS). When to pick.
 6. **Custom domain + DNS** — pointer at Vercel's domain docs.
 7. **Production callbacks for OAuth** — for consumers who used
-   `scaffold-auth` (#364) and need to register prod redirect URIs.
+   `add-auth` and need to register prod redirect URIs.
 
 After write, grep the RUNBOOK for the three named persistence
 section headings (Vercel KV, Supabase,
@@ -214,7 +214,7 @@ If any check fails, surface the failure to the consumer (not silent).
   `vercel deploy`'s job.
 - That env-var values in the consumer's Vercel dashboard are
   correct or live. The skill never reads dashboard state.
-- That OAuth callback URLs in `scaffold-auth`'s RUNBOOK are
+- That OAuth callback URLs in `add-auth`'s RUNBOOK are
   registered in production OAuth apps. That's the consumer's job
   pre-launch.
 
@@ -228,7 +228,7 @@ If any check fails, surface the failure to the consumer (not silent).
 
 ## Coordination
 
-- **`scaffold-auth` (#364)** — produces its own `RUNBOOK.md`
+- **`add-auth`** — produces its own `RUNBOOK.md`
   sections for OAuth setup (dev callback URLs). This skill's
   RUNBOOK adds production callback URLs and merges with any
   existing runbook content (not blindly overwrites).

package/templates/.claude/skills/{provision-config → setup-deploy}/references/env-vars-template.md

@@ -1,6 +1,6 @@
 # `.env.example` Template
 
-The structure the `provision-config` skill emits at the consumer's
+The structure the `setup-deploy` skill emits at the consumer's
 project root. Placeholder values only — the skill never echoes a
 real secret.
 
@@ -177,7 +177,7 @@ Step 3) offers merge / overwrite / skip. Merge logic:
 4. Vars **missing** are appended at the end of the existing file
    under a new section:
    ```
-   # ── Added by provision-config ────────────────────────────────
+   # ── Added by setup-deploy ────────────────────────────────
    ```
 
 This avoids duplicating vars while still surfacing additions the

package/templates/.claude/skills/{provision-config → setup-deploy}/references/runbook-template.md

@@ -1,6 +1,6 @@
 # `RUNBOOK.md` Template
 
-The `provision-config` skill emits this runbook at the consumer's
+The `setup-deploy` skill emits this runbook at the consumer's
 project root. It documents pre-deploy steps, the **critical**
 leads-persistence caveat, and the three named upgrade paths.
 
@@ -13,12 +13,12 @@ missing, the skill has a bug.
 ```markdown
 # RUNBOOK — Production Operations
 
-This runbook is generated by the `provision-config` skill. It covers
+This runbook is generated by the `setup-deploy` skill. It covers
 what to do before and after deploying to Vercel, plus the
 operational caveats AILK ships with.
 
-If you re-run `provision-config`, new sections may be appended at
-the end under "## Added by provision-config." Existing sections are
+If you re-run `setup-deploy`, new sections may be appended at
+the end under "## Added by setup-deploy." Existing sections are
 not modified by the skill.
 
 ---
@@ -40,7 +40,7 @@ Before you click Deploy in Vercel:
       your site captures leads. AILK's default `leads.jsonl`
       fallback does not persist on Vercel's ephemeral filesystem.
 - [ ] **Register production OAuth callbacks** if you used
-      `scaffold-auth` and activated Google or GitHub. Each provider
+      `add-auth` and activated Google or GitHub. Each provider
       needs the prod callback URL added to its OAuth app settings.
 
 ---
@@ -160,9 +160,9 @@ Domains → Add → DNS records → wait for verification.
 
 ---
 
-## Production callbacks for OAuth (if you used `scaffold-auth`)
+## Production callbacks for OAuth (if you used `add-auth`)
 
-If you activated Google or GitHub OAuth via `scaffold-auth` (#364),
+If you activated Google or GitHub OAuth via `add-auth`,
 those activations used dev callback URLs (`localhost:3000`). For
 production, add the prod callback URLs to each OAuth app:
 
@@ -240,7 +240,7 @@ Step 3) offers merge / overwrite / skip. Merge logic:
 3. Headings already present → not modified.
 4. Headings missing → append at the end of the existing file under:
    ```
-   ## Added by provision-config
+   ## Added by setup-deploy
    ```
 
 The pre-deploy checklist, custom-domain, and OAuth-prod-callbacks

package/templates/.claude/skills/{provision-config → setup-deploy}/references/vercel-json-template.md

@@ -1,6 +1,6 @@
 # `vercel.json` Template
 
-The minimal viable Vercel config the `provision-config` skill emits.
+The minimal viable Vercel config the `setup-deploy` skill emits.
 Customization beyond this template is the consumer's responsibility —
 the skill's job is to ship the consumer with a working baseline.
 

package/templates/.claude/skills/upgrade-plan/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: upgrade-plan
+description: Explain the AI Launch Kit options — Free, Pro, Pro Plus, Agency and the commerce add-on's three rungs (Commerce, SaaS, SaaS with Usage) — side by side, with the prices the public pricing page publishes right now, read this site's own modules and shape, and recommend exactly one option with a reason. Use when the user asks "what does Pro get me?", "should I upgrade?", "compare plans", "which plan do I need?", "how much is commerce?", or types /upgrade-plan. The skill reads and explains only — it never buys, never installs, and never states a price from memory.
+---
+
+# upgrade-plan
+
+Answer "what does a paid level get me, and which one should I buy?" from two
+live sources: the public pricing page (for prices) and this repository (for
+what the site actually uses). A bundled helper does the reading and the
+choosing; this skill runs it and explains the result in plain words.
+
+## When to use
+
+- "what does Pro get me?" / "what's in Pro Plus?"
+- "should I upgrade?" / "which plan do I need?"
+- "compare the plans" / "how does Agency work?"
+- "can I sell things on my site?" / "how much is the commerce add-on?"
+- `/upgrade-plan`
+
+Skip this skill when the user wants to actually buy or install something —
+this skill explains and recommends; the purchase happens on the pricing
+page, and installing a module is a separate step (see "What happens next").
+
+## The mechanic
+
+### Step 1 — Map the user's stated need (optional)
+
+If the user said what they want to do, map it to one `--need` value:
+
+| The user says…                                    | `--need`       |
+| ------------------------------------------------- | -------------- |
+| "I build sites for clients"                        | `agency`       |
+| "I want to sell / take payments"                   | `sell`         |
+| "my product bills its own customers on plans"      | `saas`         |
+| "I bill my customers by usage / credits"           | `usage`        |
+| "I need docs or a blog"                            | `docs`         |
+| "I need booking / scheduling"                      | `scheduling`   |
+| "I need organizations / teams / many workspaces"   | `multi-tenant` |
+
+If the need maps to none of these, omit `--need`, and tell the user which
+need you could not map — the recommendation then comes from the site alone.
+
+### Step 2 — Run the helper
+
+From the project root:
+
+```bash
+pnpm exec tsx .claude/skills/upgrade-plan/scripts/upgrade-plan.ts [--need <value>]
+```
+
+It prints one JSON object:
+
+- `pricing.status` — `ok` (the page published prices), `unpublished` (the
+  page loaded but carries no machine-readable offers) or `unreachable`
+  (network error, timeout or error status). `pricing.url` is the link to give
+  the user.
+- `options[]` — the seven options, always all seven, each with `adds`,
+  `requires`, and `prices[]` (empty, with `status: "not published on the
+  pricing page"`, when the page does not price it).
+- `alsoPublished[]` — other offers on the pricing page that are none of the
+  seven (for example a one-off service), with their published price.
+- `site` — this site's `modules`, `template`, `shape`, `design`, whether it
+  already prices something (`sellsSomething`), whether commerce is installed,
+  and whether `AILK_LICENSE_KEY` is set in this shell (`licenseKeySet` —
+  presence only, never the value).
+- `recommendation` — one `option`, its `reason`, and its `link`.
+
+Exit status 0 in all three pricing states. Exit 2 is a usage error — re-run
+without the argument it names.
+
+### Step 3 — Explain it
+
+Answer in this order, in plain words:
+
+1. **Your site.** State the shape and the modules from `site`, the template
+   and design when recorded, whether it already prices anything, and whether
+   a licence key is set in this shell. A `null` field is "not recorded —
+   scaffolded without `--template`"; never guess a shape. If the key is not
+   set, say "not set in this shell" (a key kept only in `.env` reads that way).
+2. **The options, side by side.** A table of all seven options: name, what it
+   adds, what it requires, and its price exactly as `prices[]` gives it
+   (figure, currency and unit text). An option with no price reads
+   "not published on the pricing page — see https://ailaunchkit.ai/pricing".
+   Then list `alsoPublished` under "Also on the pricing page".
+3. **The recommendation.** Exactly one option — `recommendation.option` —
+   with its reason, naming the module or need that decided it. Do not offer a
+   second recommendation; you may say what would change it (for example "if
+   you add multi-tenant later, that moves you to Pro Plus").
+4. **What happens next.** Link `recommendation.link`. After purchase the
+   licence key arrives by email; set it as `AILK_LICENSE_KEY` in your
+   environment. To install the module(s): run
+   `pnpm dlx create-ailk@latest --help`, and name `add-module` only if that
+   output lists it. Otherwise say: re-run `create-ailk` with
+   `--modules <module>` and the key set, into a new directory, and move your
+   content across.
+
+## Hard rules
+
+- **Never state a price that is not in the helper's output for this run.**
+  Not from memory, not from an earlier run, not from another page, not as an
+  estimate or a range. A price appears in your answer only if it appears in
+  this run's `options[].prices` or `alsoPublished`.
+- **Unreachable means no prices.** When `pricing.status` is `unreachable`,
+  say the pricing page could not be reached, give no price for any option,
+  and link https://ailaunchkit.ai/pricing. Still show the site and the
+  recommendation — neither depends on a price.
+- **Unpublished means no prices.** When `pricing.status` is `unpublished`,
+  say the pricing page does not publish machine-readable prices yet and link
+  https://ailaunchkit.ai/pricing.
+- **Read-only.** Write no file and install nothing. The only outside command
+  besides the helper is the `--help` probe in step 3.
+- **Never print the licence key.** Report only whether it is set.
+
+## References
+
+- `references/options.md` — the seven options in plain words.

package/templates/.claude/skills/upgrade-plan/references/options.md

@@ -0,0 +1,24 @@
+# The options
+
+What each option adds and what it requires, in plain words. Names and
+structure only — prices come from https://ailaunchkit.ai/pricing at run time,
+never from this file.
+
+Source: the AI Launch Kit product vocabulary (Commerce; Packaging and
+delivery). Levels are Free, Pro and Pro Plus; Agency is an agreement, not a
+level; Commerce, SaaS and SaaS with Usage are the three rungs of the one
+commerce add-on, bought on top of a level.
+
+| Option              | What it adds                                                                                                                         | Requires                                  |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------- |
+| **Free**            | The open-source base: the website, its API and MCP server, and the marketing module. Every site is agent-discoverable at this level. | Nothing — no licence key                  |
+| **Pro**             | The paid modules for one site — docs and blog, scheduling, signal collectors, the Admin app — kept current.                    | A licence key for the site                |
+| **Pro Plus**        | Everything in Pro, plus the multi-tenant module: organizations, workspaces and members.                                              | A licence key for the site                |
+| **Agency**          | A reseller agreement for building sites for clients. Not a bigger level.                                                             | Each client site is licensed Pro or Pro Plus |
+| **Commerce**        | Checkout, payment links, hosted invoices, subscriptions and the customer portal, through your own Stripe account.                    | Any paid level (Pro or Pro Plus)          |
+| **SaaS**            | Commerce plus plans, trials, coupons and entitlements mapped to feature flags — for a product that bills its tenants.                | Pro Plus                                  |
+| **SaaS with Usage** | SaaS plus usage metering, prepaid credits, overage and spend limits.                                                                  | Pro Plus                                  |
+
+Payment always happens on a Stripe-hosted page; the site never renders a card
+form. Paid bookings (deposits, no-show holds) belong to the scheduling module,
+not to Commerce.