create-ailk 0.3.0 → 0.5.0

package/site-templates/minimalism-site/content/en/ReportPage/annual-letter-2024.mdx

@@ -0,0 +1,52 @@
+---
+type: "ReportPage"
+slug: "annual-letter-2024"
+title: "Annual Letter"
+description: "{One line on the question this report answers. Replace before you launch.}"
+schema:
+  datePublished: "2024-12-09"
+  author:
+    "@type": Organization
+    name: "Your Company"
+sections:
+  [
+    {
+      "id": "header",
+      "type": "report-header",
+      "data":
+        {
+          "title": "Annual Letter",
+          "eyebrow": "December 2024",
+          "backHref": "/reports",
+          "backLabel": "All reports",
+          "tone": "on-dark",
+        },
+    },
+    {
+      "id": "document",
+      "type": "document-viewer",
+      "data":
+        {
+          "src": "/reports/sample-report.pdf",
+          "geometry": "16:9",
+          "pages": 8,
+          "downloadFilename": "annual-letter-2024.pdf",
+          "outline":
+            [
+              { "id": "opening", "label": "Opening", "startPage": 1 },
+              { "id": "findings", "label": "Findings", "startPage": 3 },
+              { "id": "outlook", "label": "Outlook", "startPage": 6 },
+            ],
+        },
+    },
+  ]
+---
+
+{/_
+A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
+PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
+bundle), shared by all four samples so the template ships no binary of its
+own. Point `src` at your real document and set `pages` to its real page
+count — the count reserves the reader's layout before the renderer loads, so
+a wrong number shows as a jump.
+_/}

package/site-templates/minimalism-site/content/en/ReportPage/field-notes-2023.mdx

@@ -0,0 +1,52 @@
+---
+type: "ReportPage"
+slug: "field-notes-2023"
+title: "Field Notes"
+description: "{One line on the question this report answers. Replace before you launch.}"
+schema:
+  datePublished: "2023-09-19"
+  author:
+    "@type": Organization
+    name: "Your Company"
+sections:
+  [
+    {
+      "id": "header",
+      "type": "report-header",
+      "data":
+        {
+          "title": "Field Notes",
+          "eyebrow": "2023",
+          "backHref": "/reports",
+          "backLabel": "All reports",
+          "tone": "on-dark",
+        },
+    },
+    {
+      "id": "document",
+      "type": "document-viewer",
+      "data":
+        {
+          "src": "/reports/sample-report.pdf",
+          "geometry": "16:9",
+          "pages": 8,
+          "downloadFilename": "field-notes-2023.pdf",
+          "outline":
+            [
+              { "id": "opening", "label": "Opening", "startPage": 1 },
+              { "id": "findings", "label": "Findings", "startPage": 3 },
+              { "id": "outlook", "label": "Outlook", "startPage": 6 },
+            ],
+        },
+    },
+  ]
+---
+
+{/_
+A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
+PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
+bundle), shared by all four samples so the template ships no binary of its
+own. Point `src` at your real document and set `pages` to its real page
+count — the count reserves the reader's layout before the renderer loads, so
+a wrong number shows as a jump.
+_/}

package/site-templates/minimalism-site/content/en/ReportPage/platform-shift-2025.mdx

