create-ailk 0.6.1 → 0.8.0

package/site-templates/shapes/person-service/content/en/PortfolioList/portfolio.mdx

@@ -0,0 +1,169 @@
+---
+type: "PortfolioList"
+slug: "portfolio"
+title: "{Before and after, compared} | {Your Name}"
+description: "{Every project shown as a comparison — what the client had, what they have now, and what changed in between.}"
+sections:
+  [
+    {
+      "id": "cases-hero",
+      "type": "hero",
+      "data":
+        {
+          "variant": "default",
+          "size": "display",
+          "surface": "wash-secondary",
+          "gapBelow": "tight",
+          "eyebrow": "{Portfolio}",
+          "eyebrowTone": "brand",
+          "headline": "{My work, before and after.}",
+          "subheadline": "{Two or three sentences on why the comparison is the honest proof — what the before cost the client, what the after changed, and how a reader can check it.}",
+          "subtitleSize": "lead",
+          "ctaSize": "xl",
+          "primaryCta": { "label": "{Book a call}", "href": "/book-a-call" },
+          "secondaryCta": { "label": "{Get in touch}", "href": "/contact" },
+        },
+    },
+    {
+      "id": "cases-tiles",
+      "type": "items",
+      "data":
+        {
+          "variant": "tile",
+          "tileHover": "outline",
+          "columns": 2,
+          "surface": "none",
+          "items":
+            [
+              {
+                "title": "{Example one}: before and after",
+                "description": "{One sentence on what example one had, and what they have now}",
+                "rows":
+                  [
+                    {
+                      "label": "THE CLIENT",
+                      "body": "{Who they are and the market they sell into}",
+                    },
+                    {
+                      "label": "WHAT CHANGED",
+                      "body": "{The one thing the after does that the before could not}",
+                    },
+                  ],
+                "link":
+                  {
+                    "label": "See the comparison →",
+                    "href": "/portfolio/sample-one",
+                  },
+              },
+              {
+                "title": "{Example two}: before and after",
+                "description": "{One sentence on what example two had, and what they have now}",
+                "rows":
+                  [
+                    {
+                      "label": "THE CLIENT",
+                      "body": "{Who they are and the market they sell into}",
+                    },
+                    {
+                      "label": "WHAT CHANGED",
+                      "body": "{The one thing the after does that the before could not}",
+                    },
+                  ],
+                "link":
+                  {
+                    "label": "See the comparison →",
+                    "href": "/portfolio/sample-two",
+                  },
+              },
+              {
+                "title": "{Example three}: before and after",
+                "description": "{One sentence on what example three had, and what they have now}",
+                "rows":
+                  [
+                    {
+                      "label": "THE CLIENT",
+                      "body": "{Who they are and the market they sell into}",
+                    },
+                    {
+                      "label": "WHAT CHANGED",
+                      "body": "{The one thing the after does that the before could not}",
+                    },
+                  ],
+                "link":
+                  {
+                    "label": "See the comparison →",
+                    "href": "/portfolio/sample-three",
+                  },
+              },
+              {
+                "title": "{Example four}: before and after",
+                "description": "{One sentence on what example four had, and what they have now}",
+                "rows":
+                  [
+                    {
+                      "label": "THE CLIENT",
+                      "body": "{Who they are and the market they sell into}",
+                    },
+                    {
+                      "label": "WHAT CHANGED",
+                      "body": "{The one thing the after does that the before could not}",
+                    },
+                  ],
+                "link":
+                  {
+                    "label": "See the comparison →",
+                    "href": "/portfolio/sample-four",
+                  },
+              },
+            ],
+        },
+    },
+    {
+      "id": "cases-close",
+      "type": "cta",
+      "data":
+        {
+          "variant": "beam",
+          "headline": "{Is your project the before or the after?}",
+          "description": "{One line offering the reader the same comparison for their own project.}",
+          "primaryCta": { "label": "{Book a call}", "href": "/book-a-call" },
+          "secondaryCta": { "label": "{Get in touch}", "href": "/contact" },
+          "chips":
+            [
+              "{Proof you can check}",
+              "{Every project shown both ways}",
+              "{Re-checked every quarter}",
+            ],
+        },
+    },
+    {
+      "id": "cases-faq",
+      "type": "faq",
+      "data":
+        {
+          "headline": "Frequently Asked Questions",
+          "variant": "centered",
+          "presentation": "accordion",
+          "questionSize": "body-lg",
+          "initialOpen": "first",
+          "containerWidth": "default",
+          "surface": "gray-100",
+          "items":
+            [
+              {
+                "question": "{How do you pick which projects to show?}",
+                "answer": "{Two or three sentences.}",
+              },
+              {
+                "question": "{Are the before screenshots real?}",
+                "answer": "{Two or three sentences.}",
+              },
+              {
+                "question": "{Can I see the numbers behind a comparison?}",
+                "answer": "{Two or three sentences.}",
+              },
+            ],
+        },
+    },
+  ]
+---

