create-ailk 0.6.1 → 0.7.0

package/templates/.claude/skills/add-page/references/page-types.md

@@ -0,0 +1,111 @@
+<!-- GENERATED — do not hand-edit. Regenerate with:
+       cd packages/create-ailk && pnpm page-types:build
+     Source: packages/schema/src/registry/entries.ts
+     Generator: packages/create-ailk/scripts/generate-page-types-reference.ts
+-->
+
+# Page-Type → schema.org Registry Reference
+
+The full page-type catalog the `add-page` skill reads at runtime to
+resolve a slug or page-purpose hint to a family, chassis, schema.org
+`@type`, and route convention. Generated from
+`packages/schema/src/registry/entries.ts` — every registered page type
+appears exactly once, list/detail pairs are shown together, and no row
+here can name a type the registry doesn't have.
+
+The skill resolves in this order:
+
+1. **Exact slug match** — `pricing` → `Pricing`.
+2. **Slug-prefix match** — `blog/<anything>` → `BlogPosting`.
+3. **Free-text hint match** — "company story" / "team" → `AboutPage`.
+4. **Ask** — if nothing matches, ask the consumer rather than guessing.
+
+`<slug>` in a route below is the page's own slug (e.g. `hello-world`);
+`<Type>` families using two-layer builders route supplementary schema
+through the `schema:` frontmatter override — see this skill's
+[Adding schema to an existing page](../SKILL.md#adding-schema-to-an-existing-page) section, or `packages/schema/README.md` for the full
+override contract.
+
+## Core
+
+| Key | `@type` | Family | Chassis | Route |
+| --- | --- | --- | --- | --- |
+| `HomePage` | `HomePage` | core | home | / |
+| `AboutPage` | `AboutPage` | core | detail | /about |
+| `ContactPage` | `ContactPage` | core | detail | /contact |
+| `PrivacyPage` | `WebPage` | core | detail | /privacy |
+| `TermsPage` | `WebPage` | core | detail | /terms |
+| `PurchasePolicyPage` | `WebPage` | core | detail | /purchase-policy |
+| `WorkingAgreementPage` | `WebPage` | core | detail | /working-agreement |
+| `LandingPage` | `WebPage` | core | home | /<slug> |
+| `ThankYouPage` | `WebPage` | core | detail | /thanks/<slug> |
+| `BookCall` | `WebPage` | core | home | /book-a-call |
+| `NewsletterSignup` | `WebPage` | core | home | /newsletter |
+| `DemoRequest` | `WebPage` | core | home | /demo-request |
+| `TrialSignup` | `WebPage` | core | home | /trial-signup |
+| `Waitlist` | `WebPage` | core | home | /waitlist |
+| `Assessment` | `WebApplication` | core | home | /assessment |
+| `Calculator` | `WebApplication` | core | home | /calculator |
+| `CampaignLP` | `WebPage` | core | home | /<slug> |
+
+## Identity
+
+| Key | `@type` | Family | Chassis | Route |
+| --- | --- | --- | --- | --- |
+| `Organization` | `Organization` | identity | detail | — site-wide identity — emitted on the home page or in a layout |
+| `Person` | `Person` | identity | detail | — site-wide identity — emitted on the home page or in a layout |
+| `BreadcrumbList` | `BreadcrumbList` | identity | detail | — site-wide — attached alongside another page's own schema |
+| `ContactPoint` | `ContactPoint` | identity | detail | — site-wide — embedded in `Organization` or `Person` |
+
+## Canonical
+
+| Key | `@type` | Family | Chassis | Route |
+| --- | --- | --- | --- | --- |
+| `ServicesList` | `CollectionPage` | canonical-list | list | /services |
+| `Service` | `Service` | canonical-detail | detail | /services/<slug> |
+| `ProductsList` | `CollectionPage` | canonical-list | list | /products |
+| `Product` | `Product` | canonical-detail | detail | /products/<slug> |
+| `ProjectsList` | `CollectionPage` | canonical-list | list | /projects |
+| `Project` | `CreativeWork` | canonical-detail | detail | /projects/<slug> |
+| `FAQPage` | `FAQPage` | canonical-list | list | /faq |
+| `CareersList` | `CollectionPage` | canonical-list | list | /careers |
+| `JobPosting` | `JobPosting` | canonical-detail | detail | /careers/<slug> |
+| `UseCasesList` | `CollectionPage` | canonical-list | list | /use-cases |
+| `UseCase` | `WebPage` | canonical-detail | detail | /use-cases/<slug> |
+| `TestimonialsList` | `CollectionPage` | canonical-list | list | /testimonials |
+| `ClientsList` | `CollectionPage` | canonical-list | list | /clients |
+| `DownloadsList` | `CollectionPage` | canonical-list | list | /downloads |
+| `EventsList` | `CollectionPage` | canonical-list | list | /events |
+| `Event` | `Event` | canonical-detail | detail | /events/<slug> |
+| `CoursesList` | `CollectionPage` | canonical-list | list | /courses |
+| `Course` | `Course` | canonical-detail | detail | /courses/<slug> |
+| `TeamList` | `CollectionPage` | canonical-list | list | /team |
+| `TeamMember` | `ProfilePage` | canonical-detail | detail | /team/<slug> |
+| `PartnersList` | `CollectionPage` | canonical-list | list | /partners |
+| `Partner` | `AboutPage` | canonical-detail | detail | /partners/<slug> |
+| `IntegrationsList` | `CollectionPage` | canonical-list | list | /integrations |
+| `Integration` | `WebPage` | canonical-detail | detail | /integrations/<slug> |
+| `GlossaryList` | `CollectionPage` | canonical-list | list | /glossary |
+| `LocationsList` | `CollectionPage` | canonical-list | list | /locations |
+| `Location` | `Place` | canonical-detail | detail | /locations/<slug> |
+| `DocsList` | `CollectionPage` | canonical-list | list | /docs |
+| `SoftwareProduct` | `WebPage` | canonical-detail | detail | /software/<slug> |
+| `ServiceAreaPage` | `WebPage` | canonical-detail | detail | /service-areas/<slug> |
+| `Pricing` | `WebPage` | canonical-detail | detail | /pricing |
+| `ComparisonPage` | `WebPage` | canonical-detail | detail | /comparisons/<slug> |
+| `ReportPage` | `Report` | canonical-detail | detail | /reports/<slug> |
+
+## Editorial
+
+| Key | `@type` | Family | Chassis | Route |
+| --- | --- | --- | --- | --- |
+| `BlogList` | `Blog` | editorial-list | list | /blog |
+| `BlogPosting` | `BlogPosting` | editorial-detail | detail | /blog/<slug> |
+| `ResourcesHub` | `CollectionPage` | editorial-list | list | /resources |
+| `ResourceDetail` | `Article` | editorial-detail | detail | /resources/<slug> |
+| `CaseStudiesList` | `CollectionPage` | editorial-list | list | /case-studies |
+| `CaseStudy` | `Article` | editorial-detail | detail | /case-studies/<slug> |
+| `HowTo` | `HowTo` | editorial-detail | detail | /how-to/<slug> |
+| `Whitepaper` | `Article` | editorial-detail | detail | /whitepapers/<slug> |
+| `TechArticle` | `TechArticle` | editorial-detail | detail | /tech-articles/<slug> |
+| `DocsDetail` | `TechArticle` | editorial-detail | detail | /docs/<slug> |

package/templates/.claude/skills/{scaffold-page → add-page}/templates/content.mdx.tmpl

@@ -10,7 +10,7 @@ description: {{DESCRIPTION}}
 {{DESCRIPTION}}
 
 <!--
-  This is the MDX content stub emitted by `scaffold-page`.
+  This is the MDX content stub emitted by `add-page`.
   The frontmatter is the source of truth for JSON-LD — the
   `{{BUILDER}}(page)` call in `app/{{SLUG}}/page.tsx` reads it.
 
@@ -21,8 +21,8 @@ description: {{DESCRIPTION}}
    - Don't change `type` unless you also update the route's import
      to match a different `@working-theory/schema` builder.
 
-  When you're happy with the page, run `audit-site` (#365) to see
-  how it scores on citation-readiness. Use `add-schema` (#366) to
-  add supplementary schema (FAQPage, HowTo, etc.) without
+  When you're happy with the page, run `check-site` to see
+  how it scores on citation-readiness. Use the `schema:` frontmatter
+  override to add supplementary schema (FAQPage, HowTo, etc.) without
   re-scaffolding.
 -->

package/templates/.claude/skills/{scaffold-page → add-page}/templates/route.tsx.tmpl

@@ -1,4 +1,4 @@
-// Emitted by `scaffold-page` at `app/{{SLUG}}/page.tsx`. Substitutions:
+// Emitted by `add-page` at `app/{{SLUG}}/page.tsx`. Substitutions:
 //   {{SLUG}}     — page slug (e.g., "pricing")
 //   {{TYPE}}     — schema.org @type (e.g., "Service")
 //   {{BUILDER}}  — typed builder name (e.g., "buildService")

package/templates/.claude/skills/{audit-site → check-site}/SKILL.md

@@ -1,14 +1,14 @@
 ---
-name: audit-site
+name: check-site
 description: Run `ailk-audit --json` on the consumer's AILK site, parse the JSON report, and explain the score and findings in plain language. Use when the user asks "how is my site doing?", "audit my site", "what's my score?", "is my JSON-LD valid?", "do I have all the schema I need?", or otherwise wants a citation-readiness check on their AILK content. The skill never edits files — it reports and points at fix tools.
 ---
 
-# audit-site
+# check-site
 
 Shell out to `ailk-audit --json`, parse the JSON, and turn it into a
 conversational summary the consumer can act on. Pure explain-only —
-the skill names fix tools (like `add-schema`) but does not invoke
-them.
+the skill names fix tools (like the `schema:` frontmatter override)
+but does not invoke them.
 
 ## When to use
 
@@ -24,7 +24,7 @@ citation-readiness audit (AEO Layer 1). Triggers:
 Skip this skill when:
 
 - The consumer wants to _fix_ a finding — point them at the fix
-  tool (usually `add-schema` (#366)) and stop. This skill reports;
+  tool (usually `add-page`'s `schema:` frontmatter override) and stop. This skill reports;
   fix tools fix.
 - The consumer is asking about deploy-time monitoring or continuous
   audits — those are Pro features (`ailk pro` for details). Mention
@@ -131,18 +131,17 @@ themselves on a subsequent turn.
 
 | Rule                  | Fix tool                                                                                 |
 | --------------------- | ---------------------------------------------------------------------------------------- |
-| `schema-coverage`     | `add-schema` (#366) — add the missing schema type to the named page                      |
-| `jsonld-validity`     | `add-schema` (#366) — replace the invalid block; or hand-fix the MDX                     |
+| `schema-coverage`     | `add-page`'s `schema:` frontmatter override — add the missing schema type to the named page |
+| `jsonld-validity`     | `add-page`'s `schema:` frontmatter override — replace the invalid block; or hand-fix the MDX |
 | `entity-markup`       | Manual edit — ensure `Organization` (or `Person`) JSON-LD is emitted somewhere site-wide |
-| `faq-howto-incentive` | `add-schema` (#366) — add an `FAQPage` or `HowTo` block to a relevant page               |
+| `faq-howto-incentive` | `add-page`'s `schema:` frontmatter override — add an `FAQPage` or `HowTo` block to a relevant page |
 
 Phrase the pointer as a single sentence:
 
-> "Missing `Product` schema on `/pricing` — run `add-schema` (#366)
-> to add it."
+> "Missing `Product` schema on `/pricing` — add it via `add-page`'s
+> `schema:` frontmatter override."
 
-Never invoke `add-schema` automatically. Never write to the
-consumer's repo from inside this skill.
+Never write to the consumer's repo from inside this skill.
 
 ### Step 8 — Soft Pro mention
 
@@ -187,8 +186,8 @@ Never recommend "weekly" / "monthly" / a date.
 ## What this skill does NOT do
 
 - Edit any file in the consumer's repo.
-- Add JSON-LD to pages (that's `add-schema` #366).
-- Create new pages (that's `scaffold-page` #362).
+- Add JSON-LD to pages (that's the `schema:` frontmatter override, documented in `add-page`).
+- Create new pages (that's `add-page`).
 - Cache results between runs.
 - Track score history or trends.
 - Auto-invoke fix tools.
@@ -202,9 +201,9 @@ Never recommend "weekly" / "monthly" / a date.
 
 ## Coordination
 
-- **`add-schema` (#366)** — primary fix tool the skill points at.
-  Never auto-invoked.
-- **`scaffold-page` (#362)** — new-page creation; not a fix-tool
+- **`add-page`'s `schema:` frontmatter override** — primary fix
+  mechanism the skill points at. Never auto-invoked.
+- **`add-page`** — new-page creation; not a fix-tool
   for audit findings (audit reports on existing pages).
 - **`packages/aeo`** — owner of the `ailk-audit` CLI and rule set.
   This skill depends only on the CLI's `--json` output schema, not

package/templates/.claude/skills/{audit-site → check-site}/references/common-errors.md

@@ -1,7 +1,7 @@
 # Common Errors — Plain-Language Translations
 
 The three most common ways `ailk-audit` fails on a real consumer
-setup, with translations the `audit-site` skill emits instead of
+setup, with translations the `check-site` skill emits instead of
 the raw stderr. Errors not matching any of these signatures pass
 through verbatim with a one-line `` `ailk-audit` failed — `` prefix
 (see SKILL.md Step 2).
@@ -56,8 +56,8 @@ mis-translate an unfamiliar error into a familiar fix path.
 >
 > - Your content lives elsewhere — pass `--content-root <path>`
 >   to point at the right directory.
-> - You haven't authored any pages yet — run `suggest-site-pages`
->   to plan your pages, then `scaffold-page` to generate them.
+> - You haven't authored any pages yet — run `add-page` to generate
+>   them.
 > - The MDX files exist but aren't in the format the AILK content
 >   adapter expects — make sure each page has frontmatter with at
 >   least `title` and `type`.

package/templates/.claude/skills/{audit-site → check-site}/references/findings-glossary.md

@@ -2,7 +2,7 @@
 
 What each AEO rule means in plain language, what its `pass: false`
 result indicates, and what the consumer can do about it. Used by the
-`audit-site` skill in Step 6 (drill-down) and Step 7 (fix-tool
+`check-site` skill in Step 6 (drill-down) and Step 7 (fix-tool
 pointer).
 
 The structure deliberately matches `perRule[].id` from the audit
@@ -30,9 +30,10 @@ SGE, Perplexity, ChatGPT search) read to understand your pages. A
 page with no schema is invisible to citation; a page with the
 wrong schema gets miscategorized.
 
-**Fix tool:** `add-schema` (#366) — invoke it with the page slug
-and the schema type the registry expects (the audit names both).
-The skill will emit a `<JsonLd>` block matching the page's content.
+**Fix tool:** `add-page`'s `schema:` frontmatter override — set the
+schema type the registry expects (the audit names it) on the page's
+frontmatter. The typed builder emits a `<JsonLd>` block matching the
+page's content.
 
 ---
 
@@ -52,10 +53,10 @@ invalid blocks. The page exists, the JSON-LD exists, but the
 citation surface is broken because the block doesn't parse as
 valid schema.org.
 
-**Fix tool:** `add-schema` (#366) — replace the malformed block.
-For one-off edits to MDX, the consumer can also hand-edit the
-JSON-LD inline; `add-schema` is the safer path because it uses
-typed builders.
+**Fix tool:** `add-page`'s `schema:` frontmatter override — replace
+the malformed block. For one-off edits to MDX, the consumer can also
+hand-edit the JSON-LD inline; the frontmatter override is the safer
+path because it uses typed builders.
 
 ---
 
@@ -81,8 +82,9 @@ have nothing to anchor to.
 layout component rendered on every page) emits an
 `Organization` (or `Person`) JSON-LD block. The `<JsonLd
 schema={OrganizationSchema(...)} />` pattern from `@working-theory/schema`
-is the one this is going to ship as. `add-schema` (#366) can land
-the block on a specific page if you'd rather; but typically
+is the one this is going to ship as. `add-page`'s `schema:`
+frontmatter override can land the block on a specific page if you'd
+rather; but typically
 identity goes in a layout, not a leaf page.
 
 ---
@@ -105,10 +107,10 @@ explicit Q&A or step-by-step content because those are easier to
 quote directly into a generated response. Adding an FAQ or HowTo
 block to relevant pages is a low-effort score boost.
 
-**Fix tool:** `add-schema` (#366) — add an `FAQPage` block to
-your `/pricing` or `/contact` page (anywhere your customers ask
-predictable questions), or a `HowTo` block to any
-process/instructions content. `audit-site` will surface this as
+**Fix tool:** `add-page`'s `schema:` frontmatter override — add an
+`FAQPage` block to your `/pricing` or `/contact` page (anywhere your
+customers ask predictable questions), or a `HowTo` block to any
+process/instructions content. `check-site` will surface this as
 an _incentive_ in drill-down, not a finding to "fix."
 
 ---

package/templates/.claude/skills/{audit-site → check-site}/references/severity-levels.md

@@ -1,7 +1,7 @@
 # Severity Levels — Score Banding + Severity Mapping
 
 The AEO audit JSON does **not** include explicit severity fields.
-Severity is **derived** by the `audit-site` skill from each rule's
+Severity is **derived** by the `check-site` skill from each rule's
 `weight` and `pass`. This file is the source of truth for that
 mapping.
 

package/templates/.claude/skills/fill-page/SKILL.md

@@ -0,0 +1,180 @@
+---
+name: fill-page
+description: Fill one existing page's section content from a category profile. Tier 1 writes realistic, labelled sample content for the category (a plumber's home page, say). Tier 2 asks the owner the profile's questions and writes the company's own first draft from their answers and `_site.mdx`. Use when the user says "fill this page", "fill the home page for a plumber", "write sample content for my services page", or "write my real copy from what I tell you". It never creates a page, never changes a page's section stack, and never edits `_site.mdx`.
+---
+
+# fill-page
+
+Replace one page's `{brace}` instructions with content, reading the
+content from a **category profile** (`profiles/<slug>.yaml` beside this
+file). A profile is the data for one business type: the schema.org
+subtype, the typical offerings, the proof buyers expect, the buyer's own
+words, and the questions to ask the owner.
+
+Two tiers:
+
+| Tier | Source                                                   | Result                                     | `placeholder` |
+| ---- | -------------------------------------------------------- | ------------------------------------------ | ------------- |
+| 1    | the profile                                              | realistic sample content for the category  | `true`        |
+| 2    | `_site.mdx` + the owner's answers (`content/_intake.yaml`) | the company's own first draft              | by the rule in Step 2.4 |
+
+`placeholder: true` in a page's frontmatter makes the site render a
+**PLACEHOLDER — REPLACE BEFORE LAUNCH** label at the top of the page.
+The label is for people. Structured data reaches agents without it, so
+tier-1 content must be safe to publish by itself (see the never-invent
+list).
+
+## Inputs
+
+- **The page file** — `content/<locale>/<Type>/<slug>.mdx`. It must
+  already exist; `add-page` creates pages.
+- **The page type** — the frontmatter `type`.
+- **The profile slug** — a file under `profiles/` (e.g. `plumbing`).
+  Ask if the user did not name one. If there is no profile for their
+  category, say so and stop.
+- **The tier** — 1 unless the user asks for their own copy.
+
+## What never changes
+
+- The page's **section stack**: every section's `id` and `type`, in
+  order. Never add, remove or reorder a section. The starter's manifest
+  records each page's sections, and a changed stack fails its check.
+- Each section's **layout options** that are already present:
+  `variant`, `columns`, `layout`, `initialOpen`, `size` and the like.
+  They are the site's locked look.
+- Link targets (`href`) that are already present, except a link to a
+  Service page, which follows that page's slug (Step 1.3).
+- `{/* … */}` comments in the MDX body.
+- `_site.mdx`. Identity strings (the company name) are read from it,
+  never written to it.
+
+## Never invent (tier 1)
+
+At tier 1, write none of these. Remove any you find in the page:
+
+- `price`, `priceCurrency`, `availability` or `stripe` — each feeds the
+  schema.org `Offer` an agent quotes as the company's price.
+- A person's name or another company's name.
+- A phone number, a street address, or a licence or registration number.
+- A town, a county, or a distance: the service area is a company fact.
+- Testimonials: `author` is the literal `Sample customer`; no `company`,
+  `rating` or `avatar`.
+- Statistics a reader would take as measured (a count of jobs, a years
+  figure). Use the profile's `proof[]` labels as words, not numbers.
+
+The company name is the one identity string tier 1 may write, and it
+comes from `_site.mdx` `siteIdentity.name`.
+
+## Step 0 — Read
+
+1. Read the profile: `profiles/<slug>.yaml`.
+2. Read `content/_site.mdx` for `siteIdentity.name`.
+3. Read the page file. Note its stack (`sections[].type` in order).
+4. For each section type in the stack, read its data schema: the
+   `<Type>SectionDataSchema` (or `<Type>DataSchema`) export in the
+   installed `@working-theory/validation`'s `schemas/page-sections`. Fill
+   only fields the schema declares. Every field a section renders from
+   copy gets content; a field the source page did not use stays unused.
+5. Find the route that renders this page type under `apps/web/app/[locale]/`
+   and read its `bodyMode`. When it is `"mdx-body"`, the MDX body is
+   rendered and must be filled too. Otherwise the body is a short note,
+   and you rewrite it as one plain sentence that names no braces.
+
+`references/section-sources.md` maps each section type to the profile
+fields and intake answers that fill it.
+
+## Step 1 — Tier 1: sample content
+
+1. **Sections.** For each section, in place, write every copy field from
+   the profile using `references/section-sources.md`:
+   - offerings → `items` entries (`title` = the offering `name`,
+     `description` = its `job`, `link.href` = `/services/<kebab name>`);
+   - vocabulary → headlines, eyebrows and FAQ questions (the buyer's own
+     words: the `problem` list for what went wrong, `outcome` for what
+     they get);
+   - proof → `stats` labels and `testimonials` quotes, under the
+     never-invent list.
+   Keep `id`, `type` and every layout option.
+2. **Frontmatter.** Rewrite `title` and `description` without braces.
+   Use the company name from `_site.mdx` where the page names the
+   company. On a page that carries `provider.name`, set it to the company
+   name. Drop `schema.areaServed`; set `schema.serviceType` to the
+   offering name. Remove every key the never-invent list names.
+3. **Service pages.** A `Service` page is one offering. The user names
+   the offering, or you take the first profile offering that no other
+   Service page carries yet. Set `title` and `schema.serviceType` to the
+   offering `name`, and `slug` and the file name to its name in kebab
+   case (`Drain clearing` → `drain-clearing`): rename the file, never
+   copy it. To give every offering a page, the user first adds one
+   Service page per offering (`add-page`, or a copy of an existing one),
+   then runs this skill on each.
+4. **Body.** When the route renders `mdx-body`, rewrite each paragraph
+   and list item under the page's existing headings in the category's
+   words. Keep the headings, keep the order, keep the comments. Drop
+   every `\{…\}` instruction. Under a price heading, say how the job is
+   priced (the offering's `pricing`: `quote`, `fixed`, `hourly`,
+   `subscription`) in words, with no figure.
+5. **Label.** Set `placeholder: true` in the frontmatter.
+6. **Check** (below).
+
+## Step 2 — Tier 2: the company's own draft
+
+1. **Ask.** Ask each `intake[]` question from the profile, in order, one
+   at a time. Record the answers in `content/_intake.yaml`:
+
+   ```yaml
+   answers:
+     offerings: [Drain clearing, Emergency call-out]
+     service_area: "…"
+     faq: null # unanswered
+   ```
+
+   A list answer stays a list. An unanswered or skipped question is
+   `null`. Offerings are named exactly as the profile names them.
+2. **Fill.** Fill the page as in Step 1, but from `_site.mdx` and the
+   answers first; the profile fills only what the answers leave open.
+   - A profile offering the owner does not offer appears on no page:
+     remove its `items` entries, and ask before deleting its Service
+     page (the one file this skill may delete).
+   - A price appears only when the owner gave one, with `priceCurrency`.
+   - The company name appears in each page's frontmatter (`title` or
+     `description`), and the service area in the home hero when given.
+   - A section whose sources have no answer keeps its tier-1 sample
+     content.
+3. **Never invent** still holds for everything the owner did not give.
+   Testimonials stay `Sample customer` unless the owner supplies a
+   customer's name with permission to publish it.
+4. **Label.** Set `placeholder: false` only when every section is filled
+   from company facts:
+   - every section type in the stack appears in the `fills` of at least
+     one intake item whose answer is not empty, and
+   - when the stack has a `hero` or `cta`, `_site.mdx` has
+     `siteIdentity.name`.
+
+   A page with no sections is judged on its body: a `Service` page is
+   cleared only when the `offerings` answer names its offering; any
+   other page with no sections keeps `placeholder: true`. In every other
+   case, keep `placeholder: true`.
+5. **Check** (below).
+
+## The check
+
+Run the site's own structured-data check. It reads every content page
+through the same frontmatter and section schemas the site renders with,
+and validates each page's JSON-LD:
+
+```bash
+pnpm --filter web test -- lib/__tests__/structured-data.test.tsx
+```
+
+Then search the filled file for a `{` or `}` in any frontmatter string or
+in the body outside `{/* … */}` comments. Fix everything either reports
+and run both again. Stop only when both are clean.
+
+## What this skill does not do
+
+- Tier 3 (the Messaging Canvas through the content pipeline).
+- Create a page — use `add-page`.
+- Edit `_site.mdx`, the nav or the page roster. A profile's `roster` and
+  `nav` entries are declared for a later step and are not applied here.
+- Write a price, a name or an address the owner did not give.

package/templates/.claude/skills/fill-page/profiles/plumbing.yaml

@@ -0,0 +1,80 @@
+# Category profile — Local Plumbing (#6640; starter-template contract § D).
+# Read by the `fill-page` skill: tier 1 fills a page with labelled sample
+# content from this file; tier 2 asks `intake[]` and fills from the answers.
+# Twin: templates/.claude/skills/fill-page/profiles/plumbing.yaml (byte-identical).
+slug: plumbing
+shape: local-business-service
+subtype: Plumber
+secondary: Person
+offerings:
+  - name: Drain clearing
+    job: Clears blocked sinks, showers, toilets and main drains, and says what caused the blockage.
+    pricing: quote
+  - name: Water heater installation
+    job: Removes the old tank or boiler and fits, tests and registers a new water heater.
+    pricing: fixed
+  - name: Emergency call-out
+    job: A plumber at the door the same day for a burst pipe, a flood or no water at all.
+    pricing: hourly
+  - name: Leak detection and repair
+    job: Finds the hidden leak behind a wall or under a floor and fixes it with the least damage.
+    pricing: quote
+proof:
+  - kind: credential
+    label: Licensed and insured
+  - kind: reviews
+    label: Reviews from local customers
+  - kind: response-time
+    label: Same-day response on emergency calls
+  - kind: guarantee
+    label: Workmanship guaranteed
+vocabulary:
+  problem:
+    - burst pipe
+    - blocked drain
+    - no hot water
+    - leaking tap
+    - low water pressure
+    - water stain on the ceiling
+  service:
+    - drain clearing
+    - water heater install
+    - emergency call-out
+    - leak repair
+    - pipe replacement
+  outcome:
+    - same-day fix
+    - hot water back on
+    - no water damage
+    - upfront quote
+    - tidy job, nothing left behind
+roster:
+  - op: add
+    route: /emergency
+    pageType: BookCall
+    reason: Emergency jobs book a call, not a form.
+  - op: drop
+    route: /pricing
+    reason: Most plumbing work is quote-priced, so a price table misleads.
+nav:
+  Services: Plumbing services
+content_posture: sample
+intake:
+  - id: offerings
+    ask: Which of these jobs do you take on, and is there one you do not list? (Drain clearing, water heater installation, emergency call-out, leak detection and repair.)
+    fills: [hero, items]
+  - id: service_area
+    ask: Which towns, postcodes or radius do you cover?
+    fills: [hero, cta]
+  - id: about
+    ask: How did the business start, who does the work, and what will you not take on?
+    fills: [content-block]
+  - id: proof
+    ask: What can a customer check — your licence, your insurance, your reviews, your response time, your guarantee?
+    fills: [stats, testimonials, social-proof]
+  - id: faq
+    ask: What do customers ask before they book, and what do you tell them?
+    fills: [faq]
+  - id: contact
+    ask: How should a customer reach you — phone, form or booking — and how fast do you reply?
+    fills: [cta]

package/templates/.claude/skills/fill-page/references/section-sources.md

@@ -0,0 +1,41 @@
+# Section sources
+
+Where each section's copy comes from. **Profile** is tier 1's source;
+**Intake** lists the `intake[]` answers that fill the section at tier 2
+(the same ids appear in each question's `fills`). Fields not named here
+are layout options: keep them as they are.
+
+| Section type    | Copy fields                                                                 | Profile (tier 1)                                                                                                 | Intake (tier 2)                          |
+| --------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
+| `hero`          | `eyebrow`, `headline`, `subheadline`, `primaryCta.label`, `secondaryCta.label` | `vocabulary.problem` + `vocabulary.outcome` for the headline; the category name for the eyebrow                 | `offerings`, `service_area`              |
+| `items`         | `headline`, `description`, `items[].title`, `items[].description`, `items[].link` | one item per `offerings[]` entry: `title` = `name`, `description` = `job`, `link.href` = `/services/<kebab name>` | `offerings`                              |
+| `cta`           | `headline`, `description`, `primaryCta.label`, `secondaryCta.label`         | `vocabulary.outcome`                                                                                             | `service_area`, `contact`                |
+| `content-block` | `eyebrow`, `headline`, `body`                                               | `proof[].label` and `vocabulary.service`, with no names, places or numbers                                        | `about`                                  |
+| `faq`           | `headline`, `items[].question`, `items[].answer`                            | questions in `vocabulary.problem` words; answers from `offerings[].pricing` and `proof[]`                        | `faq`                                    |
+| `stats`         | `headline`, `items[].label`, `items[].value`                                | `proof[].label` as the label; a value only when it is not a measurement (e.g. `Same day`)                        | `proof`                                  |
+| `testimonials`  | `headline`, `items[].quote`, `items[].author`                               | quotes in `vocabulary.outcome` words; `author: Sample customer`; no `company`, `rating` or `avatar`              | `proof`                                  |
+| `social-proof`  | `headline`, labels                                                          | `proof[].label`                                                                                                  | `proof`                                  |
+
+A section type not in this table: fill its copy fields from the profile's
+`vocabulary` and leave its data otherwise as it was. At tier 2 no intake
+answer fills it, so a page carrying it keeps `placeholder: true`.
+
+## Frontmatter
+
+| Key                    | Tier 1                                             | Tier 2                                      |
+| ---------------------- | -------------------------------------------------- | ------------------------------------------- |
+| `title`, `description` | the category's words; the company name from `_site.mdx` where the page names the company | the company name and the owner's answers    |
+| `provider.name`        | `siteIdentity.name`                                | `siteIdentity.name`                         |
+| `schema.serviceType`   | the offering `name`                                | the offering `name`                         |
+| `schema.areaServed`    | removed                                            | the `service_area` answer                   |
+| `price`, `priceCurrency`, `availability`, `stripe` | removed                | only a price the owner gave, with its currency |
+| `placeholder`          | `true`                                             | by the rule in `SKILL.md` Step 2.4           |
+
+## Pricing words (Service bodies, FAQ answers)
+
+| `pricing`      | Say                                                                 |
+| -------------- | ------------------------------------------------------------------- |
+| `quote`        | priced after a look at the job; the quote is given before work starts |
+| `fixed`        | one fixed price for the job, agreed before work starts               |
+| `hourly`       | charged by the hour on site, with the call-out rate stated up front  |
+| `subscription` | a regular plan, billed on a schedule                                 |