@@ -0,0 +1,52 @@
+---
+type: "ReportPage"
+slug: "platform-shift-2025"
+title: "The {Platform Shift} Report"
+description: "{One line on the question this report answers. Replace before you launch.}"
+schema:
+  datePublished: "2025-03-11"
+  author:
+    "@type": Organization
+    name: "Your Company"
+sections:
+  [
+    {
+      "id": "header",
+      "type": "report-header",
+      "data":
+        {
+          "title": "The {Platform Shift} Report",
+          "eyebrow": "March 2025",
+          "backHref": "/reports",
+          "backLabel": "All reports",
+          "tone": "on-dark",
+        },
+    },
+    {
+      "id": "document",
+      "type": "document-viewer",
+      "data":
+        {
+          "src": "/reports/sample-report.pdf",
+          "geometry": "16:9",
+          "pages": 8,
+          "downloadFilename": "platform-shift-2025.pdf",
+          "outline":
+            [
+              { "id": "opening", "label": "Opening", "startPage": 1 },
+              { "id": "findings", "label": "Findings", "startPage": 3 },
+              { "id": "outlook", "label": "Outlook", "startPage": 6 },
+            ],
+        },
+    },
+  ]
+---
+
+{/_
+A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
+PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
+bundle), shared by all four samples so the template ships no binary of its
+own. Point `src` at your real document and set `pages` to its real page
+count — the count reserves the reader's layout before the renderer loads, so
+a wrong number shows as a jump.
+_/}

package/site-templates/minimalism-site/content/en/ReportPage/state-of-the-market-2026.mdx

@@ -0,0 +1,52 @@
+---
+type: "ReportPage"
+slug: "state-of-the-market-2026"
+title: "State of {Your Market} 2026"
+description: "{One line on the question this report answers. Replace before you launch.}"
+schema:
+  datePublished: "2026-05-14"
+  author:
+    "@type": Organization
+    name: "Your Company"
+sections:
+  [
+    {
+      "id": "header",
+      "type": "report-header",
+      "data":
+        {
+          "title": "State of {Your Market} 2026",
+          "eyebrow": "May 2026",
+          "backHref": "/reports",
+          "backLabel": "All reports",
+          "tone": "on-dark",
+        },
+    },
+    {
+      "id": "document",
+      "type": "document-viewer",
+      "data":
+        {
+          "src": "/reports/sample-report.pdf",
+          "geometry": "16:9",
+          "pages": 8,
+          "downloadFilename": "state-of-the-market-2026.pdf",
+          "outline":
+            [
+              { "id": "opening", "label": "Opening", "startPage": 1 },
+              { "id": "findings", "label": "Findings", "startPage": 3 },
+              { "id": "outlook", "label": "Outlook", "startPage": 6 },
+            ],
+        },
+    },
+  ]
+---
+
+{/_
+A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
+PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
+bundle), shared by all four samples so the template ships no binary of its
+own. Point `src` at your real document and set `pages` to its real page
+count — the count reserves the reader's layout before the renderer loads, so
+a wrong number shows as a jump.
+_/}

package/site-templates/minimalism-site/content/en/Service/first-engagement.mdx

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

package/site-templates/minimalism-site/content/en/Service/second-engagement.mdx

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

package/site-templates/minimalism-site/content/en/Service/third-engagement.mdx

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

package/site-templates/minimalism-site/content/en/ServicesList/services.mdx

@@ -0,0 +1,73 @@
+---
+type: "ServicesList"
+slug: "services"
+title: "Services"
+description: "The three engagements {your company} offers. Placeholder copy — replace before you launch."
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "variant": "centered",
+          "eyebrow": "Services",
+          "headline": "Three ways to work together",
+          "subheadline": "{One line on how to choose between them. Name the question a reader is actually asking.}",
+        },
+    },
+    {
+      "id": "engagements",
+      "type": "items",
+      "data":
+        {
+          "headline": "Engagements",
+          "columns": 3,
+          "items":
+            [
+              {
+                "title": "{First engagement}",
+                "description": "{One line on what it is and who it suits.}",
+                "link":
+                  {
+                    "label": "Read more",
+                    "href": "/services/first-engagement",
+                  },
+              },
+              {
+                "title": "{Second engagement}",
+                "description": "{One line on what it is and who it suits.}",
+                "link":
+                  {
+                    "label": "Read more",
+                    "href": "/services/second-engagement",
+                  },
+              },
+              {
+                "title": "{Third engagement}",
+                "description": "{One line on what it is and who it suits.}",
+                "link":
+                  {
+                    "label": "Read more",
+                    "href": "/services/third-engagement",
+                  },
+              },
+            ],
+        },
+    },
+    {
+      "id": "closing",
+      "type": "cta",
+      "data":
+        {
+          "variant": "minimal",
+          "headline": "Not sure which one?",
+          "description": "{One line inviting the reader to book the call instead of guessing.}",
+          "primaryCta": { "label": "Hire me →", "href": "/meet" },
+        },
+    },
+  ]
+---
+
+{/_ Placeholder copy. The three detail pages under `content/en/Service/` carry
+the long form; this page is the chooser. _/}

