create-ailk 0.6.1 → 0.7.0

package/site-templates/simple-service/content/en/BookCall/book-call.mdx

@@ -0,0 +1,53 @@
+---
+type: "BookCall"
+slug: "book-call"
+title: "{Book a call: what a visitor gets from it}"
+description: "{One sentence on who the call is for and what they leave with}"
+placeholder: true
+schema:
+  mainEntity:
+    "@type": "Offer"
+    name: "{Your call name}"
+    price: 0
+    priceCurrency: "USD"
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "eyebrow": "Book a call",
+          "headline": "{Book a call: what a visitor gets from it}",
+          "subheadline": "{One sentence on who the call is for and what they leave with}",
+          "primaryCta": { "label": "Book a time", "href": "/meet" },
+        },
+    },
+    {
+      "id": "what-happens-on-the-call",
+      "type": "items",
+      "data":
+        {
+          "headline": "What happens on the call?",
+          "columns": 3,
+          "items":
+            [
+              {
+                "title": "{The first thing you cover}",
+                "description": "{One or two sentences on what the visitor learns or decides here}",
+              },
+              {
+                "title": "{The second thing you cover}",
+                "description": "{One or two sentences on what the visitor learns or decides here}",
+              },
+              {
+                "title": "{The next step you agree}",
+                "description": "{One or two sentences on what happens after the call}",
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]` by the /book-a-call route. This template carries the scheduling module, so the call to action opens the /meet booker. It overrides the base layer's copy, which points at /contact. The `schema:` Offer is the page's JSON-LD main entity — a free call. Placeholder copy — replace every {brace} with your own words before you launch. */}

package/site-templates/simple-service/content/en/ContactPage/contact.mdx

@@ -16,41 +16,6 @@ sections:
           "subheadline": "{One line on what happens after you send this, and how long it takes. If a call is faster, say so.}",
         },
     },
-    {
-      "id": "contact-form",
-      "type": "contact-form",
-      "data":
-        {
-          "variant": "card",
-          "source": "contact",
-          "fields":
-            [
-              {
-                "name": "name",
-                "label": "Name",
-                "type": "text",
-                "required": true,
-              },
-              {
-                "name": "email",
-                "label": "Email",
-                "type": "email",
-                "required": true,
-              },
-              {
-                "name": "message",
-                "label": "What needs doing?",
-                "type": "textarea",
-                "required": true,
-              },
-            ],
-          "submitLabel": "Send →",
-          "consentText": "I accept the Terms",
-          "consentLink": { "label": "Terms", "href": "/terms" },
-          "successMessage": "Thank you — your message is in. You will hear back within {time amount}.",
-          "action": "/v1/leads/submit",
-        },
-    },
     {
       "id": "closing",
       "type": "cta",
@@ -64,4 +29,4 @@ sections:
   ]
 ---
 
-The form posts to the site's own API (`/v1/leads/submit`) and confirms inline — no redirect, no thank-you page. Placeholder copy.
+The /contact route mounts the page's one contact surface — the guided intake, with its fallback form — which posts to the site's own API (`/v1/leads/submit`) and confirms inline. Placeholder copy.

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

@@ -0,0 +1,124 @@
+---
+type: "PurchasePolicyPage"
+slug: "purchase-policy"
+title: "Purchase Policy"
+description: "How cancellations, reschedules and refunds work for bookings made on this site. Placeholder policy — replace every section before you launch."
+placeholder: true
+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 Company, 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 bookings made on this site. The headings are the ones a customer 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 appointment, and say how it is measured. A customer 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 booking, and when each is charged. If you hold a deposit, say what happens to it in each case.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "our-cancellations",
+                      "heading": "If we cancel",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Set out what a customer gets if you cancel or move an appointment — 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 customer 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 customer gets back after a cancellation — the booking price, the deposit, or both, and how long the refund takes to reach the payment method it came from. If you offer store credit or a rebooking instead, describe when each applies.",
+                    },
+                  ],
+                "subsections":
+                  [
+                    {
+                      "id": "questions",
+                      "heading": "Questions about a refund",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Point to the one place a customer 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/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

@@ -9,14 +9,14 @@ 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.            |
+| `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

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

@@ -1,9 +1,9 @@
 ---
-name: scaffold-page
-description: Generate a new page on an AILK consumer site — App Router route + MDX content stub + typed JSON-LD attachment — in a single confirm-before-write pass. Use when the user says "scaffold me a /pricing page", "add an about page", "create a /contact route", or chains a row from `suggest-site-pages` output (e.g., "scaffold home — Organization — anchor with hero, value prop, CTA"). Both invocation shapes flow through the same pipeline. MDX-only at v1; refuses on existing routes and points at `add-schema` (#366).
+name: add-page
+description: Generate a new page on an AILK consumer site — App Router route + MDX content stub + typed JSON-LD attachment — in a single confirm-before-write pass. Use when the user says "scaffold me a /pricing page", "add an about page", "create a /contact route", or hands over a structured triple (e.g., "add home — Organization — anchor with hero, value prop, CTA"). Both invocation shapes flow through the same pipeline. MDX-only at v1; refuses on existing routes and points at the `schema:` frontmatter override for adding structured data to a page that already exists.
 ---
 
-# scaffold-page
+# add-page
 
 Generate a new page in one pass. Three artifacts emit together:
 
@@ -20,31 +20,29 @@ The consumer wants a new page on their AILK site. Triggers:
 
 - "scaffold me a /pricing page" / "create a /contact route"
 - "add an about page" / "I need a /privacy page"
-- A row chained from `suggest-site-pages` output:
-  `home — Organization — anchor with hero, value prop, CTA`
-- "scaffold that one" referring to a specific row from prior chat output
+- A structured triple: `home — Organization — anchor with hero, value prop, CTA`
+- "add that one" referring to a specific row from prior chat output
 
 Skip this skill when:
 
-- The consumer wants to **add schema to an existing page** — that's
-  `add-schema` (#366). This skill refuses on existing routes and
-  points at #366 explicitly.
-- The consumer wants to **plan their pages** — that's
-  `suggest-site-pages` (#361). Output of #361 is this skill's chained
-  input contract.
+- The consumer wants to **add supplementary schema to an existing
+  page** — that's the `schema:` frontmatter override (see
+  [Adding schema to an existing page](#adding-schema-to-an-existing-page)
+  below), not a separate skill. This skill refuses on existing routes
+  and points there.
 - The consumer's content backend is **not MDX**. v1 is MDX-only —
   other adapters (Sanity, Payload, additional adapters) are additive
   future PRs. Refuse with a clear message.
 
 ## What this skill does
 
-1. Parses the consumer's input — chained format
+1. Parses the consumer's input — structured triple
    (`<slug> — <Schema.orgType> — <purpose>`) OR free-text.
 2. Resolves the **primary schema.org type** for the page using
-   `references/page-types.md` (about → AboutPage, pricing → Service,
+   `references/page-types.md` (about → AboutPage, pricing → Pricing,
    etc.). Confirms the choice before writing.
 3. Detects existing routes and refuses if `app/<slug>/page.tsx`
-   already exists, pointing at `add-schema` (#366).
+   already exists, pointing at the `schema:` frontmatter override.
 4. Detects content adapter — only MDX is supported at v1; refuses
    on any other adapter with a clear message.
 5. Emits three files via `templates/route.tsx.tmpl` and
@@ -52,12 +50,13 @@ Skip this skill when:
    typed builder import from `@working-theory/schema`.
 6. Shows the consumer a **single diff** of all three files and waits
    for one confirmation. After approval, writes all files.
-7. Closing summary: pointer at `add-schema` (#366) for additional
-   schema, pointer at `audit-site` (#365) for citation-readiness check.
+7. Closing summary: pointer at the `schema:` frontmatter override for
+   additional schema, pointer at `check-site` for citation-readiness check.
 
 ## What this skill does NOT do
 
-- Modify an existing route. Refuses + points at `add-schema` (#366).
+- Modify an existing route. Refuses + points at the `schema:`
+  frontmatter override.
 - Run `pnpm dev` or rebuild content. The consumer does that.
 - Detect content-adapter type beyond "is it MDX?". v1 ships MDX
   only; other adapters are out of scope.
@@ -74,12 +73,12 @@ Skip this skill when:
 
 The consumer's request can arrive in either shape:
 
-**Chained shape** (from `suggest-site-pages` output):
+**Structured triple:**
 
 ```
 home — Organization — anchor with hero, value prop, CTA
 about — AboutPage — company story and team
-pricing — Service — public price tiers and feature comparison
+pricing — Pricing — public price tiers and feature comparison
 ```
 
 Three em-dash-separated fields: `<slug>` `<Schema.orgType>` `<purpose>`.
@@ -113,7 +112,7 @@ backend?
 
 If neither exists, refuse:
 
-> "scaffold-page only supports the MDX content backend at v1. Your
+> "add-page only supports the MDX content backend at v1. Your
 > project doesn't appear to have one — file an issue at the upstream
 > repo if you'd like Sanity / Payload / additional adapter support."
 
@@ -126,10 +125,11 @@ depending on the consumer's structure).
 
 If it exists, refuse:
 
-> "A route at `/<slug>` already exists. To **add schema** to an
-> existing page, run `add-schema` (#366) instead. To **replace** the
-> page entirely, delete the existing files first and re-run this
-> skill."
+> "A route at `/<slug>` already exists. To **add structured data** to
+> an existing page, use the `schema:` frontmatter override (see this
+> skill's [Adding schema to an existing page](#adding-schema-to-an-existing-page)
+> section) instead. To **replace** the page entirely, delete the
+> existing files first and re-run this skill."
 
 Stop. No writes.
 
@@ -187,57 +187,71 @@ Print:
 - The two paths written.
 - Reminder: `pnpm dev` to see the page, `pnpm build` to confirm it
   compiles.
-- Pointer at `add-schema` (#366) for adding supplementary schema
-  (FAQPage, HowTo, Product, etc.) to this page later.
-- Pointer at `audit-site` (#365) for citation-readiness check after
+- Pointer at the `schema:` frontmatter override for adding
+  supplementary schema (FAQPage-shaped Q&A, a `Review`, a richer
+  `mainEntity`, etc.) to this page later.
+- Pointer at `check-site` for citation-readiness check after
   adding pages.
 
-## Cross-skill chaining
+## Adding schema to an existing page
 
-Output of `suggest-site-pages` (#361) is this skill's input contract.
-The consumer can paste any row of #361's output verbatim and this
-skill scaffolds it. Example end-to-end:
+There is no separate skill for this — a page's MDX frontmatter
+already carries an escape hatch. `page.schema` is a
+`Record<string, unknown>`, opaque to the typed builder, that the
+builder merges on top of its derived fields after deriving them
+(frontmatter wins on conflict). Use it to add structured sub-entities,
+enrich a page with additional fields, or override any derived field
+— without re-scaffolding the route.
 
-1. Consumer asks `suggest-site-pages` for a SaaS page list.
-2. Output includes: `pricing — Service — public price tiers and feature comparison`
-3. Consumer says: "scaffold that pricing one"
-4. This skill resolves the row, emits route + MDX + JSON-LD, all in
-   one confirm-before-write pass.
-5. Consumer continues with the next row, or moves on.
+```yaml
+# in an existing page's MDX frontmatter
+---
+type: BlogPosting
+slug: hello-world
+title: Hello, World
+description: First post.
+schema:
+  author:
+    "@type": Person
+    name: Jane Doe
+---
+```
 
-## What lives in `references/page-types.md`
+Where an override key lands depends on the builder's shape — a
+two-layer builder (a `WebPage`-family envelope wrapping a described
+`mainEntity`, e.g. `BlogPosting`, `Service`, `Product`, `JobPosting`)
+routes most keys to the entity and a known few to the envelope; every
+other builder shallow-merges `page.schema` onto the top level. The
+full routing table is `packages/schema/README.md` § `schema` field
+override — read it before guiding a consumer through a non-obvious
+placement (e.g. `mainEntity` object merges, `@type` retyping).
 
-The type-to-schema mapping is data, not logic. Read the references
-file at runtime — don't try to remember the table.
+This is also how a page picks up a **supplementary** schema type that
+has no builder of its own — an `Offer`, a `Review`, an `AggregateRating`
+— since those are expressed as plain objects inside `schema:`, not as
+a distinct AILK page type.
 
-The mapping covers the canonical AILK page types:
+## What lives in `references/page-types.md`
 
-- Identity — `home → HomePage`, `about → AboutPage`
-- Conversion — `pricing → Service`, `contact → ContactPage`
-- Trust — `privacy → PrivacyPage`, `terms → TermsPage`
-- Editorial — `blog → Blog`, `blog/<slug> → BlogPosting`
-- Catalog — `products → ItemList`, `products/<slug> → Product`
-- Q&A — `faq → FAQPage`, `how-to/<slug> → HowTo`
+The type-to-schema mapping is data, not logic. Read the references
+file at runtime — don't try to remember the table. It is generated
+from `packages/schema/src/registry/entries.ts` by
+`packages/create-ailk/scripts/generate-page-types-reference.ts` —
+never hand-edit it; regenerate it instead (`pnpm page-types:build` from
+`packages/create-ailk`) whenever a registry key changes.
 
-The full list is in `references/page-types.md`. New types added to
-`@working-theory/schema` should be added to that file in a follow-up PR; the
-skill renders unrecognized types as a "missing from page-types.md"
-prompt to ask the consumer rather than guessing.
+The mapping covers every registered AILK page type — family, chassis,
+schema.org `@type`, and the route convention — with list/detail pairs
+(e.g. `ServicesList` / `Service`) shown together.
 
 ## Coordination
 
-- **`suggest-site-pages` (#361)** — output is this skill's chained
-  input. The two skills' references corpora (`categories.md` and
-  `page-types.md`) must agree on schema-type names.
-- **`add-schema` (#366)** — modifies existing pages. The
-  `<JsonLd schema={build<Type>(...)} />` attachment pattern is
-  shared with this skill (canonical pattern landed in #389 /
-  `@working-theory/jsonld`).
-- **`audit-site` (#365)** — citation-readiness check. Runs after
+- **`check-site`** — citation-readiness check. Runs after
   pages exist; not invoked from inside this skill.
-- **`@working-theory/jsonld`** (#389) — the React component for JSON-LD
+- **`@working-theory/jsonld`** — the React component for JSON-LD
   rendering. Single source of truth for the attachment pattern.
 - **`@working-theory/schema`** — typed builders (`buildHomePage`,
-  `buildAboutPage`, etc.). The skill's emit imports from here.
+  `buildAboutPage`, etc.). The skill's emit imports from here, and its
+  README documents the `schema` frontmatter override in full.
 - **`@working-theory/content-adapters`** (MDX) — the content backend. v1 is
   MDX-only; other adapters are deferred.