package/site-templates/shapes/person-service/content/en/PurchasePolicyPage/purchase-policy.mdx

@@ -0,0 +1,123 @@
+---
+type: "PurchasePolicyPage"
+slug: "purchase-policy"
+title: "Purchase Policy"
+description: "How cancellations, reschedules and refunds work for engagements booked on this site. Placeholder policy — replace every section before you launch."
+sections:
+  [
+    {
+      "id": "purchase-policy-document",
+      "type": "document-chassis",
+      "data":
+        {
+          "headline": "Purchase Policy",
+          "layout": "article",
+          "updated": "Last updated {Month Day, Year}",
+          "navGroupLabel": "Contents",
+          "sections":
+            [
+              {
+                "id": "cancellation",
+                "heading": "Cancellation",
+                "blocks":
+                  [
+                    {
+                      "kind": "paragraph",
+                      "text": "This page is starter content that shipped with your site. It is not a purchase policy, it makes no commitment on behalf of Your Name, and it is not legal advice. Replace every section with the policy you actually operate, and have someone qualified read it before you publish.",
+                    },
+                    {
+                      "kind": "paragraph",
+                      "text": "This section explains how cancellations and reschedules work for engagements booked on this site. The headings are the ones a client and an agent both look for, so keep them and fill in your own terms.",
+                    },
+                  ],
+                "subsections":
+                  [
+                    {
+                      "id": "notice",
+                      "heading": "How much notice is required",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "State the notice period in hours before the session, and say how it is measured. A client reading at midnight should be able to work out, without arithmetic you have not shown them, whether they are still inside it.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "how-to-cancel",
+                      "heading": "How to cancel or reschedule",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Give one route to cancel and one to reschedule, and say whether a reschedule inside the notice period counts as a cancellation. If a booking confirmation carries a self-service link, name it here.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "fees",
+                      "heading": "Late cancellations and no-shows",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Say what a late cancellation costs and what a no-show costs, as a figure or a share of the engagement, and when each is charged. If you hold a deposit, say what happens to it in each case.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "our-cancellations",
+                      "heading": "If I cancel",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Set out what a client gets if you cancel or move a session — a full refund, a rebooking, or both — and how quickly you tell them. A policy that only binds one side reads as one.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "exceptions",
+                      "heading": "Exceptions",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Name the circumstances in which you waive a fee — illness, bereavement, severe weather — and say what you need from the client to apply the waiver. Vague discretion is worse for you than a short written list.",
+                          },
+                        ],
+                    },
+                  ],
+              },
+              {
+                "id": "refunds",
+                "heading": "Refunds",
+                "blocks":
+                  [
+                    {
+                      "kind": "paragraph",
+                      "text": "Say what a client gets back after a cancellation — the session price, the deposit, or both, and how long the refund takes to reach the payment method it came from. If you offer credit toward a future engagement instead, describe when that applies.",
+                    },
+                  ],
+                "subsections":
+                  [
+                    {
+                      "id": "questions",
+                      "heading": "Questions about a refund",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Point to the one place a client should write, and say roughly how quickly you answer. A policy nobody can ask a question about is a policy that generates disputes.",
+                          },
+                        ],
+                    },
+                  ],
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Service shape (#6646): cancellation and refunds — this template's override of the `_base` product-shape seed. The JSON-LD — a WebPage, wrapping a MerchantReturnPolicy when a returns section is present — is emitted by `buildPurchasePolicyPage` (#6646), not hand-rolled here. */}

package/site-templates/shapes/person-service/content/en/Service/first-engagement.mdx

@@ -0,0 +1,38 @@
+---
+type: "Service"
+slug: "first-engagement"
+title: "{First engagement}"
+description: "{One line on what this engagement is and who it suits. Replace before you launch.}"
+schema:
+  serviceType: "{First engagement}"
+  provider:
+    "@type": Person
+    name: "Your Name"
+---
+
+# {First engagement}
+
+{Open with the situation a reader is in when they come looking for this. Two or
+three sentences, no more — the detail belongs under the headings below.}
+
+## What it covers
+
+- {The first thing you actually do}
+- {The second thing you actually do}
+- {The third thing you actually do}
+
+## How it runs
+
+{One paragraph on the shape of the engagement: how it starts, how long it runs,
+who is involved, and what a week looks like.}
+
+## What you end up with
+
+{One paragraph on the deliverable. Be concrete — name the artefact, not the
+feeling.}
+
+## What it costs
+
+{One line on the pricing shape — fixed fee, retainer, day rate — and what it
+excludes. Replace with your real numbers, or delete this section and let the
+call do it.}

package/site-templates/shapes/person-service/content/en/Service/second-engagement.mdx

@@ -0,0 +1,38 @@
+---
+type: "Service"
+slug: "second-engagement"
+title: "{Second engagement}"
+description: "{One line on what this engagement is and who it suits. Replace before you launch.}"
+schema:
+  serviceType: "{Second engagement}"
+  provider:
+    "@type": Person
+    name: "Your Name"
+---
+
+# {Second engagement}
+
+{Open with the situation a reader is in when they come looking for this. Two or
+three sentences, no more — the detail belongs under the headings below.}
+
+## What it covers
+
+- {The first thing you actually do}
+- {The second thing you actually do}
+- {The third thing you actually do}
+
+## How it runs
+
+{One paragraph on the shape of the engagement: how it starts, how long it runs,
+who is involved, and what a week looks like.}
+
+## What you end up with
+
+{One paragraph on the deliverable. Be concrete — name the artefact, not the
+feeling.}
+
+## What it costs
+
+{One line on the pricing shape — fixed fee, retainer, day rate — and what it
+excludes. Replace with your real numbers, or delete this section and let the
+call do it.}

package/site-templates/shapes/person-service/content/en/Service/third-engagement.mdx

@@ -0,0 +1,38 @@
+---
+type: "Service"
+slug: "third-engagement"
+title: "{Third engagement}"
+description: "{One line on what this engagement is and who it suits. Replace before you launch.}"
+schema:
+  serviceType: "{Third engagement}"
+  provider:
+    "@type": Person
+    name: "Your Name"
+---
+
+# {Third engagement}
+
+{Open with the situation a reader is in when they come looking for this. Two or
+three sentences, no more — the detail belongs under the headings below.}
+
+## What it covers
+
+- {The first thing you actually do}
+- {The second thing you actually do}
+- {The third thing you actually do}
+
+## How it runs
+
+{One paragraph on the shape of the engagement: how it starts, how long it runs,
+who is involved, and what a week looks like.}
+
+## What you end up with
+
+{One paragraph on the deliverable. Be concrete — name the artefact, not the
+feeling.}
+
+## What it costs
+
+{One line on the pricing shape — fixed fee, retainer, day rate — and what it
+excludes. Replace with your real numbers, or delete this section and let the
+call do it.}

package/site-templates/{simple-service → shapes/person-service}/content/en/ServicesList/services.mdx

@@ -2,7 +2,7 @@
 type: "ServicesList"
 slug: "services"
 title: "Services"
-description: "The three jobs {your company} does, each with its own price. Placeholder copy — replace before you launch."
+description: "The three engagements {Your Name} offers. Placeholder copy — replace before you launch."
 sections:
   [
     {
@@ -12,44 +12,44 @@ sections:
         {
           "variant": "centered",
           "eyebrow": "Services",
-          "headline": "Three jobs, three prices",
+          "headline": "Three ways to work together",
           "subheadline": "{One line on how to choose between them. Name the question a reader is actually asking.}",
         },
     },
     {
-      "id": "jobs",
+      "id": "engagements",
       "type": "items",
       "data":
         {
-          "headline": "What we do",
+          "headline": "Engagements",
           "columns": 3,
           "items":
             [
               {
-                "title": "{Lawn maintenance}",
-                "description": "{One line on the recurring visit — what it includes and how often it runs.}",
+                "title": "{First engagement}",
+                "description": "{One line on what it is and who it suits.}",
                 "link":
                   {
                     "label": "Read more",
-                    "href": "/services/lawn-maintenance",
+                    "href": "/services/first-engagement",
                   },
               },
               {
-                "title": "{Seasonal cleanup}",
-                "description": "{One line on the spring and autumn clear-down.}",
+                "title": "{Second engagement}",
+                "description": "{One line on what it is and who it suits.}",
                 "link":
                   {
                     "label": "Read more",
-                    "href": "/services/seasonal-cleanup",
+                    "href": "/services/second-engagement",
                   },
               },
               {
-                "title": "{Landscape design}",
-                "description": "{One line on the design-and-plant job, and what a customer ends up with.}",
+                "title": "{Third engagement}",
+                "description": "{One line on what it is and who it suits.}",
                 "link":
                   {
                     "label": "Read more",
-                    "href": "/services/landscape-design",
+                    "href": "/services/third-engagement",
                   },
               },
             ],
@@ -62,11 +62,11 @@ sections:
         {
           "variant": "minimal",
           "headline": "Not sure which one?",
-          "description": "{One line inviting the reader to book the visit instead of guessing.}",
-          "primaryCta": { "label": "Book a visit →", "href": "/meet" },
+          "description": "{One line inviting the reader to ask instead of guessing.}",
+          "primaryCta": { "label": "Book a call", "href": "/book-a-call" },
         },
     },
   ]
 ---
 
-Placeholder copy. The three detail pages under `content/en/Service/` carry the long form and the price; this page is the chooser.
+Placeholder copy. The three detail pages under `content/en/Service/` carry the long form; this page is the chooser.

package/site-templates/shapes/person-service/provenance.json

@@ -0,0 +1,4 @@
+{
+  "template": "person-service",
+  "requires": ["marketing"]
+}

package/templates/.claude/settings.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "cd \"$CLAUDE_PROJECT_DIR\" && [ -x node_modules/.bin/tsx ] || exit 0; pnpm --silent architecture >&2 || exit 2"
+          }
+        ]
+      }
+    ]
+  }
+}