package/site-templates/minimalism-site/flows/referral.flow.json

@@ -0,0 +1,71 @@
+{
+  "slug": "referral",
+  "defaultLocale": "en",
+  "steps": [
+    {
+      "key": "introduction",
+      "type": "field",
+      "copy": {
+        "title": {
+          "en": "Who should we meet?"
+        }
+      },
+      "fields": [
+        {
+          "name": "referrer_name",
+          "inputType": "text",
+          "required": true,
+          "mapsTo": "name",
+          "copy": {
+            "label": {
+              "en": "Your name"
+            },
+            "help": {
+              "en": "So we can tell them who sent us."
+            }
+          }
+        },
+        {
+          "name": "referrer_email",
+          "inputType": "email",
+          "required": true,
+          "mapsTo": "email",
+          "copy": {
+            "label": {
+              "en": "Your email"
+            },
+            "help": {
+              "en": "Where we tell you how it went."
+            }
+          }
+        },
+        {
+          "name": "referral_details",
+          "inputType": "textarea",
+          "required": true,
+          "minLength": 20,
+          "copy": {
+            "label": {
+              "en": "Who are they, and why them?"
+            },
+            "placeholder": {
+              "en": "Their name, a way to reach them, and one line on why you thought of them."
+            }
+          }
+        }
+      ]
+    },
+    {
+      "key": "sent",
+      "type": "message",
+      "copy": {
+        "title": {
+          "en": "Thank you — the introduction is in"
+        },
+        "body": {
+          "en": "We will reach out within a few days and let you know either way. Placeholder copy: replace it with what you actually do."
+        }
+      }
+    }
+  ]
+}

package/site-templates/minimalism-site/provenance.json

@@ -0,0 +1,4 @@
+{
+  "template": "minimalism-site",
+  "requires": ["marketing", "scheduling", "signal-collectors"]
+}

package/site-templates/saas-product/TEMPLATE-MANIFEST.md

