create-ailk 0.9.0 → 0.11.0

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

@@ -1,260 +0,0 @@
----
-name: add-page
-description: Add a new page to this AI Launch Kit site — a new service, a new "who it's for" page, a new booking page, a comparison against a competitor, a stand-alone landing page, or a whole route the site doesn't carry yet like /pricing — with its content file, its structured data and its nav link, in one confirm-before-write pass. Use this whenever the user wants a page that doesn't exist yet, even if they don't say "page" — "add a service for kitchen remodels", "I need a /pricing page", "make a page for dentists", "add a comparison with Acme", "we need a booking page for on-site estimates", "add a landing page for the spring offer", or a structured triple like "pricing — Pricing — plans and FAQ". Not for changing a page that already exists (fill-page writes content; update-page renames).
----
-
-# add-page
-
-Add a page this site can actually serve, at the path its routes really use,
-with a nav link, and nothing else. One plan, one confirmation, then write.
-
-The single most important fact about this site: **almost every page type
-already has its route.** Routes live in `apps/web/app/[locale]/…` and render
-whatever content file sits in `content/en/<Type>/`. So adding a page is
-usually **adding one content file**, not writing route code. Route code is
-only ever added by the `create-ailk add-route` command, never by hand — a
-hand-written route drifts from the template the site is built from and
-breaks the next `create-ailk` upgrade.
-
-## Step 1 — Read what this site can serve
-
-Run, from the site's root:
-
-```bash
-node .claude/skills/add-page/scripts/site-pages.mjs
-```
-
-It prints the site's shape, design and level (from `.ailk-site-manifest.json`),
-then one row per page type this site renders: its route, whether it takes new
-pages (a route with a `[slug]` does; a fixed route like `/about` is one page),
-and the pages already written. Add `--json` if you want to parse it.
-
-Treat this output as the truth about the site. `references/page-types.md`
-lists every page type AI Launch Kit knows — the vocabulary — but many of them
-are not on this site. Never offer a page type the script doesn't list unless
-you are also going to add its route (Step 3, case D).
-
-Then read `.ailk-site-manifest.json` at the site root yourself, the site's
-roster of record:
-
-- `modules` — the modules this site has. Add any module the `# Modules:`
-  line of `architecture.yaml` names that `modules` does not: `create-ailk
-  add-module` records a module it adds there. With no manifest, or none
-  carrying `modules`, that line is the set.
-- `rows` — every route the site already has (`route`) and the page type
-  each renders (`pageType`).
-- `level` — present only when the scaffold derived it from the licence key.
-  It never decides what to offer; `modules` does.
-
-A page type renders on this site only when the **Module** column of
-`references/page-types.md` names a module in that set. Never offer,
-suggest or write any other page type: a type whose Module the site lacks is
-case E, never case D.
-
-## Step 2 — Work out which page type the user wants
-
-The user may give a structured triple (`<slug> — <Type> — <purpose>`) or plain
-words. Resolve plain words to a type with `references/page-types.md`: an exact
-slug match first (`pricing` → `Pricing`), then a prefix (`services/…` →
-`Service`), then the purpose ("company story" → `AboutPage`). If two types
-fit, or none does, ask — a wrong type gives the page the wrong structured
-data, which is what search and answer engines read.
-
-Also settle the slug: lowercase, hyphenated, from the user's words
-(`kitchen-remodels`, not `kitchen_remodels` or `KitchenRemodels`).
-
-## Step 3 — Decide which case this is
-
-Check case C first: if the page the user describes already exists (the type is on a fixed route and its one page is in the "existing" column, or the slug is taken), stop there — nothing else in this skill applies.
-
-| Case | When | What you'll write |
-|---|---|---|
-| **A. New page on an existing route** | The type is listed and takes new pages (`Service`, `UseCase`, `PortfolioItem`, `BookCall`, `ThankYouPage`, …) | One content file: `content/en/<Type>/<slug>.mdx`. Plus a nav link if the page belongs in the nav. |
-| **B. Stand-alone landing page** | A one-off page at `/<slug>` that isn't any specific type (an offer, a campaign) | One content file: `content/en/LandingPage/<slug>.mdx`. The site's catch-all route serves it. |
-| **C. The page already exists** | A fixed-route type already has its page (`/about`, `/contact`, `/faq`), or `<slug>` is taken | Nothing. Say so. To change its words, use `fill-page`; to rename it or move its URL, use `update-page`. |
-| **D. The route isn't on this site** | The type exists in `page-types.md` but not in the script's output (e.g. `/pricing` on a person-service site) | First the route: `pnpm create ailk@latest add-route <route-id>` (run in the site root). `<route-id>` is the route family's name as `pnpm create ailk@latest --help` lists it under `--surfaces` — usually the first path segment (`pricing`, `alternatives`, `careers`). Then continue as case A (or case C for a fixed route — `add-route` seeds its page). |
-| **E. Needs a module the site doesn't have** | The type's **Module** in `page-types.md` is not in the site's modules (Step 1), or `add-route` refuses, naming a module (e.g. docs, blog, scheduling-backed booking) | Nothing yet. Tell the user which module renders it and which level carries it (the **Level** column), and point at the `upgrade-plan` skill. Don't try to recreate the module's routes by hand. |
-
-Why case B uses `LandingPage` rather than a new route: a route directory is
-template code the site inherits and upgrades; a content file is the owner's.
-Keeping one-off pages as content keeps upgrades clean.
-
-Comparison pages (`/vs/<competitor>`, listed on `/alternatives`) are case A on
-the `alternatives` route family, or case D when the site doesn't carry it yet
-(`add-route alternatives`). The `/alternatives` hub lists every comparison
-automatically — never hand-list them on the hub's page.
-
-Reports and flow landing pages are content on routes the **signal-collectors
-module** owns — see "Reports" and "Flow landing pages" below.
-
-## Step 4 — Draft the content file
-
-Copy the shape of a page the site already has **of the same type** — pick one
-from the "existing" column (e.g. `content/en/Service/first-engagement.mdx`).
-Its frontmatter is exactly what that type's route and structured-data builder
-expect, so matching it is how the new page renders and emits valid JSON-LD.
-Keep the same keys and section structure; replace the words.
-
-- Pick the page to copy with care: if the only page of this type is an odd one
-  (a hub slug, a stub), start from `templates/content.mdx.tmpl` instead and
-  borrow the section shapes from `content/en/HomePage/home.mdx`.
-- Set `slug` to the new slug and write a real `title` and `description` from
-  what the user said. `description` becomes the meta description and feeds the
-  structured data, so make it a true one-sentence summary.
-- Use the site's own name from `content/_site.mdx` wherever the page names
-  the business (a comparison's "us" side, a CTA) — don't leave `{Your Name}`
-  when the answer is on disk.
-- A time-limited offer carries its end date in structured data
-  (`schema: { offers: { validThrough: "2027-05-31" } }`) and says it in the
-  copy, so the page doesn't keep advertising an expired deal.
-- Where you don't have the owner's facts (prices, names, results), write
-  clearly-marked placeholder copy — never invent facts about their business.
-  Offer `fill-page` afterwards to write it properly.
-- If no page of this type exists yet, start from `templates/content.mdx.tmpl`
-  (or `templates/comparison-page.mdx.tmpl` for a comparison) and fill in the
-  `type` from `page-types.md`. Reports and flow landing pages have their own
-  templates — see their sections below.
-- Extra structured data (an `Offer`, a `Review`, an `author`) goes in the
-  frontmatter `schema:` block — see "Adding schema to a page" below. Don't
-  hand-write JSON-LD anywhere.
-
-## Step 5 — Link the page from its hub and the nav
-
-**The hub page.** Detail types sit under a list page: `Service` under
-`ServicesList` (`/services`), `UseCase` under `UseCasesList` (`/for`),
-`PortfolioItem` under `PortfolioList` (`/portfolio`). Open the hub's content
-file. If it lists its entries by hand (an `items` section with one entry per
-page, each with an `href`), add an entry for the new page in the same shape —
-otherwise visitors can't find it. The comparisons hub (`/alternatives`) and the
-reports hub (`/reports`) are the exceptions: they list their pages automatically.
-
-**The nav.**
-
-The site nav is `apps/web/lib/nav-config.ts`; its labels are keys in the
-`nav` section of `apps/web/messages/<locale>.json` (one file per language
-under `apps/web/messages/`).
-
-- A detail page under a list (a new service, a new persona) usually belongs in
-  that list's flyout or group in `nav-config.ts`. A stand-alone landing page
-  usually doesn't belong in the nav at all — ask if unsure. If it isn't in the
-  nav or a hub, tell the user how visitors will reach it (a link from the home
-  page, an email, an ad), because nothing on the site points to it yet.
-- Name a new `labelKey` after the page in camelCase (`kitchenRemodels`), not
-  after its position (`service4`), so it still makes sense after reordering.
-- A flyout may list the same links twice — once in `features` (the compact
-  view) and once in `groups` (the grouped view). Add the link to both.
-- To add a link: add an entry with the new `labelKey` and the locale-free path
-  (`/services/kitchen-remodels`, not `/en/…`), and add that key with its label
-  to **every** messages file (a site with one language has one file). A key
-  missing from one language breaks that language's nav.
-- Know the trade-off and tell the user once: `create-ailk` regenerates the nav
-  when a route or module is added, but only while `nav-config.ts` is exactly as
-  generated. Once hand-edited, later `add-route`/`add-module` runs leave it
-  alone and print the change they wanted instead.
-
-## Step 6 — Show the plan, confirm once, write
-
-Show every file you will create or change — the content file in full, and the
-exact lines added to the hub page, `nav-config.ts` and each messages file — plus any
-`add-route` command you'll run first. Wait for one confirmation. Then run the
-command (if any) and write the files. Don't write anything before the user
-confirms, and don't touch any other file.
-
-## Step 7 — Check it
-
-Run `pnpm build` from the site root. Then tell the user:
-
-- the new page's URL (with the locale, e.g. `/en/services/kitchen-remodels`)
-- that `fill-page` can write its real copy, and `check-site` can score it
-  for search and answer-engine readiness.
-
-If the build fails, the usual cause is frontmatter that doesn't match the
-type — compare the new file with the page you copied in Step 4.
-
-## Reports
-
-`ReportPage` (the `/reports/<slug>` report reader) is a hub-and-spoke family
-listed on the `/reports` hub (`ReportsList`). Its routes are
-**module-owned code** (the signal-collectors module's own
-`app/[locale]/reports/[slug]/page.tsx` and `app/[locale]/reports/page.tsx`),
-so this skill writes report **content only**, never report route code
-(spec 6892 D5).
-
-When the resolved type is `ReportPage` — a structured triple naming it, or
-free text like "add a report on Q3 results" — do this instead of Steps 3–4:
-
-1. Refuse when `app/[locale]/reports/[slug]/page.tsx` is absent, naming the
-   `signal-collectors` module: "This site has no report reader yet — run
-   `create-ailk add-module signal-collectors` first."
-2. Write `content/en/ReportPage/<slug>.mdx` from
-   `templates/report-page.mdx.tmpl` (substituting `{{SLUG}}`, `{{TITLE}}`,
-   `{{DESCRIPTION}}`, `{{DATE_PUBLISHED}}` — an ISO date — and
-   `{{DATE_LABEL}}` — the display string, e.g. "March 2025"). Refuse only
-   when that file already exists.
-3. When `content/en/ReportsList/reports.mdx` is absent, write it from
-   `templates/reports-list.mdx.tmpl` (substituting `{{TITLE}}`/`{{DESCRIPTION}}`
-   for the hub's own copy).
-
-The hub's own card list is **generated at request time** from whichever
-`ReportPage` seeds exist (`app/[locale]/reports/page.tsx` injects them) —
-never hand-list reports on the hub's MDX. Steps 5–7 apply as usual.
-
-## Flow landing pages
-
-A flow landing page is a single, standalone `LandingPage` whose CTA opens a
-named flow at `/flows/<slug>/start` — the referral-request shape (spec 6892
-D3). It belongs to no hub, but like the report family its route is
-**module-owned code** (the signal-collectors module's own
-`app/[locale]/flows/[slug]/start/page.tsx`), so this skill writes content
-only.
-
-When the consumer asks for a flow landing page — "add a referral page",
-"add a landing page for the intake flow" — given a flow slug:
-
-1. Refuse when `app/[locale]/flows/[slug]/start/page.tsx` is absent, naming
-   the `signal-collectors` module: "This site has no flow engine yet — run
-   `create-ailk add-module signal-collectors` first."
-2. Refuse when `content/en/LandingPage/<slug>.mdx` already exists — this
-   is a single standalone page, not a family member with its own detail
-   route.
-3. Write `content/en/LandingPage/<slug>.mdx` from
-   `templates/flow-landing-page.mdx.tmpl`, substituting `{{SLUG}}`,
-   `{{TITLE}}`, `{{DESCRIPTION}}` as usual and `{{FLOW_SLUG}}` — the flow's
-   own slug, which may differ from the page's `{{SLUG}}`.
-
-This skill writes no flow definition (`database/flows/<slug>.flow.json`) —
-that is a separate artifact, seeded through the flow engine, not through a
-page.
-
-## Adding schema to a page
-
-Every page's frontmatter has an escape hatch, `schema:`, that the page's
-structured-data builder merges on top of what it derives (frontmatter wins).
-Use it to add sub-entities or enrich fields, on a new page or an existing one:
-
-```yaml
----
-type: Service
-slug: kitchen-remodels
-title: Kitchen remodels
-description: Full kitchen remodels, from design to final inspection.
-schema:
-  offers:
-    "@type": Offer
-    priceCurrency: USD
-    price: "15000"
----
-```
-
-On types that wrap a described entity in a page (`Service`, `Product`,
-`BlogPosting`, `JobPosting`), most keys land on the entity; on others they
-merge at the top level. This is also how a page gets a supplementary type
-with no page type of its own — `Offer`, `Review`, `AggregateRating`.
-
-## What this skill does not do
-
-- Write or copy route code by hand — `create-ailk add-route` does that.
-- Change an existing page's words (`fill-page`), name or URL (`update-page`).
-- Add a module or change the site's level (`upgrade-plan` explains; the
-  owner decides).
-- Edit `_site.mdx`, the design, or another page's content.

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

@@ -1,124 +0,0 @@
-<!-- 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.
-
-**Level** and **Module** name what a page type needs: the module whose
-code renders it, and the level that module comes with. Read the site's
-`.ailk-site-manifest.json` `modules` first — a page type whose Module is
-not in that list is one this site cannot render, so it is never offered;
-name its module and level instead (the `upgrade-plan` skill explains the
-levels). The level is the module's, never a claim about this site's key.
-
-`<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 | Level | Module |
-| --- | --- | --- | --- | --- | --- | --- |
-| `HomePage` | `HomePage` | core | home | / | Free | `marketing` |
-| `AboutPage` | `AboutPage` | core | detail | /about | Free | `marketing` |
-| `ContactPage` | `ContactPage` | core | detail | /contact | Free | `marketing` |
-| `PrivacyPage` | `WebPage` | core | detail | /privacy | Free | `marketing` |
-| `TermsPage` | `WebPage` | core | detail | /terms | Free | `marketing` |
-| `PurchasePolicyPage` | `WebPage` | core | detail | /purchase-policy | Free | `marketing` |
-| `WorkingAgreementPage` | `WebPage` | core | detail | /working-agreement | Free | `marketing` |
-| `LandingPage` | `WebPage` | core | home | /<slug> | Free | `marketing` |
-| `ThankYouPage` | `WebPage` | core | detail | /thanks/<slug> | Free | `marketing` |
-| `BookCall` | `WebPage` | core | home | /meet/:slug | Pro | `scheduling` |
-| `NewsletterSignup` | `WebPage` | core | home | /newsletter | Free | `marketing` |
-| `DemoRequest` | `WebPage` | core | home | /demo-request | Free | `marketing` |
-| `TrialSignup` | `WebPage` | core | home | /trial-signup | Free | `marketing` |
-| `Waitlist` | `WebPage` | core | home | /waitlist | Free | `marketing` |
-| `Assessment` | `WebApplication` | core | home | /assessment | Pro | `signal-collectors` |
-| `Calculator` | `WebApplication` | core | home | /calculator | Pro | `signal-collectors` |
-| `CampaignLP` | `WebPage` | core | home | /<slug> | Free | `marketing` |
-
-## Identity
-
-| Key | `@type` | Family | Chassis | Route | Level | Module |
-| --- | --- | --- | --- | --- | --- | --- |
-| `Organization` | `Organization` | identity | detail | — site-wide identity — emitted on the home page or in a layout | Free | `marketing` |
-| `Person` | `Person` | identity | detail | — site-wide identity — emitted on the home page or in a layout | Free | `marketing` |
-| `BreadcrumbList` | `BreadcrumbList` | identity | detail | — site-wide — attached alongside another page's own schema | Free | `marketing` |
-| `ContactPoint` | `ContactPoint` | identity | detail | — site-wide — embedded in `Organization` or `Person` | Free | `marketing` |
-
-## Canonical
-
-| Key | `@type` | Family | Chassis | Route | Level | Module |
-| --- | --- | --- | --- | --- | --- | --- |
-| `ServicesList` | `CollectionPage` | canonical-list | list | /services | Free | `marketing` |
-| `Service` | `Service` | canonical-detail | detail | /services/<slug> | Free | `marketing` |
-| `ProductsList` | `CollectionPage` | canonical-list | list | /products | Free | `marketing` |
-| `Product` | `Product` | canonical-detail | detail | /products/<slug> | Free | `marketing` |
-| `ProjectsList` | `CollectionPage` | canonical-list | list | /projects | Free | `marketing` |
-| `Project` | `CreativeWork` | canonical-detail | detail | /projects/<slug> | Free | `marketing` |
-| `FAQPage` | `FAQPage` | canonical-list | list | /faq | Free | `marketing` |
-| `CareersList` | `CollectionPage` | canonical-list | list | /careers | Free | `marketing` |
-| `JobPosting` | `JobPosting` | canonical-detail | detail | /careers/<slug> | Free | `marketing` |
-| `UseCasesList` | `CollectionPage` | canonical-list | list | /for | Free | `marketing` |
-| `UseCase` | `WebPage` | canonical-detail | detail | /for/<slug> | Free | `marketing` |
-| `PortfolioList` | `CollectionPage` | canonical-list | list | /portfolio | Free | `marketing` |
-| `PortfolioItem` | `WebPage` | canonical-detail | detail | /portfolio/<slug> | Free | `marketing` |
-| `FeaturesList` | `CollectionPage` | canonical-list | list | /features | Free | `marketing` |
-| `Feature` | `WebPage` | canonical-detail | detail | /features/<slug> | Free | `marketing` |
-| `ComparisonsList` | `CollectionPage` | canonical-list | list | /alternatives | Free | `marketing` |
-| `ComparisonPage` | `WebPage` | canonical-detail | detail | /vs/<slug> | Free | `marketing` |
-| `ReportsList` | `CollectionPage` | canonical-list | list | /reports | Free | `marketing` |
-| `ReportPage` | `Report` | canonical-detail | detail | /reports/<slug> | Pro | `signal-collectors` |
-| `TestimonialsList` | `CollectionPage` | canonical-list | list | /testimonials | Free | `marketing` |
-| `ClientsList` | `CollectionPage` | canonical-list | list | /clients | Free | `marketing` |
-| `DownloadsList` | `CollectionPage` | canonical-list | list | /downloads | Free | `marketing` |
-| `EventsList` | `CollectionPage` | canonical-list | list | /events | Free | `marketing` |
-| `Event` | `Event` | canonical-detail | detail | /events/<slug> | Free | `marketing` |
-| `CoursesList` | `CollectionPage` | canonical-list | list | /courses | Free | `marketing` |
-| `Course` | `Course` | canonical-detail | detail | /courses/<slug> | Free | `marketing` |
-| `TeamList` | `CollectionPage` | canonical-list | list | /team | Free | `marketing` |
-| `TeamMember` | `ProfilePage` | canonical-detail | detail | /team/<slug> | Free | `marketing` |
-| `PartnersList` | `CollectionPage` | canonical-list | list | /partners | Free | `marketing` |
-| `Partner` | `AboutPage` | canonical-detail | detail | /partners/<slug> | Free | `marketing` |
-| `IntegrationsList` | `CollectionPage` | canonical-list | list | /integrations | Free | `marketing` |
-| `Integration` | `WebPage` | canonical-detail | detail | /integrations/<slug> | Free | `marketing` |
-| `GlossaryList` | `CollectionPage` | canonical-list | list | /glossary | Free | `marketing` |
-| `LocationsList` | `CollectionPage` | canonical-list | list | /locations | Free | `marketing` |
-| `Location` | `Place` | canonical-detail | detail | /locations/<slug> | Free | `marketing` |
-| `DocsList` | `CollectionPage` | canonical-list | list | /docs | Pro | `docs-blog` |
-| `SoftwareProduct` | `WebPage` | canonical-detail | detail | /software/<slug> | Free | `marketing` |
-| `ServiceAreaPage` | `WebPage` | canonical-detail | detail | /service-areas/<slug> | Free | `marketing` |
-| `Pricing` | `WebPage` | canonical-detail | detail | /pricing | Free | `marketing` |
-
-## Editorial
-
-| Key | `@type` | Family | Chassis | Route | Level | Module |
-| --- | --- | --- | --- | --- | --- | --- |
-| `BlogList` | `Blog` | editorial-list | list | /blog | Free | `marketing` |
-| `BlogPosting` | `BlogPosting` | editorial-detail | detail | /blog/<slug> | Pro | `docs-blog` |
-| `ResourcesHub` | `CollectionPage` | editorial-list | list | /resources | Free | `marketing` |
-| `ResourceDetail` | `Article` | editorial-detail | detail | /resources/<slug> | Free | `marketing` |
-| `CaseStudiesList` | `CollectionPage` | editorial-list | list | /case-studies | Free | `marketing` |
-| `CaseStudy` | `Article` | editorial-detail | detail | /case-studies/<slug> | Free | `marketing` |
-| `HowTo` | `HowTo` | editorial-detail | detail | /how-to/<slug> | Free | `marketing` |
-| `Whitepaper` | `Article` | editorial-detail | detail | /whitepapers/<slug> | Free | `marketing` |
-| `TechArticle` | `TechArticle` | editorial-detail | detail | /tech-articles/<slug> | Free | `marketing` |
-| `DocsDetail` | `TechArticle` | editorial-detail | detail | /docs/<slug> | Pro | `docs-blog` |

package/templates/.claude/skills/add-page/scripts/site-pages.mjs

@@ -1,87 +0,0 @@
-#!/usr/bin/env node
-// site-pages.mjs — report what THIS site can serve, read from the site itself.
-//
-// Usage: node .claude/skills/add-page/scripts/site-pages.mjs [--json] [<site-root>]
-//
-// It scans apps/web/app/[locale]/**/page.tsx for the page type each route
-// renders (the `type: "X"` literal in renderPage / renderPageMetadata, or a
-// getMdxSource("X", …) call), then pairs each type with its content folder and
-// the pages already written there. It also echoes .ailk-site-manifest.json's
-// shape, design and (when recorded) level. Read-only: it never writes.
-import { existsSync, readdirSync, readFileSync, statSync } from "node:fs";
-import { join, relative, sep } from "node:path";
-
-const args = process.argv.slice(2);
-const asJson = args.includes("--json");
-const root = args.find((a) => !a.startsWith("--")) ?? process.cwd();
-const appRoot = join(root, "apps/web/app/[locale]");
-if (!existsSync(appRoot)) {
-  console.error(`site-pages: ${appRoot} not found — run from the site's root.`);
-  process.exit(2);
-}
-
-// Types whose content lives outside content/<locale>/<Type>.
-const CONTENT_OVERRIDES = {
-  BlogPosting: "apps/web/content/en/blog",
-  BlogList: "apps/web/content/en/blog",
-  DocsDetail: "apps/web/content/en/docs",
-  DocsList: "apps/web/content/en/docs",
-};
-
-function walk(dir, out = []) {
-  for (const name of readdirSync(dir)) {
-    const abs = join(dir, name);
-    if (name === "__tests__" || name === "node_modules") continue;
-    if (statSync(abs).isDirectory()) walk(abs, out);
-    else if (name === "page.tsx") out.push(abs);
-  }
-  return out;
-}
-
-const routes = [];
-for (const file of walk(appRoot)) {
-  const src = readFileSync(file, "utf8");
-  const types = new Set();
-  for (const m of src.matchAll(/type:\s*"([A-Z][A-Za-z]+)"/g)) types.add(m[1]);
-  for (const m of src.matchAll(/getMdxSource\(\s*"([A-Z][A-Za-z]+)"/g)) types.add(m[1]);
-  const dir = relative(appRoot, file).split(sep).slice(0, -1);
-  // Route groups like (auth) do not appear in the URL.
-  const path = "/" + dir.filter((s) => !/^\(.*\)$/.test(s)).join("/");
-  const dynamic = dir.some((s) => s.startsWith("["));
-  routes.push({ route: path === "/" ? "/" : path, file: relative(root, file), types: [...types], dynamic });
-}
-
-const byType = {};
-for (const r of routes) {
-  for (const t of r.types) {
-    const entry = (byType[t] ??= { type: t, routes: [], contentDir: CONTENT_OVERRIDES[t] ?? `content/en/${t}`, pages: [] });
-    entry.routes.push(r.route);
-  }
-}
-for (const e of Object.values(byType)) {
-  const abs = join(root, e.contentDir);
-  if (existsSync(abs)) {
-    e.pages = readdirSync(abs).filter((f) => /\.mdx?$/.test(f)).map((f) => f.replace(/\.mdx?$/, ""));
-  }
-  // A type served by a dynamic route takes new pages; a static-only type is one page.
-  e.takesNewPages = routes.some((r) => r.dynamic && r.types.includes(e.type));
-}
-
-let manifest = null;
-const manifestPath = join(root, ".ailk-site-manifest.json");
-if (existsSync(manifestPath)) {
-  const m = JSON.parse(readFileSync(manifestPath, "utf8"));
-  manifest = { shape: m.shape ?? null, design: m.design ?? null, level: m.level ?? null, modules: m.modules ?? m.requires ?? null };
-}
-
-const result = { manifest, types: Object.values(byType).sort((a, b) => a.type.localeCompare(b.type)) };
-if (asJson) {
-  console.log(JSON.stringify(result, null, 2));
-} else {
-  if (manifest) console.log(`shape: ${manifest.shape}  design: ${manifest.design}  level: ${manifest.level ?? "(not recorded)"}`);
-  console.log("");
-  console.log("type".padEnd(22) + "route(s)".padEnd(34) + "new pages?".padEnd(12) + "existing");
-  for (const e of result.types) {
-    console.log(e.type.padEnd(22) + e.routes.join(" ").padEnd(34) + (e.takesNewPages ? "yes" : "no").padEnd(12) + (e.pages.join(", ") || "—"));
-  }
-}

package/templates/.claude/skills/add-page/templates/comparison-page.mdx.tmpl

@@ -1,99 +0,0 @@
----
-type: ComparisonPage
-slug: {{SLUG}}
-placeholder: true
-title: {{TITLE}}
-description: {{DESCRIPTION}}
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "eyebrow": "Comparisons",
-          "headline": "{{TITLE}}",
-          "subheadline": "{{DESCRIPTION}}",
-          "primaryCta": { "label": "{Primary CTA}", "href": "/contact" },
-        },
-    },
-    {
-      "id": "decision-split",
-      "type": "decision-split",
-      "data":
-        {
-          "headline": "{Which one fits you}",
-          "panels":
-            [
-              {
-                "title": "{{TITLE}}",
-                "checklist":
-                  [
-                    "{Reason 1 to choose us}",
-                    "{Reason 2 to choose us}",
-                    "{Reason 3 to choose us}",
-                  ],
-              },
-              {
-                "title": "{The alternative}",
-                "glyph": "cross",
-                "checklist":
-                  [
-                    "{Reason 1 to choose them instead}",
-                    "{Reason 2 to choose them instead}",
-                  ],
-              },
-            ],
-        },
-    },
-    {
-      "id": "comparison-table",
-      "type": "comparison-table",
-      "data":
-        {
-          "headline": "{How they compare}",
-          "columns":
-            [
-              { "key": "us", "name": "{{TITLE}}", "highlighted": true },
-              { "key": "them", "name": "{The alternative}" },
-            ],
-          "groups":
-            [
-              {
-                "groupName": "{Core features}",
-                "rows":
-                  [
-                    {
-                      "featureName": "{Feature 1}",
-                      "values": { "us": true, "them": false },
-                    },
-                    {
-                      "featureName": "{Feature 2}",
-                      "values": { "us": true, "them": true },
-                    },
-                  ],
-              },
-            ],
-        },
-    },
-    {
-      "id": "cta",
-      "type": "cta",
-      "data":
-        {
-          "variant": "box",
-          "headline": "{Ready to switch?}",
-          "description": "{One sentence on what happens next}",
-          "primaryCta": { "label": "{Primary CTA}", "href": "/contact" },
-          "secondaryCta":
-            {
-              "label": "See all alternatives",
-              "href": "/alternatives",
-              "variant": "outline",
-            },
-        },
-    },
-  ]
----
-
-{/* Rendered from frontmatter `sections[]` by the /vs/<slug> route (D10 — the generic detail chassis: hero, decision-split, comparison-table, cta; no dedicated comparison section). Listed automatically by the /alternatives hub. Placeholder copy — replace every {brace} with your own words before you launch. */}