package/templates/.claude/skills/README.md

@@ -4,19 +4,20 @@ Skills are reusable Claude Code workflows scoped to this project. Each
 lives in its own subdirectory with a `SKILL.md` describing when to use
 it and how it works.
 
-The six skills below ship with this project. Claude Code discovers
+The seven skills below ship with this project. Claude Code discovers
 them automatically at session start — nothing to install or enable.
 
 ## Available skills
 
-| Skill                 | Purpose                                                                                                 |
-| ---------------------- | -------------------------------------------------------------------------------------------------------- |
-| `suggest-site-pages`  | Recommend a starter set of pages — each tagged with a schema.org type — from a free-text business description. |
-| `scaffold-page`       | Generate a new page: App Router route + MDX content stub + typed JSON-LD, in one confirm-before-write pass. |
-| `add-schema`          | Add or replace schema.org JSON-LD on a page that already exists.                                        |
-| `scaffold-auth`       | Activate auth providers — magic-link via Resend, Google OAuth, GitHub OAuth.                            |
-| `provision-config`    | Emit deploy configuration — `vercel.json`, `.env.example`, and `RUNBOOK.md` — for a Vercel deploy.       |
-| `audit-site`          | Run `ailk-audit --json` and explain the score and findings in plain language.                           |
+| Skill          | Purpose                                                                                                      |
+| -------------- | -------------------------------------------------------------------------------------------------------------- |
+| `add-page`     | Generate a new page: App Router route + MDX content stub + typed JSON-LD, in one confirm-before-write pass. Also documents the `schema:` frontmatter override for adding supplementary structured data to a page that already exists. |
+| `add-auth`     | Activate auth providers — magic-link via Resend, Google OAuth, GitHub OAuth.                                  |
+| `setup-deploy` | Emit deploy configuration — `vercel.json`, `.env.example`, and `RUNBOOK.md` — for a Vercel deploy. Asks where leads go (email or a database) and warns when neither is set. |
+| `setup-database` | Take the site from no database to a working lead inbox: provision Postgres, create the tables, pin the owner, and verify one test message lands in `/leads`. |
+| `check-site`   | Run `ailk-audit --json` and explain the score and findings in plain language.                                 |
+| `fill-page`    | Fill one page's section content from a category profile: labelled sample content (tier 1) or your own first draft from a short intake (tier 2). |
+| `upgrade-plan` | Compare Free, Pro, Pro Plus, Agency and the commerce add-on side by side, with the prices the public pricing page publishes right now, and recommend one option for this site with a reason. |
 
 `scaffold-commerce` is delivered with the commerce module (`--modules commerce`, licensed).
 