@@ -0,0 +1,61 @@
+# Template manifest — `saas-product`
+
+> **Stub (#5626).** Sam split #5470 on 2026-09-15: this tree lands the registered template and the `multi-tenant` delivery fix it depends on; the designed template — compositions, copy, knobs, demo data — is **#5470**, after his design conversation and the composition model (#5618). Everything below § 2 is therefore a roster and a pointer, not a page design. Same generated-file rule as its siblings: once the compositions are approved this file is produced by the manifest generator from the roster (base + module `pageContributions`), each page's MDX `sections`, and `component-catalog.json`.
+
+| Field       | Value                                                                                                      |
+| ----------- | ---------------------------------------------------------------------------------------------------------- |
+| Template    | `saas-product`                                                                                             |
+| Level       | Pro Plus (`template-level.ts` derives it from `requires`)                                                  |
+| `requires`  | `[marketing, docs-blog, scheduling, signal-collectors, multi-tenant]` (spec 5462 D12, settled 2026-09-14)  |
+| Delivery    | licence-checked template bundle (#5441), `installMap` for the provenance record; never in the Free tarball |
+| Own content | **none** — see § 3                                                                                         |
+
+## 1. What this tree carries today
+
+| File                   | Role                                                                                                                                     |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| `ailk-template.json`   | the committed `installMap` / `postInstall`; `name`, `version` and `requires` are producer-emitted from `TEMPLATE_MANIFESTS` (record D10) |
+| `provenance.json`      | lands at `.ailk-template.json` in the scaffold, naming the template and its `requires`                                                   |
+| `TEMPLATE-MANIFEST.md` | this file                                                                                                                                |
+
+`build-module-bundles.mjs --templates saas-product` lists exactly those three plus the emitted root `ailk-template.json` and the proprietary `LICENSE` (#5552 D1).
+
+## 2. Roster — the base rows, as the registry declares them
+
+`saas-product` reuses `TEMPLATE_BASE_ROSTER` (`template-manifest.ts`) and declares no rows of its own. The ten base routes:
+
+```
+/  ·  /how-it-works  ·  /features  ·  /pricing  ·  /about
+/faq  ·  /contact  ·  /sign-in  ·  /privacy  ·  /terms
+```
+
+Module-contributed rows arrive from `MODULE_SLICES[*].pageContributions` and are listed here so the page set reads as one:
+
+```
+docs-blog:          /blog  ·  /blog/<slug>  ·  /docs  ·  /docs/<slug>
+scheduling:         /meet  ·  /meet/<slug>  ·  /meet/confirmed   (renamed from the schedule/ route by #5563)
+signal-collectors:  /flows/<slug>  ·  /flows/<slug>/start  ·  /flows/<slug>/results/<payload>
+                    /projects  ·  /projects/<slug>  ·  /projects/apply  ·  /waitlist/<experimentId>
+                    /thanks/<slug>                                (per form)
+multi-tenant:       no roster row — its whole surface is the separate authed
+                    `apps/workspace` Next.js app, delivered by the module bundle
+                    rather than through the roster merge (spec 5470 § Clarifications, D2)
+```
+
+## 3. Compositions — pending (#5470)
+
+This tree deliberately carries **no `content/`**. Two layers already own the pages a Pro Plus site renders, and duplicating either here would have to be undone when the designed template lands:
+
+- the **base pages** (`/`, `/pricing`, `/privacy`, `/terms`, …) arrive with **#5618**'s base layer;
+- the **module pages** (blog, docs, schedule, flows, projects, waitlist, and the whole `apps/workspace` app) arrive with each module's **own bundle**.
+
+What **#5470** adds on top, once Sam's design conversation and the composition model (#5618) settle: the per-page section compositions and their order, the verbatim copy, the template knobs, and the demo data a Pro Plus site ships with. Until then a keyed `--template saas-product` install is honest — it delivers the provenance record, cross-checks `requires` against the installing client's registry, and lets every required module deliver its own surface.
+
+## 4. Known gaps this manifest depends on
+
+| Gap                                                                                     | Issue |
+| --------------------------------------------------------------------------------------- | ----- |
+| The designed template (compositions, copy, knobs, demo)                                 | #5470 |
+| The composition model the design is authored against                                    | #5618 |
+| The `/meet` composition per the Pro manifest (deferred by #5563, blocked on §7 Q1)      | #5670 |
+| A full-CLI keyed `--template` success test (the mock registry serves no template bytes) | #5467 |

package/site-templates/saas-product/ailk-template.json

@@ -0,0 +1,16 @@
+{
+  "name": "saas-product",
+  "requires": [
+    "marketing",
+    "docs-blog",
+    "scheduling",
+    "signal-collectors",
+    "multi-tenant"
+  ],
+  "extends": "_base",
+  "$comment": "Pro Plus template, STUB (#5626). name/version/requires are producer-emitted from TEMPLATE_MANIFESTS at build time and are never the authoritative value on disk (record D10); the committed copy agrees with the registry so the tree and the registry never read as disagreeing. installMap: bundle-relative source -> scaffold-relative destination; the stager reads only installMap/postInstall/patches. This tree carries NO content of its own: the base pages arrive with #5618's base layer and the module pages with each module's own bundle, so the designed template (#5470) drops in as content only, with nothing here to undo.",
+  "installMap": {
+    "provenance.json": ".ailk-template.json"
+  },
+  "postInstall": "Template saas-product installed. Its Pro Plus modules - docs-blog, scheduling, signal-collectors and multi-tenant (the authed apps/admin app) - are delivered by their own module bundles. This template's own page compositions, copy and demo data are pending under #5470; until they land it contributes the provenance record and its requires cross-check only, and the scaffold renders each module's own seed content."
+}

package/site-templates/saas-product/provenance.json

@@ -0,0 +1,10 @@
+{
+  "template": "saas-product",
+  "requires": [
+    "marketing",
+    "docs-blog",
+    "scheduling",
+    "signal-collectors",
+    "multi-tenant"
+  ]
+}

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

@@ -4,41 +4,32 @@ Skills are reusable Claude Code workflows scoped to this project. Each
 lives in its own subdirectory with a `SKILL.md` describing when to use
 it and how it works.
 
-The seven OSS skills below are the canonical AI Launch Kit workflows.
-Their status reflects what's available at the upstream
-<https://github.com/working-theory-labs/ai-launch-kit> repository today. Issue
-numbers in the table refer to that upstream repo (the
-`working-theory-labs/ai-launch-kit#N` form makes the link explicit), not your
-local project's issues.
-
-## Status
-
-| Skill                | Purpose                                                | Status                                               |
-| -------------------- | ------------------------------------------------------ | ---------------------------------------------------- |
-| `suggest-site-pages` | Generic page-type suggestions by category              | coming soon — issue #361 (working-theory-labs/ai-launch-kit) |
-| `scaffold-page`      | Generate a page with the appropriate schema.org type   | coming soon — issue #362 (working-theory-labs/ai-launch-kit) |
-| `scaffold-auth`      | Wire up an auth flow against `@working-theory/auth-client`       | coming soon — issue #364 (working-theory-labs/ai-launch-kit) |
-| `audit-site`         | Run `ailk audit` and explain the results               | coming soon — issue #365 (working-theory-labs/ai-launch-kit) |
-| `add-schema`         | Add Product / Service / FAQ schema to an existing page | coming soon — issue #366 (working-theory-labs/ai-launch-kit) |
-| `provision-config`   | Generate `vercel.json` and environment templates       | coming soon — issue #367 (working-theory-labs/ai-launch-kit) |
+The six skills below ship with this project. Claude Code discovers
+them automatically at session start — nothing to install or enable.
+
+## Available skills
+
+| Skill                 | Purpose                                                                                                 |
+| ---------------------- | -------------------------------------------------------------------------------------------------------- |
+| `suggest-site-pages`  | Recommend a starter set of pages — each tagged with a schema.org type — from a free-text business description. |
+| `scaffold-page`       | Generate a new page: App Router route + MDX content stub + typed JSON-LD, in one confirm-before-write pass. |
+| `add-schema`          | Add or replace schema.org JSON-LD on a page that already exists.                                        |
+| `scaffold-auth`       | Activate auth providers — magic-link via Resend, Google OAuth, GitHub OAuth.                            |
+| `provision-config`    | Emit deploy configuration — `vercel.json`, `.env.example`, and `RUNBOOK.md` — for a Vercel deploy.       |
+| `audit-site`          | Run `ailk-audit --json` and explain the score and findings in plain language.                           |
 
 `scaffold-commerce` is delivered with the commerce module (`--modules commerce`, licensed).
 
-## How a skill ships
+## How a skill works
 
-When a skill is built upstream, this directory will contain a
-subdirectory of the same name, each holding:
+Each subdirectory holds:
 
 - `SKILL.md` — when to invoke, what it produces, what it requires.
 - Any supporting prompt fragments, code templates, or reference
   files the skill loads at runtime.
 
-Until then, the workflows the skills will perform can still be done
-by hand or by asking Claude Code directly.
-
 ## Adding your own
 
 To add a project-specific skill, create a folder here with a
 `SKILL.md` describing it. Claude Code will discover it automatically
-on session start. See the upstream `@working-theory/*` repository for examples
-of the format.
+on session start. See the skills above for examples of the format.