package/templates/.claude/skills/add-page/templates/content.mdx.tmpl

@@ -1,18 +0,0 @@
----
-type: {{TYPE}}
-slug: {{SLUG}}
-title: {{TITLE}}
-description: {{DESCRIPTION}}
----
-
-{/*
-  Written by the add-page skill, used only when this site had no other page of
-  this type to copy. The frontmatter drives the page's route and its JSON-LD:
-  keep `type` as it is, and make `description` a true one-sentence summary.
-  Run `fill-page` to write the real copy, then `check-site` to score it.
-  Extra structured data goes in a `schema:` block — see the add-page skill.
-*/}
-
-# {{TITLE}}
-
-{{DESCRIPTION}}

package/templates/.claude/skills/add-page/templates/flow-landing-page.mdx.tmpl

@@ -1,43 +0,0 @@
----
-type: LandingPage
-slug: {{SLUG}}
-placeholder: true
-title: {{TITLE}}
-description: {{DESCRIPTION}}
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "variant": "centered",
-          "eyebrow": "{{TITLE}}",
-          "headline": "{{TITLE}}",
-          "subheadline": "{{DESCRIPTION}}",
-          "primaryCta":
-            { "label": "{Get started →}", "href": "/flows/{{FLOW_SLUG}}/start" },
-          "ctaSize": "xl",
-        },
-    },
-    {
-      "id": "request",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "{Ready?}",
-          "primaryCta":
-            { "label": "{Get started →}", "href": "/flows/{{FLOW_SLUG}}/start" },
-        },
-    },
-  ]
----
-
-{/* This page's CTA opens the `{{FLOW_SLUG}}` flow at
-    /flows/{{FLOW_SLUG}}/start — a signal-collectors module route, not a page
-    this seed owns. The flow definition itself
-    (`database/flows/{{FLOW_SLUG}}.flow.json`) is a separate artifact this
-    skill does not write; seed it via the flow engine before this page's CTA
-    resolves. Placeholder copy — replace every {brace} with your own words
-    before you launch. */}