package/templates/.claude/skills/{scaffold-auth → add-auth}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: scaffold-auth
+name: add-auth
 description: Activate auth providers (magic-link via Resend, Google OAuth, GitHub OAuth) on an AILK consumer site. Use when the user says "wire up auth", "add login", "set up sign-in", "I need users to log in", or asks how to enable any of magic-link / Google / GitHub auth on their AILK site. The skill writes env vars for whichever subset of providers the consumer activates and prints (plus saves) an OAuth-app-setup runbook. It does NOT modify `auth.config.ts` and does NOT emit any pages.
 ---
 
-# scaffold-auth
+# add-auth
 
 Activate one or more auth providers on an AILK site by writing the env
 vars NextAuth reads to detect them, plus a `RUNBOOK.md` that documents
@@ -24,14 +24,14 @@ Google / GitHub OAuth. Phrases that should trigger this skill:
 Skip this skill when:
 
 - The user wants a `/login` or `/account` _page_ — those are pages, not
-  auth wiring. Use `scaffold-page` (#362) for that.
+  auth wiring. Use `add-page` for that.
 - The user is asking about a third-party provider that isn't in the
   AILK locked set (Apple, Microsoft, Twitter, etc.). The locked set is
   magic-link + Google + GitHub at v1; broader provider support is a
   future PR. Acknowledge the request and stop.
 - The user is in production and needs production callback URLs. v1
   ships dev-mode callbacks (`http://localhost:3000`) only —
-  production callback setup is deferred to `provision-config` (#367)
+  production callback setup is deferred to `setup-deploy`
   or a future deploy skill. Note this and stop.
 
 ## What this skill does (and does not do)
@@ -207,7 +207,7 @@ Print:
 - A reminder to set `AILK_AUTH_REQUIRED=1` in `.env.local` if they
   want protected routes (default is auth-disabled / public).
 - A pointer to `RUNBOOK.md` for future reference.
-- A pointer to `provision-config` (#367) for production callback URL
+- A pointer to `setup-deploy` for production callback URL
   setup when the consumer is ready to deploy.
 
 ## Re-invocation
@@ -252,9 +252,9 @@ This means the skill's job is purely env-var wiring + documentation.
 
 ## Coordination
 
-- **`scaffold-page` (#362)** — `/login` or `/account` pages. This skill
+- **`add-page`** — `/login` or `/account` pages. This skill
   emits no pages.
-- **`provision-config` (#367)** — production callback URL setup. v1
+- **`setup-deploy`** — production callback URL setup. v1
   is dev-only.
 - **`@working-theory/database`** — Prisma adapter detection. Install
   `@working-theory/database` separately to upgrade from JWT-only to persistent

package/templates/.claude/skills/{scaffold-auth → add-auth}/references/env-vars.md

@@ -1,7 +1,7 @@
 # Auth Env-Var Contract
 
 Source of truth for which env vars activate which auth provider on
-an AILK consumer site. Read by the `scaffold-auth` skill before
+an AILK consumer site. Read by the `add-auth` skill before
 asking the consumer to paste secrets.
 
 The activation logic lives in `apps/web/lib/auth-env.ts` →
@@ -32,7 +32,7 @@ them in the closing summary so the consumer is aware:
 - `AILK_AUTH_REQUIRED` is the consumer's call (skill always defaults
   to leaving it unset).
 - `NEXTAUTH_URL` and `NEXTAUTH_SECRET` are deferred to production-time
-  setup (`provision-config` (#367) or future deploy skill).
+  setup (`setup-deploy` or future deploy skill).
 
 ## Env-var formats — what valid values look like
 

package/templates/.claude/skills/{scaffold-auth → add-auth}/references/oauth-app-setup.md

@@ -1,6 +1,6 @@
 # OAuth + Magic-Link Setup — RUNBOOK Template
 
-The `scaffold-auth` skill writes (or merges into) `RUNBOOK.md` at the
+The `add-auth` skill writes (or merges into) `RUNBOOK.md` at the
 consumer's repo root using the per-provider sections below. Only the
 sections for providers actually activated this session are emitted.
 
@@ -85,7 +85,7 @@ The `localhost` callback above is dev-only. For production, you'll
 need to add a second redirect URI to the same OAuth client (or
 create a separate prod client) of the form
 `https://<your-prod-domain>/api/auth/callback/google`. The
-`provision-config` skill or your future deploy skill will help you
+`setup-deploy` skill or your future deploy skill will help you
 wire this when you're ready to ship.
 
 ### Rotating the client secret
@@ -133,7 +133,7 @@ GITHUB_CLIENT_SECRET=...
 The `localhost` callback above is dev-only. For production, either
 register a separate OAuth App with a `https://<your-prod-domain>/...`
 callback, or update this app's callback (GitHub allows multiple).
-The `provision-config` skill or your future deploy skill will help
+The `setup-deploy` skill or your future deploy skill will help
 you wire this when you're ready to ship.
 
 ### Rotating the client secret