Skip to content

Anti-AI-slop design skill for Claude Code, Cursor, and Codex.

CSS

Perf · split macros + components per-item, lazy-load slop-test, extract preview examples

Youssef546ddfac867f
diff --git a/skill/SKILL.md b/skill/SKILL.md
index c6722c1..4a124ba 100644
--- a/skill/SKILL.md
+++ b/skill/SKILL.md
@@ -252,7 +252,7 @@ Once the three are settled (asked or inferred), restate them in one sentence and
### 2. Pick a macrostructure FIRST
-Before loading any visual ruleset, **pick one of the twenty-one named macrostructures in [`references/macrostructures.md`](references/macrostructures.md).** Each macrostructure is a complete page-shape — heading placement, body composition, divider language, button voice, image treatment, reveal — bundled as a single named choice. Picking one named macrostructure is faster and more varied than choosing six independent axes from scratch.
+Before loading any visual ruleset, **read the slim index at [`references/macrostructures.md`](references/macrostructures.md) and pick one of the twenty-one named macrostructures.** The index is one-line-per-macro; pick a name, then **load ONLY that one per-macro file** from `references/macrostructures/` (e.g. `references/macrostructures/05-workbench.md`). Do not load the whole catalogue — that's ~37 KB of dead weight for a single pick. Each macrostructure is a complete page-shape — heading placement, body composition, divider language, button voice, image treatment, reveal — bundled as a single named choice. Picking one named macrostructure is faster and more varied than choosing six independent axes from scratch.
**Diversification rule (mandatory).** Before you pick:
@@ -276,7 +276,7 @@ If the brief is genuinely vague (no theme, no tone), do **not** default. Offer t
The macrostructure picks five of the six structural axes for you; you only need to pick the reveal yourself. The deeper axis catalogue is still in [`references/structure.md`](references/structure.md) when you need to deviate from the macrostructure's defaults.
-**Pick a nav archetype (N1–N9) and a footer archetype (Ft1–Ft8) at this step.** They are not optional chrome; they are part of the page's structural fingerprint. Read the routing tables in [`references/component-cookbook.md`](references/component-cookbook.md) § Navigation and § Footers — the genre's default plus the acceptable alternates. State both picks alongside the macrostructure: *"Macrostructure: Marquee Hero. Nav: N5 Floating pill. Footer: Ft5 Statement. Theme: Bloom."*
+**Pick a nav archetype (N1–N10) and a footer archetype (Ft1–Ft8) at this step.** They are not optional chrome; they are part of the page's structural fingerprint. Read the slim index at [`references/component-cookbook.md`](references/component-cookbook.md) and the routing tables at its bottom — the genre's default plus the acceptable alternates. Then **load ONLY the picked archetype files** from `references/components/` (e.g. `components/n5-floating-pill.md` + `components/ft5-statement.md`). A typical build loads 5–7 archetype files total (1 hero + 1 section head + 1–2 features + 1 CTA + 1 footer + 1 nav). Do not load the cookbook end-to-end — that's ~55 KB of archetypes you won't use. State both picks alongside the macrostructure: *"Macrostructure: Marquee Hero. Nav: N5 Floating pill. Footer: Ft5 Statement. Theme: Bloom."*
**Default away from N1 and Ft3.** N1 (wordmark + 4–5 inline links + button-right at full width) and Ft3 (4 columns of links + social row + tiny copyright) are the most-recognised AI fingerprints. Reach for N5–N9 and Ft1/Ft2/Ft4/Ft5/Ft6/Ft7/Ft8 by default; reach for N1 only when the page genuinely has 2 destinations and the genre allows it; reach for Ft3 only on a genuine docs root or hub.
@@ -335,34 +335,37 @@ The diversification rule is theme-route-blind: a custom run that follows another
### 3. Load the visual ruleset
-The non-negotiables live in [`references/`](references/). **Be precise about what to load when.** Loading every file every time costs ~40k tokens; loading only what's needed costs ~15k. Discipline matters.
+The non-negotiables live in [`references/`](references/). **Be precise about what to load when. Discipline matters — over-eager loading is the largest avoidable cost of running Hallmark.**
-**Always-load (the eager bundle, ~3 files):**
+**Always-load (eager — 1 file):**
- The genre file picked in Step 1 — [`genres/editorial.md`](references/genres/editorial.md), [`genres/modern-minimal.md`](references/genres/modern-minimal.md), [`genres/atmospheric.md`](references/genres/atmospheric.md), or [`genres/playful.md`](references/genres/playful.md). Scopes everything downstream.
-- [`macrostructures.md`](references/macrostructures.md) — 21 named whole-page shapes; you must pick one before writing code (Step 2 already required this).
-- [`component-cookbook.md`](references/component-cookbook.md) — 40 component archetypes (9 hero shapes, 6 feature blocks, 4 CTA shapes, 4 testimonials, **8 footer archetypes**, **9 nav archetypes**) composable into any macrostructure. Per-genre routing tables for nav and footer live at the bottom of the file.
+
+**Index-then-pick (read the slim index, then load only the picks):**
+- [`macrostructures.md`](references/macrostructures.md) — slim index of the 21 macros. Pick one name from the index, then load ONLY `references/macrostructures/<NN-slug>.md` for that pick. **Never load the whole index plus more than one per-macro file in a single build.** ~30 lines per per-macro file vs. 660 lines for the old monolith.
+- [`component-cookbook.md`](references/component-cookbook.md) — slim index of 46 component archetypes (9 heroes, 5 section heads, 6 features, 4 CTAs, 4 testimonials, 8 footers, 10 navs) + the nav + footer routing tables at the bottom. Pick your archetype codes (H#, S#, F#, C#, T#, Ft#, N#) from the index, then load ONLY the matching `references/components/<code>-<slug>.md` files. A typical build loads 5–7 archetype files. **Loading the cookbook end-to-end or pre-loading more than one archetype per category is the single biggest token waste in the skill — don't.**
**Load-per-build (universal rules — load every build):**
-- [`typography.md`](references/typography.md) — fonts, scale, pairing, weights, measure
+- [`typography.md`](references/typography.md) — fonts, scale, pairing, weights, measure, hero headline sizing
- [`color.md`](references/color.md) — OKLCH, palette construction, accent discipline
- [`layout-and-space.md`](references/layout-and-space.md) — 4 pt scale, grid-breaks, asymmetry, depth
- [`motion.md`](references/motion.md) — durations, easings, what to animate, reduced-motion
- [`copy.md`](references/copy.md) — verbs, labels, error structure, link text
- [`anti-patterns.md`](references/anti-patterns.md) — the named tells you must not emit
-**Load-conditionally (only when the page actually needs it):**
+**Load-conditionally (only when the page actually needs it — be honest, do not pre-load "for safety"):**
- [`microinteractions.md`](references/microinteractions.md) — load whenever the output has *any* interactive element (buttons, inputs, modals, tabs, dropdowns, toasts, drag handles, copy buttons). That is most pages.
- [`interaction-and-states.md`](references/interaction-and-states.md) — load when the page has stateful UI (forms, command palettes, optimistic updates).
- [`responsive.md`](references/responsive.md) — load when mobile is in scope.
- [`structure.md`](references/structure.md) — load only when deviating from a named macrostructure.
-- [`hero-enrichment.md`](references/hero-enrichment.md) — load at Step 4 if the brief asks for enrichment.
+- [`hero-enrichment.md`](references/hero-enrichment.md) — **do NOT load at Step 4 unless the image-need check in the next paragraph returns YES.** Most builds are typography-only and never touch this file. The decision is one quick read of the brief, not a defensive auto-load.
- [`custom-craft.md`](references/custom-craft.md) — load only when an enrichment archetype requires construction (CSS art, SVG, declarative animation, etc.).
- [`assets.md`](references/assets.md) — load only when an enrichment archetype needs an external asset (icons, illustration, photography, Lottie).
-- [`custom-theme.md`](references/custom-theme.md) — load only when Step 2.6 routes to custom.
+- [`custom-theme.md`](references/custom-theme.md) — load only when Step 2.6 routes to custom. The full custom branch (palette construction, font pairing, axis computation) lives there; SKILL.md only carries the dispatch.
- [`design-md.md`](references/design-md.md) — load only when the user explicitly asks Hallmark to lock the system into a portable file (phrases: *"lock the system"*, *"give me a design.md"*, *"make this portable"*, etc.). Opt-in; never fires on a vanilla build.
+- [`preview-examples.md`](references/preview-examples.md) — load only if you need a worked example of the Step 5 preview block format. The bullet list in Step 5 itself is normally enough; reach for the file only when picking unusual macrostructures / custom themes.
-**Load-at-the-end:**
-- [`slop-test.md`](references/slop-test.md) — load at Step 7 (the gate-check after build), not earlier.
+**Load-at-the-end (Step 7 only):**
+- [`slop-test.md`](references/slop-test.md) — **strictly Step 7, after Build.** The 66 gates are a post-emit check, not a pre-emit reference. Pre-loading slop-test.md costs ~7K tokens for nothing — the gates inform fixes, not generation. If a gate fails at Step 7, fix and re-test; do not consult the file earlier "to know what to avoid" — that's what `anti-patterns.md` is for.
- [`contract.md`](references/contract.md) — load at handoff time for output-contract + scope rules.
- [`export-formats.md`](references/export-formats.md) — load at Step 6 only when the project warrants multi-format exports (i.e. has a `design.md`). Single-page builds emit `tokens.css` from the in-memory token state and don't need this file.
@@ -400,7 +403,7 @@ Before emitting any code, output a tight summary of what you're about to ship. T
- **Enrichment** · none (typography only)
- **Sections** · Hero · Logos · Stats · Features · Testimonials · Pricing · FAQ · CTA · Footer
- **Motion** · counter · pricing-lift · pulse-once
-- **Slop test** · 65 / 65 ✓ (run after Build)
+- **Slop test** · 66 / 66 ✓ (run after Build)
- **Diversification** · differs from Linen on display style + accent hue
```
@@ -411,7 +414,7 @@ Before emitting any code, output a tight summary of what you're about to ship. T
3. **Enrichment** — the chosen archetype + tier, or *none (typography only)*.
4. **Sections** — section names separated by ` · `, in DOM order.
5. **Motion** — microinteraction primitives separated by ` · `, or *none — typography only*. Always under three primitives per the [`microinteractions.md`](references/microinteractions.md) hard rules.
-6. **Slop test** — `65 / 65 ✓` if all gates pass, or `N / 65 — fails: <gate numbers>` if any are open. Run the slop test BEFORE writing this row; the slop test is Step 7.
+6. **Slop test** — `66 / 66 ✓` if all gates pass, or `N / 66 — fails: <gate numbers>` if any are open. Run the slop test BEFORE writing this row; the slop test is Step 7.
7. **Diversification** *(optional, only when `.hallmark/log.json` has prior entries)* — what axes differ vs the previous run.
**Then one quiet CTA line, italicised, after the bullets:**
@@ -420,51 +423,7 @@ Before emitting any code, output a tight summary of what you're about to ship. T
Skip the CTA line when (a) the build is component-scope, or (b) `design.md` already exists at the project root (the system is already locked). See [`design-md.md`](references/design-md.md) for the full opt-in flow.
-**Three more sample preview blocks** for the model to imitate, varied across macrostructure types:
-
-*Long Document (editorial, motion-cut):*
-> **Hallmark · v1.0.0**
->
-> - **Macrostructure** · Long Document
-> - **Theme** · Linen (cool slate paper · steel-blue accent · geometric sans)
-> - **Enrichment** · Tier-B hand-built SVG (a 60-line coffee bean with `@property --rise` 6 s breathing-loop)
-> - **Sections** · Masthead · Letter · Three Notes · Visit · Colophon
-> - **Motion** · breathing-loop on bean only (respects `prefers-reduced-motion`)
-> - **Slop test** · 65 / 65 ✓
-> - **Diversification** · first run for this project
-
-*Bento Grid (SaaS, motion-on):*
-> **Hallmark · v1.0.0**
->
-> - **Macrostructure** · Bento Grid
-> - **Theme** · Linen (cool slate paper · steel-blue accent · geometric sans)
-> - **Enrichment** · E1 Clipped-Edge Demo Video, Tier-A CSS-art trace waterfall
-> - **Sections** · Hero · 6-tile Bento (stat · sparkline · quote · code · integrations · spotlight) · Index Footer
-> - **Motion** · counter · pricing-lift · CSS marquee on integrations strip
-> - **Slop test** · 65 / 65 ✓
-> - **Diversification** · differs from Plain on paper hue (light-cool vs pure-white) + accent (indigo vs ink-blue)
-
-*Manifesto (declarative, no enrichment):*
-> **Hallmark · v1.0.0**
->
-> - **Macrostructure** · Manifesto
-> - **Theme** · Manifesto (dark · Inter Tight 900 · single red bleed)
-> - **Enrichment** · none (typography only — voice carries the brand)
-> - **Sections** · Masthead · Title · Five Declarations · Bleed Band · What We Refuse · Working Rules · Practice · Reading · Colophon
-> - **Motion** · none — typography only
-> - **Slop test** · 65 / 65 ✓
-> - **Diversification** · differs from Linen on paper band (dark vs light) + display style (display-heavy vs geometric-sans)
-
-*Custom (Coffeebox archival café):*
-> **Hallmark · v1.0.0**
->
-> - **Macrostructure** · Long Document
-> - **Theme** · custom (vibe: "archival warmth, hand-set, no varnish" · paper oklch(94% 0.020 65) · accent oklch(58% 0.16 35) terracotta · Fraunces italic display + Source Serif 4 body)
-> - **Enrichment** · Tier-A pure-CSS coffee bean (60-line SVG, breathing-loop optional)
-> - **Sections** · Masthead · Letter · Three Notes · Visit · Colophon
-> - **Motion** · breathing-loop on bean (with reduced-motion fallback)
-> - **Slop test** · 65 / 65 ✓
-> - **Diversification** · custom axes: light / italic-serif / chromatic-terracotta — differs from previous catalog Linen on accent hue + display style
+Four worked sample preview blocks (Long Document, Bento Grid, Manifesto, Custom) live in [`references/preview-examples.md`](references/preview-examples.md) — load that file only if the bullet-list spec above isn't scaffolding enough on its own. Most builds don't need it.
If any slop-test gate fails when you reach Step 7, return to the relevant Build step, fix it, and **re-emit the preview block** with the corrected slop-test row. The preview is the durable summary; it's wrong to ship if it lies.
@@ -494,7 +453,7 @@ Always:
### 7. The slop test
-Before handing back, run the output through the 65-gate slop test in [`references/slop-test.md`](references/slop-test.md). Every answer must be **no**. Load that file at this step (not earlier — it isn't needed until handoff). The active genre matters: some gates are universal, some are genre-scoped (atmospheric loosens the radial-bloom gate; modern-minimal loosens the zero-chroma neutral gate; etc.). The full per-genre overrides are listed inline in `slop-test.md`.
+Before handing back, run the output through the 66-gate slop test in [`references/slop-test.md`](references/slop-test.md). Every answer must be **no**. Load that file at this step (not earlier — it isn't needed until handoff). The active genre matters: some gates are universal, some are genre-scoped (atmospheric loosens the radial-bloom gate; modern-minimal loosens the zero-chroma neutral gate; etc.). The full per-genre overrides are listed inline in `slop-test.md`.
Run the slop test BEFORE writing the Slop test row in the Step 5 preview block — that row reflects the actual outcome of this step.
diff --git a/skill/references/component-cookbook.md b/skill/references/component-cookbook.md
index bbe2df5..c73b98f 100644
--- a/skill/references/component-cookbook.md
+++ b/skill/references/component-cookbook.md
@@ -8,6 +8,82 @@ The same macrostructure (e.g., Bento Grid) can be built from many different comb
---
+
+---
+
+## Archetype index — load ONLY the picks you need
+
+**Pick your archetype names here, then read ONLY those individual files** from `references/components/`. Do not load the whole cookbook. A typical build needs 5–7 files: 1 hero + 1 section head + 1–2 features + 1 CTA + 1 footer + 1 nav.
+
+### Heroes
+
+- **H1 · Marquee** — A single statement fills the fold. No subhead, no CTA in view. [`components/h1-marquee.md`](components/h1-marquee.md)
+- **H2 · Split diptych** — Headline + lede on one side, image or product capture on the other. 6/6 or 7/5 columns. [`components/h2-split-diptych.md`](components/h2-split-diptych.md)
+- **H3 · Quote led** — A pull-quote with attribution is the hero. Your headline is borrowed credibility. [`components/h3-quote-led.md`](components/h3-quote-led.md)
+- **H4 · Stat led** — A giant number or metric is the hero. A small qualifier line below. [`components/h4-stat-led.md`](components/h4-stat-led.md)
+- **H5 · Letter hero** — First-person opening — "Dear reader,". No buttons in fold. Reads as personal correspondence. [`components/h5-letter-hero.md`](components/h5-letter-hero.md)
+- **H6 · Photographic fold** — Single full-bleed image fills the viewport. Caption sits in a corner. [`components/h6-photographic-fold.md`](components/h6-photographic-fold.md)
+- **H7 · Demo video clipped by viewport edge** — Display headline left, demo video right, the rightmost ~10–20 % extending past the viewport so it's intentionally cut off. The clip *is* the design — implies "there's more product [`components/h7-demo-video-clipped-by-viewport-edge.md`](components/h7-demo-video-clipped-by-viewport-edge.md)
+- **H8 · Mockup split browser framed** — Headline left, browser-frame mockup right, the mockup tilted 1–3° for life. Frame can be browser chrome, macOS toolbar, minimal hairline, or floating no-frame. [`components/h8-mockup-split-browser-framed.md`](components/h8-mockup-split-browser-framed.md)
+- **H9 · Custom illustration centerpiece** — A single hand-built SVG (Tier B in the enrichment hierarchy — or pure CSS at Tier A for simpler shapes) sitting on the hero as one illustrative element. The bakery loaf, the studio [`components/h9-custom-illustration-centerpiece.md`](components/h9-custom-illustration-centerpiece.md)
+
+### Section heads
+
+- **S1 · Left margin numbered** — A narrow left column holds `01 — LABEL.`; the wide right column holds the heading and content. [`components/s1-left-margin-numbered.md`](components/s1-left-margin-numbered.md)
+- **S2 · Hanging** — Heading floats above the section in negative space; no border, no rule. [`components/s2-hanging.md`](components/s2-hanging.md)
+- **S3 · Sticky pinned** — Heading remains in viewport while content scrolls beneath. Orientation aid. [`components/s3-sticky-pinned.md`](components/s3-sticky-pinned.md)
+- **S4 · Inline no break** — The heading is a small caps phrase that emerges *inside* the body flow; no spatial break. [`components/s4-inline-no-break.md`](components/s4-inline-no-break.md)
+- **S5 · Bottom anchored** — The label or heading sits *below* the section's content. Inverts hierarchy. [`components/s5-bottom-anchored.md`](components/s5-bottom-anchored.md)
+
+### Feature blocks
+
+- **F1 · Bento grid** — Asymmetric grid of 8–15 tiles in mixed spans (1×1, 2×1, 1×2, 2×2). Visual rhythm via size. [`components/f1-bento-grid.md`](components/f1-bento-grid.md)
+- **F2 · Sticky scroll stack** — Sticky left pane, scrolling right pane that cycles through related screenshots. [`components/f2-sticky-scroll-stack.md`](components/f2-sticky-scroll-stack.md)
+- **F3 · Tabular spec sheet** — Each row is a feature; columns hold name, value, footnote. Hairline rules between rows. Tabular numerics. [`components/f3-tabular-spec-sheet.md`](components/f3-tabular-spec-sheet.md)
+- **F4 · Step sequence** — Numbered stages (`1.0 → 2.0 → 3.0`) flow vertically. Each stage has a heading, a paragraph, sometimes a small visual. [`components/f4-step-sequence.md`](components/f4-step-sequence.md)
+- **F5 · Annotated screenshot** — A product capture sits centre-stage with arrows or short labels pointing to UI details. [`components/f5-annotated-screenshot.md`](components/f5-annotated-screenshot.md)
+- **F6 · Product card grid** — Each card is a product, not a feature. Image · name · price · one micro-action. Reads like a shop floor, not a marketing site. [`components/f6-product-card-grid.md`](components/f6-product-card-grid.md)
+
+### CTAs / signups
+
+- **C1 · Outlined chip** — A bordered, transparent button with a typographic verb ("Save changes"). [`components/c1-outlined-chip.md`](components/c1-outlined-chip.md)
+- **C2 · Inline form as cta** — The CTA *is* the form — a single email input with a "Submit →" beside it. No separate landing for sign-up. [`components/c2-inline-form-as-cta.md`](components/c2-inline-form-as-cta.md)
+- **C3 · Typographic link** — Just a word, an arrow, and a 1-px underline. No box, no fill. [`components/c3-typographic-link.md`](components/c3-typographic-link.md)
+- **C4 · Sticky bottom bar** — A horizontal bar pinned to the viewport bottom, holding a CTA + a brief reassurance line. [`components/c4-sticky-bottom-bar.md`](components/c4-sticky-bottom-bar.md)
+
+### Testimonials / proof
+
+- **T1 · Pull quote with marginalia** — A quote sits in the wide column; the attribution and source link float in the narrow margin column. [`components/t1-pull-quote-with-marginalia.md`](components/t1-pull-quote-with-marginalia.md)
+- **T2 · Logo wall hairline** — A row of customer logos, monochromatic, separated by hairline rules. No card boxes, no shadows. [`components/t2-logo-wall-hairline.md`](components/t2-logo-wall-hairline.md)
+- **T3 · Single huge quote** — One quote, set big, centered, taking a whole section. No supporting text, no attribution boxes — attribution is a small caps line beneath. [`components/t3-single-huge-quote.md`](components/t3-single-huge-quote.md)
+- **T4 · Numbered stat strip** — A horizontal strip of 3–5 stats (count + qualifier) running across one row. Tabular nums. [`components/t4-numbered-stat-strip.md`](components/t4-numbered-stat-strip.md)
+
+### Footers
+
+- **Ft1 · Mast headed** — A wordmark and tagline anchor a single horizontal band. Two or three small links beside, address or licence below. [`components/ft1-mast-headed.md`](components/ft1-mast-headed.md)
+- **Ft2 · Inline rule single line** — A single horizontal line of credits, address, copyright. Hairline rule above. No columns. [`components/ft2-inline-rule-single-line.md`](components/ft2-inline-rule-single-line.md)
+- **Ft3 · Index style category list** — Three or four short columns, each headed by a category in small caps, holding 4–6 links each. [`components/ft3-index-style-category-list.md`](components/ft3-index-style-category-list.md)
+- **Ft4 · Dense typographic** — One large block of text — credits, references, licence, address — in a small monospace font, fully justified or ragged-right. Editorial colophon energy. [`components/ft4-dense-typographic.md`](components/ft4-dense-typographic.md)
+- **Ft5 · Statement** — One large display sentence dominates the footer — a closing line, not a sitemap. Wordmark, minimal links, copyright sit beneath in muted small type. Stripe (older), Mailchimp pre-r [`components/ft5-statement.md`](components/ft5-statement.md)
+- **Ft6 · Letter close** — Closes the page like a letter — `Yours, the team. 2026.` Optional postscript line beneath. Sets the page as a piece of writing rather than a product. [`components/ft6-letter-close.md`](components/ft6-letter-close.md)
+- **Ft7 · Newsletter first** — The form (label + input + submit) is the *primary* element of the footer; everything else (wordmark, links, copyright) is set in 12 px muted type beneath. Stratechery, Substack-sha [`components/ft7-newsletter-first.md`](components/ft7-newsletter-first.md)
+- **Ft8 · Marquee scroll** — A horizontal infinite-scroll line of repeating tagline + dot separator: `STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 ·`. Sport-genre sites, fashion lookbooks, brand-forward agenc [`components/ft8-marquee-scroll.md`](components/ft8-marquee-scroll.md)
+
+### Navigation
+
+- **N1 · Wordmark 2 links** — Top-of-page bar: wordmark on the left, two text links on the right ("Pricing" / "Sign in"). No logo image, no menu icon. [`components/n1-wordmark-2-links.md`](components/n1-wordmark-2-links.md)
+- **N2 · Floating chip** — A small fixed chip in a corner — wordmark + a single action ("Try it"). Doesn't sit in document flow. [`components/n2-floating-chip.md`](components/n2-floating-chip.md)
+- **N3 · Side rail** — A thin vertical strip on the left edge — wordmark rotated, plus 2–3 dot-indicators for sections. Editorial / portfolio energy. [`components/n3-side-rail.md`](components/n3-side-rail.md)
+- **N4 · Hidden behind k** — No visible nav. The user opens a command palette via `⌘K` to get anywhere. Designed for keyboard-first audiences. [`components/n4-hidden-behind-k.md`](components/n4-hidden-behind-k.md)
+- **N5 · Floating pill** — A rounded full-pill nav, *visibly detached* from the page edges, sitting ~`var(--space-md)` from the top, soft blur backdrop, soft shadow. Reads as contemporary modern-minimal — Ve [`components/n5-floating-pill.md`](components/n5-floating-pill.md)
+- **N6 · Newspaper masthead** — Full-width header, large centred wordmark on the top row, thin issue/date line above or below in serif small caps, optional inline link row beneath, double-rule below the whole thi [`components/n6-newspaper-masthead.md`](components/n6-newspaper-masthead.md)
+- **N7 · Brutal slab** — A heavy, full-width nav with a 2 px solid border-bottom, all-caps wordmark and tracked uppercase link row, dense rhythm, no shadow, no rounded corners. Reads as Pentagram project p [`components/n7-brutal-slab.md`](components/n7-brutal-slab.md)
+- **N8 · Terminal command** — A nav formatted as a CLI prompt: `> studio --catalog --voice --get▮`. The "links" are command flags. The blinking cursor (`▮`) is allowed *only here* (it has purpose — signals "you [`components/n8-terminal-command.md`](components/n8-terminal-command.md)
+- **N9 · Edge aligned minimal** — Wordmark hard-left, single CTA hard-right, vast empty space between, no link row at all. The *absence* is the design — Apple product pages, Carl Hauser, luxury sites. [`components/n9-edge-aligned-minimal.md`](components/n9-edge-aligned-minimal.md)
+- **N10 · Floating on scroll morph** — A sticky bar at the top that **morphs into a floating pill** as the user scrolls past a threshold. Two visual modes share one DOM — `.nav` (outer) owns the bar look, `.nav__inner` [`components/n10-floating-on-scroll-morph.md`](components/n10-floating-on-scroll-morph.md)
+
+---
+
## Within-archetype variation knobs
Picking an archetype is the first axis of variety. The second is *how you build it*. Two pages built with the same archetype should not be identical — each archetype below has 2–3 *variation knobs*. Pick one value per knob per output. This prevents "every Bento I build looks like the same Bento."
@@ -65,628 +141,6 @@ When you pick an archetype, **state the knob values you chose** in the macrostru
---
-## Heroes
-
-### H1 · Marquee
-A single statement fills the fold. No subhead, no CTA in view.
-*Use when:* the brand or person *is* the message.
-*Don't confuse with:* H4 Stat-Led (which is a number, not a statement).
-
-```html
-<section class="hero-marquee">
- <h1 class="display-xxl">A statement.</h1>
-</section>
-```
-```css
-.hero-marquee { min-height: 80dvh; display: grid; align-content: end; padding: 0 var(--page-gutter) var(--space-2xl); }
-.display-xxl { font-size: clamp(4rem, 12vw, 12rem); line-height: 0.92; }
-```
-
-### H2 · Split Diptych
-Headline + lede on one side, image or product capture on the other. 6/6 or 7/5 columns.
-*Use when:* you can pair every claim with a visual proof.
-*Don't confuse with:* H6 Photographic (which puts the image full-bleed, not paired).
-
-```html
-<section class="hero-split">
- <div><h1>…</h1><p>…</p><a class="cta-outline">…</a></div>
- <figure><img src="" /></figure>
-</section>
-```
-```css
-.hero-split { display: grid; grid-template-columns: 7fr 5fr; gap: var(--space-2xl); align-items: center; }
-@media (max-width: 56rem) { .hero-split { grid-template-columns: 1fr; } }
-```
-
-### H3 · Quote-Led
-A pull-quote with attribution is the hero. Your headline is borrowed credibility.
-*Use when:* you have a real testimonial that earns the front page.
-*Don't confuse with:* T3 Single huge quote (which lives mid-page, not in the hero slot).
-
-```html
-<section class="hero-quote">
- <blockquote class="display-italic">"…"</blockquote>
- <p class="attribution">— Name, Role, Company</p>
-</section>
-```
-
-### H4 · Stat-Led
-A giant number or metric is the hero. A small qualifier line below.
-*Use when:* you have one defensible, externally-verifiable number.
-*Don't confuse with:* T4 Numbered stat strip (which is several stats in a row, not one focal).
-
-```html
-<section class="hero-stat">
- <p class="figure tnum">99.97<span class="unit">%</span></p>
- <p class="qualifier">…</p>
-</section>
-```
-```css
-.figure { font-size: clamp(6rem, 18vw, 16rem); font-variant-numeric: tabular-nums; line-height: 0.85; }
-```
-
-### H5 · Letter Hero
-First-person opening — "Dear reader,". No buttons in fold. Reads as personal correspondence.
-*Use when:* the founder's voice is the brand.
-*Don't confuse with:* H1 Marquee (which is impersonal declaration).
-
-```html
-<section class="hero-letter">
- <p class="salutation"><em>Dear reader,</em></p>
- <p class="lede">…</p>
-</section>
-```
-
-### H6 · Photographic Fold
-Single full-bleed image fills the viewport. Caption sits in a corner.
-*Use when:* you have real photography that earns full-bleed.
-*Don't confuse with:* H2 Split (which pairs image with text in a grid).
-
-```html
-<section class="hero-photo">
- <img class="bleed" src="" alt="" />
- <p class="caption">Spring, 2026.</p>
-</section>
-```
-```css
-.hero-photo { position: relative; height: 80dvh; }
-.hero-photo .bleed { width: 100%; height: 100%; object-fit: cover; }
-.hero-photo .caption { position: absolute; bottom: var(--space-md); right: var(--space-md); }
-```
-
-### H7 · Demo Video — Clipped-by-viewport-edge
-Display headline left, demo video right, the rightmost ~10–20 % extending past the viewport so it's intentionally cut off. The clip *is* the design — implies "there's more product than fits the screen". Pioneered by Linear, refined by Vercel / Resend / Cursor.
-*Use when:* the brief is SaaS / dev-tool / dashboard / platform AND you have real footage of the product (or a hand-built CSS-art mockup of it).
-*Don't confuse with:* H4 Stat-Led (number-led, no video) or H8 Mockup Split (still screenshot, not video).
-
-See [`hero-enrichment.md`](hero-enrichment.md) for the full E1 recipe (codec chain, autoplay rules, `prefers-reduced-motion` fallback, mobile collapse). The cookbook entry below is the structural sketch.
-
-```html
-<section class="hero hero--clipped">
- <div class="hero__copy">
- <h1>Plan, build, ship.</h1>
- <p>The project tracker your engineering team won't ignore.</p>
- </div>
- <figure class="hero__media">
- <video autoplay muted loop playsinline preload="metadata"
- poster="/hero-poster.webp" fetchpriority="high">
- <source src="/hero.av1.mp4" type='video/mp4; codecs="av01.0.05M.08"'>
- <source src="/hero.h264.mp4" type="video/mp4">
- </video>
- </figure>
-</section>
-```
-```css
-.hero--clipped { display: grid; grid-template-columns: 1fr 1.4fr; gap: var(--space-2xl); overflow: visible; }
-.hero__media { width: calc(100% + 12vw); aspect-ratio: 16 / 10; border-radius: 12px; overflow: hidden; }
-@media (max-width: 60rem) { .hero--clipped { grid-template-columns: 1fr; } .hero__media { width: 100%; } }
-```
-
-### H8 · Mockup Split (browser-framed)
-Headline left, browser-frame mockup right, the mockup tilted 1–3° for life. Frame can be browser chrome, macOS toolbar, minimal hairline, or floating no-frame.
-*Use when:* you're selling a web app and you have a clean, well-lit screenshot.
-*Don't confuse with:* H7 Clipped-Edge (which extends past the viewport) or H2 Split Diptych (which uses photography or proof column, not a product mockup).
-
-```html
-<section class="hero-mock">
- <div>
- <h1>The studio's new mute button.</h1>
- <p>Press <kbd>⌘ M</kbd> from anywhere.</p>
- </div>
- <figure class="mock">
- <header class="mock__chrome"><span></span><span></span><span></span></header>
- <div class="mock__body"><!-- screenshot or CSS-art mockup --></div>
- </figure>
-</section>
-```
-```css
-.hero-mock { display: grid; grid-template-columns: 1fr 1.2fr; gap: var(--space-2xl); align-items: center; }
-.mock { transform: rotate(1.5deg); border-radius: 12px; overflow: hidden; box-shadow: 0 24px 60px -20px oklch(20% 0.02 60 / 0.18); }
-.mock__chrome { display: flex; gap: 6px; padding: 10px 12px; background: var(--color-paper-2); border-block-end: var(--rule-hair) solid var(--color-rule); }
-.mock__chrome span { width: 10px; height: 10px; border-radius: 50%; background: var(--color-rule-2); }
-```
-
-### H9 · Custom Illustration Centerpiece
-A single hand-built SVG (Tier B in the enrichment hierarchy — or pure CSS at Tier A for simpler shapes) sitting on the hero as one illustrative element. The bakery loaf, the studio's mascot, the workflow diagram.
-*Use when:* the brand has a *thing* that benefits from being drawn — a craft, a character, a process.
-*Don't confuse with:* H6 Photographic (real photography) or H8 Mockup (a product screenshot, not artwork).
-
-The illustration itself is *built*, not picked from Storyset / Humaaans / unDraw / Lottie. See [`custom-craft.md`](custom-craft.md) for full recipes (CSS art, hand-built SVG, declarative animation). The cookbook entry below is the page-level structural sketch.
-
-```html
-<section class="hero-art">
- <div>
- <p class="eyebrow">Maple Street Bread · est. 2026</p>
- <h1>Sourdough, every morning.</h1>
- <p>Slow-fermented overnight, baked on stone, before you wake.</p>
- </div>
- <svg viewBox="0 0 200 100" class="loaf" aria-label="A loaf of bread">
- <path class="loaf__body" d="M 20 70 Q 100 10 180 70 L 180 90 L 20 90 Z" />
- <path class="loaf__score" d="M 60 50 L 90 30 M 100 45 L 130 25 M 140 50 L 165 35" />
- </svg>
-</section>
-```
-```css
-.hero-art { display: grid; grid-template-columns: 1fr 1fr; gap: var(--space-2xl); align-items: center; }
-.loaf__body { fill: oklch(72% 0.14 50); }
-.loaf__score{ stroke: oklch(38% 0.10 35); stroke-width: 2; fill: none; stroke-linecap: round; }
-```
-
----
-
-## Section heads
-
-### S1 · Left-margin numbered
-A narrow left column holds `01 — LABEL.`; the wide right column holds the heading and content.
-*Use when:* the page is editorial / specimen.
-*Don't confuse with:* S5 Bottom-anchored (which puts the label *under* the section).
-
-```html
-<header class="head-margin">
- <p class="num-label">01 — Foundations</p>
- <h2>…</h2>
-</header>
-```
-```css
-.head-margin { display: grid; grid-template-columns: 10rem 1fr; gap: var(--space-xl); align-items: baseline; }
-```
-
-### S2 · Hanging
-Heading floats above the section in negative space; no border, no rule.
-*Use when:* the content has a quiet, room-to-breathe energy.
-*Don't confuse with:* S3 Sticky-pinned (which moves with scroll).
-
-```html
-<header class="head-hang">
- <h2>…</h2>
-</header>
-```
-```css
-.head-hang { padding-block: var(--space-3xl) var(--space-xl); }
-```
-
-### S3 · Sticky pinned
-Heading remains in viewport while content scrolls beneath. Orientation aid.
-*Use when:* the section is dense and the user benefits from always seeing where they are.
-*Don't confuse with:* S1 Left-margin (which doesn't move).
-
-```html
-<header class="head-sticky">
- <p class="num-label">02</p>
- <h2>…</h2>
-</header>
-```
-```css
-.head-sticky { position: sticky; top: 0; background: var(--color-paper); padding-block: var(--space-sm); border-bottom: 1px solid var(--color-ink); z-index: 10; }
-```
-
-### S4 · Inline (no break)
-The heading is a small caps phrase that emerges *inside* the body flow; no spatial break.
-*Use when:* the page is prose-led; reading should be continuous.
-*Don't confuse with:* S2 Hanging (which separates with negative space).
-
-```html
-<p>… <span class="head-inline">A small heading.</span> …</p>
-```
-```css
-.head-inline { font-variant-caps: all-small-caps; letter-spacing: 0.06em; font-weight: 500; }
-```
-
-### S5 · Bottom-anchored
-The label or heading sits *below* the section's content. Inverts hierarchy.
-*Use when:* the content is the primary act and the label is a footer to it.
-*Don't confuse with:* S1 Left-margin (which leads with the label).
-
-```html
-<section>
- <div class="content">…</div>
- <p class="num-label">— end of 02</p>
-</section>
-```
-
----
-
-## Feature blocks
-
-### F1 · Bento grid
-Asymmetric grid of 8–15 tiles in mixed spans (1×1, 2×1, 1×2, 2×2). Visual rhythm via size.
-*Use when:* multiple equally-valid entry points; SaaS feature page.
-*Don't confuse with:* F2 Sticky-scroll (which stacks vertically with sticky pacing).
-
-```html
-<section class="bento">
- <article class="cell span-2x2">…</article>
- <article class="cell span-1x1">…</article>
- <article class="cell span-2x1">…</article>
-</section>
-```
-```css
-.bento { display: grid; grid-template-columns: repeat(4, 1fr); grid-auto-rows: 12rem; gap: var(--space-md); }
-.span-2x2 { grid-column: span 2; grid-row: span 2; }
-.span-2x1 { grid-column: span 2; }
-.span-1x2 { grid-row: span 2; }
-@media (max-width: 56rem) { .bento { grid-template-columns: repeat(2, 1fr); } }
-```
-
-### F2 · Sticky-scroll stack
-Sticky left pane, scrolling right pane that cycles through related screenshots.
-*Use when:* feature has multiple sub-states worth showing in sequence.
-*Don't confuse with:* F4 Step sequence (which is linearly numbered, not synced).
-
-```html
-<section class="sticky-stack">
- <div class="pane-sticky"><h3>…</h3><p>…</p></div>
- <div class="pane-scroll">
- <figure>1</figure><figure>2</figure><figure>3</figure>
- </div>
-</section>
-```
-```css
-.sticky-stack { display: grid; grid-template-columns: 1fr 1fr; gap: var(--space-2xl); }
-.pane-sticky { position: sticky; top: var(--space-xl); align-self: start; }
-```
-
-### F3 · Tabular spec sheet
-Each row is a feature; columns hold name, value, footnote. Hairline rules between rows. Tabular numerics.
-*Use when:* features compare quantitatively.
-*Don't confuse with:* F1 Bento (which is non-tabular and visually rhythmic).
-
-```html
-<table class="spec-sheet tnum">
- <tr><th>Latency</th><td>p99 &lt; 50 ms</td><td class="muted">measured externally</td></tr>
- <tr>…</tr>
-</table>
-```
-
-### F4 · Step sequence
-Numbered stages (`1.0 → 2.0 → 3.0`) flow vertically. Each stage has a heading, a paragraph, sometimes a small visual.
-*Use when:* the product is a workflow, not a single moment.
-*Don't confuse with:* F2 Sticky-scroll (which doesn't number stages).
-
-```html
-<ol class="steps">
- <li><span class="stage">1.0</span><h3>Intake.</h3><p>…</p></li>
- <li><span class="stage">2.0</span><h3>Plan.</h3><p>…</p></li>
-</ol>
-```
-
-### F5 · Annotated screenshot
-A product capture sits centre-stage with arrows or short labels pointing to UI details.
-*Use when:* the product UI itself is the explanation.
-*Don't confuse with:* F2 Sticky-scroll (which uses multiple screenshots in sequence).
-
-```html
-<figure class="annotated">
- <img src="" />
- <span class="callout" style="--x:60%; --y:30%;">→ assigns automatically.</span>
-</figure>
-```
-
-### F6 · Product card grid
-Each card is a product, not a feature. Image · name · price · one micro-action. Reads like a shop floor, not a marketing site.
-*Use when:* the brief is commerce, catalogue, lookbook, marketplace — anything where the page sells *things*, not *features*.
-*Don't confuse with:* F1 Bento (which sells *features*; tiles vary in size and span). Product cards are uniform on purpose — the rhythm comes from the products, not the layout.
-
-**Variation knobs:** card ratio (3/4 portrait · 1/1 square · 4/3 landscape) · density (3-up · 4-up · 5-up) · price treatment (under name · over image · hover-reveal) · micro-action (Add · Save · View → · none).
-
-```html
-<section class="product-grid">
- <article class="product">
- <a class="product__media" href=""><img src="" alt="" loading="lazy" /></a>
- <div class="product__meta">
- <h3 class="product__name">Linen Apron · Indigo</h3>
- <p class="product__price tabular-nums">¥ 6,400</p>
- </div>
- <button class="product__add" aria-label="Add Linen Apron to bag">+</button>
- </article>
- <!-- ... more products, uniform shape ... -->
-</section>
-```
-```css
-.product-grid { display: grid; grid-template-columns: repeat(3, 1fr); gap: var(--space-xl) var(--space-lg); }
-@media (max-width: 60rem) { .product-grid { grid-template-columns: repeat(2, 1fr); } }
-.product { display: grid; gap: var(--space-sm); position: relative; }
-.product__media { display: block; aspect-ratio: 3 / 4; background: var(--color-paper-2); overflow: hidden; }
-.product__media img { width: 100%; height: 100%; object-fit: cover; transition: transform var(--dur-long) var(--ease-out); }
-.product__media:hover img { transform: scale(1.02); }
-.product__name { font-family: var(--font-body); font-size: var(--text-md); margin: 0; }
-.product__price { font-family: var(--font-mono); font-size: var(--text-sm); color: var(--color-ink-2); }
-.product__add { position: absolute; top: var(--space-sm); right: var(--space-sm); width: 32px; height: 32px; background: var(--color-paper); border: var(--rule-hair) solid var(--color-rule-2); cursor: pointer; opacity: 0; transition: opacity var(--dur-short) var(--ease-out); }
-.product:hover .product__add, .product:focus-within .product__add { opacity: 1; }
-@media (pointer: coarse) { .product__add { opacity: 1; } }
-```
-
-**Anti-patterns to avoid in product grids:**
-- Don't borrow Bento's irregular spans — products want uniform rhythm.
-- Don't put feature-style two-line descriptions under product names. The price *is* the description.
-- Don't auto-scale the image on idle — only on hover, and only by 1.02× max.
-- Don't use cards with shadow + radius + border + tile + ribbon. Pick one container signal.
-
----
-
-## CTAs / signups
-
-### C1 · Outlined chip
-A bordered, transparent button with a typographic verb ("Save changes").
-*Use when:* the page has one primary action; you want it visible but quiet.
-*Don't confuse with:* C2 Oversized solid (which is statement-loud).
-
-```html
-<a class="cta-outline">Open your studio →</a>
-```
-```css
-.cta-outline { display: inline-flex; align-items: center; gap: 0.4em; padding: 0.7rem 1.2rem; border: 1px solid var(--color-ink); min-height: 44px; }
-```
-
-### C2 · Inline form-as-CTA
-The CTA *is* the form — a single email input with a "Submit →" beside it. No separate landing for sign-up.
-*Use when:* the action is collecting an email.
-*Don't confuse with:* C1 Outlined chip (which navigates, not submits).
-
-```html
-<form class="cta-form">
- <label for="email" class="visually-hidden">Email</label>
- <input id="email" type="email" placeholder="[email protected]" />
- <button type="submit">Send →</button>
-</form>
-```
-```css
-.cta-form { display: grid; grid-template-columns: 1fr auto; border-bottom: 1px solid var(--color-ink); }
-.cta-form input { background: none; border: 0; padding: 0.7rem 0; min-height: 44px; }
-```
-
-### C3 · Typographic link
-Just a word, an arrow, and a 1-px underline. No box, no fill.
-*Use when:* the page is editorial / Long Document; CTAs should not shout.
-*Don't confuse with:* C1 Outlined chip (which is bordered).
-
-```html
-<a class="link">Read the case study →</a>
-```
-
-### C4 · Sticky bottom bar
-A horizontal bar pinned to the viewport bottom, holding a CTA + a brief reassurance line.
-*Use when:* the page is long and the CTA needs to be reachable always.
-*Don't confuse with:* anything in the fold; this is a *persistent* element, not a hero CTA.
-
-```html
-<aside class="cta-sticky">
- <span>Try it free for 14 days.</span>
- <a class="cta-outline">Start →</a>
-</aside>
-```
-```css
-.cta-sticky { position: fixed; left: 0; right: 0; bottom: 0; padding: var(--space-sm) var(--space-md); background: var(--color-paper); border-top: 1px solid var(--color-rule); display: flex; justify-content: space-between; align-items: center; }
-```
-
----
-
-## Testimonials / proof
-
-### T1 · Pull-quote with marginalia
-A quote sits in the wide column; the attribution and source link float in the narrow margin column.
-*Use when:* the page already has a marginalia rhythm (Tufte-leaning, editorial).
-*Don't confuse with:* T3 Single huge quote (which is centered and dominates).
-
-```html
-<aside class="proof-margin">
- <blockquote class="serif-italic">"…"</blockquote>
- <p class="attribution muted">— Name<br />Role, Company</p>
-</aside>
-```
-
-### T2 · Logo wall (hairline)
-A row of customer logos, monochromatic, separated by hairline rules. No card boxes, no shadows.
-*Use when:* you have recognisable customers and want to surface them quietly.
-*Don't confuse with:* the AI-default 6-logo box grid; this version refuses card boxes.
-
-```html
-<section class="logo-wall">
- <ul>
- <li><img src="" /></li>
- <li><img src="" /></li>
- <li><img src="" /></li>
- </ul>
-</section>
-```
-```css
-.logo-wall ul { display: grid; grid-template-columns: repeat(auto-fit, minmax(8rem, 1fr)); gap: 0; }
-.logo-wall li { padding: var(--space-md); border-right: 1px solid var(--color-rule); display: grid; place-items: center; }
-.logo-wall img { filter: grayscale(1); opacity: 0.7; }
-```
-
-### T3 · Single huge quote
-One quote, set big, centered, taking a whole section. No supporting text, no attribution boxes — attribution is a small caps line beneath.
-*Use when:* one quote is so good it earns the room.
-*Don't confuse with:* T1 Margin pull-quote (which is the *side* mate, not the *room*).
-
-```html
-<section class="proof-room">
- <blockquote class="display-italic">"…"</blockquote>
- <p class="attribution"><span class="caps">— Name, Company</span></p>
-</section>
-```
-
-### T4 · Numbered stat strip
-A horizontal strip of 3–5 stats (count + qualifier) running across one row. Tabular nums.
-*Use when:* you have multiple complementary metrics that work together.
-*Don't confuse with:* H4 Stat-led hero (which is one focal number, not several).
-
-```html
-<section class="stat-strip tnum">
- <div><b>2.4M</b><span>users</span></div>
- <div><b>99.97%</b><span>uptime</span></div>
- <div><b>14</b><span>regions</span></div>
-</section>
-```
-
----
-
-## Footers
-
-### Ft1 · Mast-headed
-A wordmark and tagline anchor a single horizontal band. Two or three small links beside, address or licence below.
-*Use when:* the page has heavy content; the footer should be quiet and singular.
-*Don't confuse with:* Ft2 Inline-rule (which is even more reduced).
-
-```html
-<footer class="foot-mast">
- <p class="wordmark">Studio Name</p>
- <p class="tagline muted">Designs that don't look generated.</p>
- <p class="links muted">Imprint · Privacy · Contact</p>
-</footer>
-```
-
-### Ft2 · Inline-rule single line
-A single horizontal line of credits, address, copyright. Hairline rule above. No columns.
-*Use when:* the page is editorial and the footer is afterthought.
-*Don't confuse with:* Ft4 Dense typographic (which packs more in).
-
-```html
-<footer class="foot-line">
- <p>© 2026 · 137 Marlow Street · MIT licensed</p>
-</footer>
-```
-
-### Ft3 · Index-style category list
-Three or four short columns, each headed by a category in small caps, holding 4–6 links each.
-*Use when:* the page is a hub or a documentation root.
-*Don't confuse with:* Ft4 Dense typographic (which is one big block, not columns).
-
-```html
-<footer class="foot-index">
- <div><p class="caps">Product</p><ul>…</ul></div>
- <div><p class="caps">Company</p><ul>…</ul></div>
- <div><p class="caps">Resources</p><ul>…</ul></div>
-</footer>
-```
-
-### Ft4 · Dense typographic
-One large block of text — credits, references, licence, address — in a small monospace font, fully justified or ragged-right. Editorial colophon energy.
-*Use when:* the brand is editorial and a colophon-style sign-off fits.
-*Don't confuse with:* Ft3 Index (which navigates).
-
-```html
-<footer class="foot-dense mono">
- <p>Hallmark v0.2.0. Built with The Future, Fraunces, IBM Plex Mono. MIT licensed. Powered by Together AI. 137 Marlow Street, 2026.</p>
-</footer>
-```
-
-### Ft5 · Statement
-One large display sentence dominates the footer — a closing line, not a sitemap. Wordmark, minimal links, copyright sit beneath in muted small type. Stripe (older), Mailchimp pre-rebrand, agency portfolio closers.
-*Use when:* the page wants a *closing line* — editorial, manifesto, atmospheric. The sentence pairs with the page's argument.
-*Don't confuse with:* Ft1 Mast-headed (which leads with the wordmark, not a sentence).
-
-```html
-<footer class="foot-stmt">
- <p class="foot-stmt__line">Build something they'll remember.</p>
- <div class="foot-stmt__meta">
- <span class="wordmark">Studio</span>
- <span class="muted">© 2026 · MIT</span>
- </div>
-</footer>
-```
-```css
-.foot-stmt { padding: var(--space-2xl) var(--page-gutter) var(--space-xl); display: grid; gap: var(--space-lg); }
-.foot-stmt__line { font-family: var(--font-display); font-size: clamp(1.75rem, 5vw, 3.25rem); line-height: 1.0; letter-spacing: -0.02em; max-width: 28ch; margin: 0; }
-.foot-stmt__meta { display: flex; justify-content: space-between; align-items: baseline; padding-block-start: var(--space-sm); border-top: var(--rule-hair) solid var(--color-rule); }
-```
-
-*Anti-pattern:* using a Statement footer on a docs root or hub. The sentence reads as marketing fluff there; default Ft3 instead.
-
-### Ft6 · Letter close
-Closes the page like a letter — `Yours, the team. 2026.` Optional postscript line beneath. Sets the page as a piece of writing rather than a product.
-*Use when:* the page voice is warm, hand-written, editorial-quiet — Garden, Atelier, Salon, personal sites.
-*Don't confuse with:* Ft1 Mast-headed (which is a wordmark anchor, not a signoff).
-
-```html
-<footer class="foot-letter">
- <p class="foot-letter__close">Yours,<br><span class="foot-letter__sign">— Studio</span></p>
- <p class="foot-letter__ps muted">P.S. — letters back welcome at <a href="mailto:hello@studio">hello@studio</a>.</p>
-</footer>
-```
-```css
-.foot-letter { padding: var(--space-2xl) var(--page-gutter); max-width: 60ch; }
-.foot-letter__close { font-family: var(--font-display); font-style: italic; font-size: var(--text-lg); line-height: 1.4; }
-.foot-letter__sign { font-style: normal; font-weight: 600; }
-.foot-letter__ps { font-size: var(--text-sm); margin-top: var(--space-md); }
-```
-
-*Anti-pattern:* using Ft6 on a stat-led / B2B product page — voice mismatch reads as twee. Reserve for genuinely letter-shaped pages.
-
-### Ft7 · Newsletter-first
-The form (label + input + submit) is the *primary* element of the footer; everything else (wordmark, links, copyright) is set in 12 px muted type beneath. Stratechery, Substack-shaped sites, indie magazines.
-*Use when:* the brand legitimately publishes — and the page above the fold has *already* offered a subscription. The footer is a final invitation, not an ambush.
-*Don't confuse with:* Ft1 (which doesn't ask for anything).
-
-```html
-<footer class="foot-news">
- <form class="foot-news__form" action="/subscribe" method="post">
- <label for="foot-email">Letters from the studio · monthly</label>
- <div class="foot-news__row">
- <input id="foot-email" name="email" type="email" required placeholder="you@domain">
- <button type="submit" class="cta-fill">Subscribe</button>
- </div>
- </form>
- <p class="foot-news__meta muted">Studio · © 2026 · <a href="/imprint">Imprint</a></p>
-</footer>
-```
-```css
-.foot-news { padding: var(--space-2xl) var(--page-gutter); display: grid; gap: var(--space-lg); max-width: 56ch; }
-.foot-news__form label { display: block; font-size: var(--text-sm); margin-block-end: var(--space-2xs); }
-.foot-news__row { display: flex; gap: var(--space-2xs); }
-.foot-news__row input { flex: 1; min-height: 44px; padding-inline: var(--space-sm); border: var(--rule-hair) solid var(--color-rule); border-radius: var(--radius-input); background: var(--color-paper); }
-.foot-news__row input:focus-visible { outline: 2px solid var(--color-focus); outline-offset: 1px; }
-.foot-news__meta { font-size: var(--text-xs); }
-```
-
-*Anti-pattern:* Ft7 when the page never said "subscribe" above the fold. The footer is an honest *conclusion*; if you didn't ask, don't ambush. Drop to Ft2 instead.
-
-### Ft8 · Marquee scroll
-A horizontal infinite-scroll line of repeating tagline + dot separator: `STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 ·`. Sport-genre sites, fashion lookbooks, brand-forward agencies.
-*Use when:* the brand voice is loud, kinetic, sport-or-manifesto.
-*Don't confuse with:* Ft4 Dense colophon (which is static text).
-
-```html
-<footer class="foot-marquee" aria-label="Footer">
- <div class="foot-marquee__track" aria-hidden="true">
- <span>STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 ·</span>
- <span>STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 ·</span>
- </div>
- <p class="visually-hidden">Studio · 2026 · MIT licensed</p>
-</footer>
-```
-```css
-.foot-marquee { overflow: hidden; border-top: 2px solid var(--color-ink); }
-.foot-marquee__track { display: flex; gap: var(--space-2xl); white-space: nowrap; padding-block: var(--space-md); animation: foot-marquee 32s linear infinite; }
-.foot-marquee__track span { font-family: var(--font-display); font-weight: 700; letter-spacing: 0.08em; font-size: clamp(1rem, 2.5vw, 1.5rem); }
-@keyframes foot-marquee { from { transform: translateX(0); } to { transform: translateX(-50%); } }
-@media (prefers-reduced-motion: reduce) { .foot-marquee__track { animation: none; } }
-```
-
-*Anti-pattern:* using Ft8 on editorial / quiet contexts — the motion reads as loud. Pair only with playful / sport / manifesto voices, and always honour `prefers-reduced-motion: reduce`.
-
----
## Routing — which footer fits which genre
@@ -705,196 +159,6 @@ A horizontal infinite-scroll line of repeating tagline + dot separator: `STUDIO
---
-## Navigation
-
-### N1 · Wordmark + 2 links
-Top-of-page bar: wordmark on the left, two text links on the right ("Pricing" / "Sign in"). No logo image, no menu icon.
-*Use when:* the page has very few destinations.
-*Don't confuse with:* N3 Side-rail (which is vertical).
-
-```html
-<nav class="nav-min">
- <a class="wordmark">Studio</a>
- <ul><li><a>Pricing</a></li><li><a>Sign in</a></li></ul>
-</nav>
-```
-
-### N2 · Floating chip
-A small fixed chip in a corner — wordmark + a single action ("Try it"). Doesn't sit in document flow.
-*Use when:* the page is fold-heavy and traditional nav would fight the content.
-*Don't confuse with:* C4 Sticky bottom bar (which is full-width).
-
-```html
-<aside class="nav-chip">
- <a class="wordmark">Studio</a>
- <a class="cta-outline">Try →</a>
-</aside>
-```
-```css
-.nav-chip { position: fixed; top: var(--space-md); right: var(--space-md); display: inline-flex; gap: var(--space-md); padding: 0.5rem 0.75rem; background: var(--color-paper); border: 1px solid var(--color-rule); }
-```
-
-### N3 · Side-rail
-A thin vertical strip on the left edge — wordmark rotated, plus 2–3 dot-indicators for sections. Editorial / portfolio energy.
-*Use when:* the page is long and section-numbered.
-*Don't confuse with:* N1 Top wordmark (which is horizontal).
-
-```html
-<nav class="nav-rail">
- <p class="wordmark vertical">Studio</p>
- <ul class="dots"><li></li><li></li><li></li></ul>
-</nav>
-```
-```css
-.nav-rail { position: fixed; left: 0; top: 0; bottom: 0; width: 3rem; padding: var(--space-md); writing-mode: vertical-rl; }
-```
-
-### N4 · Hidden behind ⌘K
-No visible nav. The user opens a command palette via `⌘K` to get anywhere. Designed for keyboard-first audiences.
-*Use when:* the page is for technical users who expect this affordance.
-*Don't confuse with:* N2 Floating chip (which is visible always).
-
-```html
-<button class="kbd-hint">⌘ K</button>
-<dialog class="palette">…</dialog>
-```
-
-### N5 · Floating pill
-A rounded full-pill nav, *visibly detached* from the page edges, sitting ~`var(--space-md)` from the top, soft blur backdrop, soft shadow. Reads as contemporary modern-minimal — Vercel, Linear, Framer, Raycast.
-*Use when:* the page is modern-minimal / atmospheric and the hero has a distinct surface or imagery beneath the pill that the blur can sit over.
-*Don't confuse with:* N1 Wordmark + 2 links (which is full-width); N2 Floating chip (which is corner-anchored).
-
-```html
-<nav class="nav-pill" aria-label="Primary">
- <a class="wordmark">Studio</a>
- <ul class="nav-pill__links"><li><a>Catalog</a></li><li><a>Voice</a></li></ul>
- <a class="cta-fill">Get →</a>
-</nav>
-```
-```css
-.nav-pill {
- position: fixed; inset: var(--space-md) auto auto 50%;
- transform: translateX(-50%);
- display: inline-flex; align-items: center; gap: var(--space-md);
- padding: 0.5rem 0.875rem;
- background: color-mix(in oklch, var(--color-paper) 78%, transparent);
- backdrop-filter: blur(14px) saturate(120%);
- border: var(--rule-hair) solid var(--color-rule);
- border-radius: 999px;
- box-shadow: 0 8px 24px -12px oklch(0% 0 0 / 0.18);
- z-index: 20;
-}
-```
-
-*Anti-pattern:* a "pill" that's ~95 % viewport-wide is just a full-width nav with rounded ends — defeats the point. The pill must be visibly detached and content-sized; if your link list pushes it past ~720 px, drop a link or switch to N1.
-
-### N6 · Newspaper masthead
-Full-width header, large centred wordmark on the top row, thin issue/date line above or below in serif small caps, optional inline link row beneath, double-rule below the whole thing. Reads as editorial, broadsheet — NYT, FT, Vogue.
-*Use when:* the page is editorial, magazine-shaped, or framed as an issue / edition.
-*Don't confuse with:* N1 Wordmark + 2 links (which is asymmetric and small).
-
-```html
-<header class="nav-mast">
- <p class="mast-line muted">No 22 · Spring 2026 · Studio</p>
- <h1 class="mast-name">STUDIO</h1>
- <nav class="mast-nav" aria-label="Primary">
- <ul><li><a>Catalog</a></li><li><a>Voice</a></li><li><a>Letters</a></li></ul>
- </nav>
- <hr class="mast-rule double" aria-hidden="true">
-</header>
-```
-```css
-.nav-mast { display: grid; gap: var(--space-2xs); padding: var(--space-md) var(--page-gutter) 0; text-align: center; }
-.mast-name { font-family: var(--font-display); font-size: clamp(2.25rem, 5vw, 3.75rem); letter-spacing: -0.01em; line-height: 0.95; margin: 0; }
-.mast-line { font-variant: small-caps; letter-spacing: 0.08em; font-size: var(--text-xs); }
-.mast-nav ul { display: inline-flex; gap: var(--space-md); list-style: none; padding: 0; margin: var(--space-2xs) 0 0; }
-.mast-rule.double { border: 0; border-top: var(--rule-hair) solid var(--color-rule); border-bottom: var(--rule-hair) solid var(--color-rule); height: 4px; margin: var(--space-sm) 0 0; }
-```
-
-*Anti-pattern:* using N6 on a SaaS dashboard or a developer-tool product page. The masthead vocabulary belongs to long-form / editorial sites; on a B2B product, it reads as costume.
-
-### N7 · Brutal slab
-A heavy, full-width nav with a 2 px solid border-bottom, all-caps wordmark and tracked uppercase link row, dense rhythm, no shadow, no rounded corners. Reads as Pentagram project pages, Liquid Death, brutalist-leaning agencies.
-*Use when:* the genre is playful (Brutal, Manifesto, Sport) or the brand voice is heavy / declarative.
-*Don't confuse with:* N1 Wordmark + 2 links (which is small and quiet).
-
-```html
-<header class="nav-slab">
- <a class="slab-mark">STUDIO</a>
- <nav class="slab-nav" aria-label="Primary">
- <ul><li><a>CATALOG</a></li><li><a>VOICE</a></li><li><a>WORK</a></li></ul>
- </nav>
- <a class="cta-fill cta-fill--slab">GET</a>
-</header>
-```
-```css
-.nav-slab { display: flex; align-items: center; gap: var(--space-md); padding: var(--space-sm) var(--page-gutter); border-bottom: 2px solid var(--color-ink); background: var(--color-paper); }
-.slab-mark { font-family: var(--font-display); font-weight: 800; letter-spacing: 0.04em; }
-.slab-nav ul { display: flex; gap: var(--space-md); list-style: none; padding: 0; margin: 0 0 0 auto; }
-.slab-nav a { text-transform: uppercase; letter-spacing: 0.08em; font-size: var(--text-sm); font-weight: 600; }
-```
-
-*Anti-pattern:* combining N7 with rounded corners, soft shadows, or backdrop-blur — those vocabularies fight. If you reach for blur, drop to N5; if you reach for round, drop to N1.
-
-### N8 · Terminal command
-A nav formatted as a CLI prompt: `> studio --catalog --voice --get▮`. The "links" are command flags. The blinking cursor (`▮`) is allowed *only here* (it has purpose — signals "you'd type next"); never standalone elsewhere on the page. Reads as Vercel CLI docs landing, Charm, Mitchell Hashimoto's site.
-*Use when:* the page is a CLI tool, dev-tool docs, or carries the Terminal theme.
-*Don't confuse with:* N4 ⌘K-only (which is a palette, not a visible bar).
-
-```html
-<header class="nav-term">
- <pre class="nav-term__line"><span class="prompt">&gt;</span> studio <a href="#catalog">--catalog</a> <a href="#voice">--voice</a> <a href="#get">--get</a><span class="caret" aria-hidden="true">▮</span></pre>
-</header>
-```
-```css
-.nav-term { padding: var(--space-sm) var(--page-gutter); border-bottom: var(--rule-hair) solid var(--color-rule); }
-.nav-term__line { font-family: var(--font-outlier, ui-monospace, "JetBrains Mono", monospace); font-size: var(--text-sm); margin: 0; }
-.nav-term__line .prompt { color: var(--color-accent); padding-right: 0.4ch; }
-.nav-term__line a { color: var(--color-ink); text-decoration: underline; text-underline-offset: 2px; }
-.caret { display: inline-block; width: 1ch; animation: blink 1.05s steps(2) infinite; color: var(--color-accent); }
-@keyframes blink { 50% { opacity: 0; } }
-@media (prefers-reduced-motion: reduce) { .caret { animation: none; opacity: 1; } }
-```
-
-*Anti-pattern:* using `>` prompt vocabulary on a non-developer site (a wedding photographer's portfolio with a `> view --gallery` nav reads as set decoration). N8 belongs to genuine terminal / CLI brands only.
-
-### N9 · Edge-aligned minimal
-Wordmark hard-left, single CTA hard-right, vast empty space between, no link row at all. The *absence* is the design — Apple product pages, Carl Hauser, luxury sites.
-*Use when:* the page is luxury / quiet / Atelier / Salon and the brand earns the silence.
-*Don't confuse with:* N1 Wordmark + 2 links (which fills the middle).
-
-```html
-<header class="nav-edge">
- <a class="wordmark">Studio</a>
- <a class="cta-outline">Get →</a>
-</header>
-```
-```css
-.nav-edge { display: flex; justify-content: space-between; align-items: center; padding: var(--space-md) var(--page-gutter); }
-.nav-edge .wordmark { font-family: var(--font-display); font-size: var(--text-md); }
-```
-
-*Anti-pattern:* adding 4 inline links between the wordmark and CTA "to fill the space". The space *is* the design; if you fill it, you've made N1 with extra steps.
-
-### N10 · Floating-on-scroll morph
-A sticky bar at the top that **morphs into a floating pill** as the user scrolls past a threshold. Two visual modes share one DOM — `.nav` (outer) owns the bar look, `.nav__inner` (inner) owns the pill look. Cross-faded on a single class toggle (`.is-floating`) with one timing curve. Active layer feels seamless; AI defaults always botch this.
-*Use when:* atmospheric / modern-minimal pages where the kinetic micro-moment earns its place. Adds a single tasteful surprise; resists novelty.
-*Don't confuse with:* N5 Floating pill (always-on, no scroll behaviour). N10 is N5 plus a default-bar state that morphs *into* it.
-
-```html
-<header class="nav">
- <div class="nav__inner">
- <a class="wordmark">Hallmark</a>
- <ul class="nav__links">…</ul>
- </div>
-</header>
-```
-
-The full recipe — the four laws (height-constant, transform-for-offset, cross-fade-everything, single-curve), the property-morph table, the scroll-handler script, and the eight anti-patterns Hallmark refuses — lives in [`floating-nav.md`](floating-nav.md). Reach for that file *before* building this archetype. Skipping the four laws is what makes 90% of attempts read as broken.
-
-*Anti-pattern (one of eight in floating-nav.md):* swapping two `<header>` elements via opacity instead of cross-fading one DOM. Doubles markup, fights focus order, desyncs content.
-
----
## Routing — which nav fits which genre / theme
@@ -913,6 +177,7 @@ The full recipe — the four laws (height-constant, transform-for-offset, cross-
---
+
## Picking from this file
When building a section:
@@ -927,6 +192,7 @@ The goal is composed variety — within a page, sections feel different from eac
---
+
## Mobile collapse — per archetype
Every archetype has a defined collapse behaviour at narrow viewports. The two breakpoints to know:
@@ -986,3 +252,5 @@ Below 60 rem the archetype must still feel like itself — same hierarchy, same
- Disable any scroll-linked animation below 40 rem (mobile scroll has its own physics; layered animations fight it).
- Image `loading="lazy"` always below the fold; **never on the LCP element regardless of viewport.**
- Auto-play video respects `data-saver` (`navigator.connection.saveData`) — replaces with poster when set.
+
+
diff --git a/skill/references/components/c1-outlined-chip.md b/skill/references/components/c1-outlined-chip.md
new file mode 100644
index 0000000..9319f53
--- /dev/null
+++ b/skill/references/components/c1-outlined-chip.md
@@ -0,0 +1,12 @@
+
+### C1 · Outlined chip
+A bordered, transparent button with a typographic verb ("Save changes").
+*Use when:* the page has one primary action; you want it visible but quiet.
+*Don't confuse with:* C2 Oversized solid (which is statement-loud).
+
+```html
+<a class="cta-outline">Open your studio →</a>
+```
+```css
+.cta-outline { display: inline-flex; align-items: center; gap: 0.4em; padding: 0.7rem 1.2rem; border: 1px solid var(--color-ink); min-height: 44px; }
+```
diff --git a/skill/references/components/c2-inline-form-as-cta.md b/skill/references/components/c2-inline-form-as-cta.md
new file mode 100644
index 0000000..9600223
--- /dev/null
+++ b/skill/references/components/c2-inline-form-as-cta.md
@@ -0,0 +1,16 @@
+### C2 · Inline form-as-CTA
+The CTA *is* the form — a single email input with a "Submit →" beside it. No separate landing for sign-up.
+*Use when:* the action is collecting an email.
+*Don't confuse with:* C1 Outlined chip (which navigates, not submits).
+
+```html
+<form class="cta-form">
+ <label for="email" class="visually-hidden">Email</label>
+ <input id="email" type="email" placeholder="[email protected]" />
+ <button type="submit">Send →</button>
+</form>
+```
+```css
+.cta-form { display: grid; grid-template-columns: 1fr auto; border-bottom: 1px solid var(--color-ink); }
+.cta-form input { background: none; border: 0; padding: 0.7rem 0; min-height: 44px; }
+```
diff --git a/skill/references/components/c3-typographic-link.md b/skill/references/components/c3-typographic-link.md
new file mode 100644
index 0000000..68ce77f
--- /dev/null
+++ b/skill/references/components/c3-typographic-link.md
@@ -0,0 +1,8 @@
+### C3 · Typographic link
+Just a word, an arrow, and a 1-px underline. No box, no fill.
+*Use when:* the page is editorial / Long Document; CTAs should not shout.
+*Don't confuse with:* C1 Outlined chip (which is bordered).
+
+```html
+<a class="link">Read the case study →</a>
+```
diff --git a/skill/references/components/c4-sticky-bottom-bar.md b/skill/references/components/c4-sticky-bottom-bar.md
new file mode 100644
index 0000000..8f8c05b
--- /dev/null
+++ b/skill/references/components/c4-sticky-bottom-bar.md
@@ -0,0 +1,16 @@
+### C4 · Sticky bottom bar
+A horizontal bar pinned to the viewport bottom, holding a CTA + a brief reassurance line.
+*Use when:* the page is long and the CTA needs to be reachable always.
+*Don't confuse with:* anything in the fold; this is a *persistent* element, not a hero CTA.
+
+```html
+<aside class="cta-sticky">
+ <span>Try it free for 14 days.</span>
+ <a class="cta-outline">Start →</a>
+</aside>
+```
+```css
+.cta-sticky { position: fixed; left: 0; right: 0; bottom: 0; padding: var(--space-sm) var(--space-md); background: var(--color-paper); border-top: 1px solid var(--color-rule); display: flex; justify-content: space-between; align-items: center; }
+```
+
+---
diff --git a/skill/references/components/f1-bento-grid.md b/skill/references/components/f1-bento-grid.md
new file mode 100644
index 0000000..fab987e
--- /dev/null
+++ b/skill/references/components/f1-bento-grid.md
@@ -0,0 +1,20 @@
+
+### F1 · Bento grid
+Asymmetric grid of 8–15 tiles in mixed spans (1×1, 2×1, 1×2, 2×2). Visual rhythm via size.
+*Use when:* multiple equally-valid entry points; SaaS feature page.
+*Don't confuse with:* F2 Sticky-scroll (which stacks vertically with sticky pacing).
+
+```html
+<section class="bento">
+ <article class="cell span-2x2">…</article>
+ <article class="cell span-1x1">…</article>
+ <article class="cell span-2x1">…</article>
+</section>
+```
+```css
+.bento { display: grid; grid-template-columns: repeat(4, 1fr); grid-auto-rows: 12rem; gap: var(--space-md); }
+.span-2x2 { grid-column: span 2; grid-row: span 2; }
+.span-2x1 { grid-column: span 2; }
+.span-1x2 { grid-row: span 2; }
+@media (max-width: 56rem) { .bento { grid-template-columns: repeat(2, 1fr); } }
+```
diff --git a/skill/references/components/f2-sticky-scroll-stack.md b/skill/references/components/f2-sticky-scroll-stack.md
new file mode 100644
index 0000000..b36965a
--- /dev/null
+++ b/skill/references/components/f2-sticky-scroll-stack.md
@@ -0,0 +1,17 @@
+### F2 · Sticky-scroll stack
+Sticky left pane, scrolling right pane that cycles through related screenshots.
+*Use when:* feature has multiple sub-states worth showing in sequence.
+*Don't confuse with:* F4 Step sequence (which is linearly numbered, not synced).
+
+```html
+<section class="sticky-stack">
+ <div class="pane-sticky"><h3>…</h3><p>…</p></div>
+ <div class="pane-scroll">
+ <figure>1</figure><figure>2</figure><figure>3</figure>
+ </div>
+</section>
+```
+```css
+.sticky-stack { display: grid; grid-template-columns: 1fr 1fr; gap: var(--space-2xl); }
+.pane-sticky { position: sticky; top: var(--space-xl); align-self: start; }
+```
diff --git a/skill/references/components/f3-tabular-spec-sheet.md b/skill/references/components/f3-tabular-spec-sheet.md
new file mode 100644
index 0000000..4007334
--- /dev/null
+++ b/skill/references/components/f3-tabular-spec-sheet.md
@@ -0,0 +1,11 @@
+### F3 · Tabular spec sheet
+Each row is a feature; columns hold name, value, footnote. Hairline rules between rows. Tabular numerics.
+*Use when:* features compare quantitatively.
+*Don't confuse with:* F1 Bento (which is non-tabular and visually rhythmic).
+
+```html
+<table class="spec-sheet tnum">
+ <tr><th>Latency</th><td>p99 &lt; 50 ms</td><td class="muted">measured externally</td></tr>
+ <tr>…</tr>
+</table>
+```
diff --git a/skill/references/components/f4-step-sequence.md b/skill/references/components/f4-step-sequence.md
new file mode 100644
index 0000000..ac82a18
--- /dev/null
+++ b/skill/references/components/f4-step-sequence.md
@@ -0,0 +1,11 @@
+### F4 · Step sequence
+Numbered stages (`1.0 → 2.0 → 3.0`) flow vertically. Each stage has a heading, a paragraph, sometimes a small visual.
+*Use when:* the product is a workflow, not a single moment.
+*Don't confuse with:* F2 Sticky-scroll (which doesn't number stages).
+
+```html
+<ol class="steps">
+ <li><span class="stage">1.0</span><h3>Intake.</h3><p>…</p></li>
+ <li><span class="stage">2.0</span><h3>Plan.</h3><p>…</p></li>
+</ol>
+```
diff --git a/skill/references/components/f5-annotated-screenshot.md b/skill/references/components/f5-annotated-screenshot.md
new file mode 100644
index 0000000..014aefd
--- /dev/null
+++ b/skill/references/components/f5-annotated-screenshot.md
@@ -0,0 +1,11 @@
+### F5 · Annotated screenshot
+A product capture sits centre-stage with arrows or short labels pointing to UI details.
+*Use when:* the product UI itself is the explanation.
+*Don't confuse with:* F2 Sticky-scroll (which uses multiple screenshots in sequence).
+
+```html
+<figure class="annotated">
+ <img src="" />
+ <span class="callout" style="--x:60%; --y:30%;">→ assigns automatically.</span>
+</figure>
+```
diff --git a/skill/references/components/f6-product-card-grid.md b/skill/references/components/f6-product-card-grid.md
new file mode 100644
index 0000000..1521921
--- /dev/null
+++ b/skill/references/components/f6-product-card-grid.md
@@ -0,0 +1,41 @@
+### F6 · Product card grid
+Each card is a product, not a feature. Image · name · price · one micro-action. Reads like a shop floor, not a marketing site.
+*Use when:* the brief is commerce, catalogue, lookbook, marketplace — anything where the page sells *things*, not *features*.
+*Don't confuse with:* F1 Bento (which sells *features*; tiles vary in size and span). Product cards are uniform on purpose — the rhythm comes from the products, not the layout.
+
+**Variation knobs:** card ratio (3/4 portrait · 1/1 square · 4/3 landscape) · density (3-up · 4-up · 5-up) · price treatment (under name · over image · hover-reveal) · micro-action (Add · Save · View → · none).
+
+```html
+<section class="product-grid">
+ <article class="product">
+ <a class="product__media" href=""><img src="" alt="" loading="lazy" /></a>
+ <div class="product__meta">
+ <h3 class="product__name">Linen Apron · Indigo</h3>
+ <p class="product__price tabular-nums">¥ 6,400</p>
+ </div>
+ <button class="product__add" aria-label="Add Linen Apron to bag">+</button>
+ </article>
+ <!-- ... more products, uniform shape ... -->
+</section>
+```
+```css
+.product-grid { display: grid; grid-template-columns: repeat(3, 1fr); gap: var(--space-xl) var(--space-lg); }
+@media (max-width: 60rem) { .product-grid { grid-template-columns: repeat(2, 1fr); } }
+.product { display: grid; gap: var(--space-sm); position: relative; }
+.product__media { display: block; aspect-ratio: 3 / 4; background: var(--color-paper-2); overflow: hidden; }
+.product__media img { width: 100%; height: 100%; object-fit: cover; transition: transform var(--dur-long) var(--ease-out); }
+.product__media:hover img { transform: scale(1.02); }
+.product__name { font-family: var(--font-body); font-size: var(--text-md); margin: 0; }
+.product__price { font-family: var(--font-mono); font-size: var(--text-sm); color: var(--color-ink-2); }
+.product__add { position: absolute; top: var(--space-sm); right: var(--space-sm); width: 32px; height: 32px; background: var(--color-paper); border: var(--rule-hair) solid var(--color-rule-2); cursor: pointer; opacity: 0; transition: opacity var(--dur-short) var(--ease-out); }
+.product:hover .product__add, .product:focus-within .product__add { opacity: 1; }
+@media (pointer: coarse) { .product__add { opacity: 1; } }
+```
+
+**Anti-patterns to avoid in product grids:**
+- Don't borrow Bento's irregular spans — products want uniform rhythm.
+- Don't put feature-style two-line descriptions under product names. The price *is* the description.
+- Don't auto-scale the image on idle — only on hover, and only by 1.02× max.
+- Don't use cards with shadow + radius + border + tile + ribbon. Pick one container signal.
+
+---
diff --git a/skill/references/components/ft1-mast-headed.md b/skill/references/components/ft1-mast-headed.md
new file mode 100644
index 0000000..92972cc
--- /dev/null
+++ b/skill/references/components/ft1-mast-headed.md
@@ -0,0 +1,13 @@
+
+### Ft1 · Mast-headed
+A wordmark and tagline anchor a single horizontal band. Two or three small links beside, address or licence below.
+*Use when:* the page has heavy content; the footer should be quiet and singular.
+*Don't confuse with:* Ft2 Inline-rule (which is even more reduced).
+
+```html
+<footer class="foot-mast">
+ <p class="wordmark">Studio Name</p>
+ <p class="tagline muted">Designs that don't look generated.</p>
+ <p class="links muted">Imprint · Privacy · Contact</p>
+</footer>
+```
diff --git a/skill/references/components/ft2-inline-rule-single-line.md b/skill/references/components/ft2-inline-rule-single-line.md
new file mode 100644
index 0000000..f994f8b
--- /dev/null
+++ b/skill/references/components/ft2-inline-rule-single-line.md
@@ -0,0 +1,10 @@
+### Ft2 · Inline-rule single line
+A single horizontal line of credits, address, copyright. Hairline rule above. No columns.
+*Use when:* the page is editorial and the footer is afterthought.
+*Don't confuse with:* Ft4 Dense typographic (which packs more in).
+
+```html
+<footer class="foot-line">
+ <p>© 2026 · 137 Marlow Street · MIT licensed</p>
+</footer>
+```
diff --git a/skill/references/components/ft3-index-style-category-list.md b/skill/references/components/ft3-index-style-category-list.md
new file mode 100644
index 0000000..a02f8d2
--- /dev/null
+++ b/skill/references/components/ft3-index-style-category-list.md
@@ -0,0 +1,12 @@
+### Ft3 · Index-style category list
+Three or four short columns, each headed by a category in small caps, holding 4–6 links each.
+*Use when:* the page is a hub or a documentation root.
+*Don't confuse with:* Ft4 Dense typographic (which is one big block, not columns).
+
+```html
+<footer class="foot-index">
+ <div><p class="caps">Product</p><ul>…</ul></div>
+ <div><p class="caps">Company</p><ul>…</ul></div>
+ <div><p class="caps">Resources</p><ul>…</ul></div>
+</footer>
+```
diff --git a/skill/references/components/ft4-dense-typographic.md b/skill/references/components/ft4-dense-typographic.md
new file mode 100644
index 0000000..7d2b250
--- /dev/null
+++ b/skill/references/components/ft4-dense-typographic.md
@@ -0,0 +1,10 @@
+### Ft4 · Dense typographic
+One large block of text — credits, references, licence, address — in a small monospace font, fully justified or ragged-right. Editorial colophon energy.
+*Use when:* the brand is editorial and a colophon-style sign-off fits.
+*Don't confuse with:* Ft3 Index (which navigates).
+
+```html
+<footer class="foot-dense mono">
+ <p>Hallmark v0.2.0. Built with The Future, Fraunces, IBM Plex Mono. MIT licensed. Powered by Together AI. 137 Marlow Street, 2026.</p>
+</footer>
+```
diff --git a/skill/references/components/ft5-statement.md b/skill/references/components/ft5-statement.md
new file mode 100644
index 0000000..e0d88a7
--- /dev/null
+++ b/skill/references/components/ft5-statement.md
@@ -0,0 +1,21 @@
+### Ft5 · Statement
+One large display sentence dominates the footer — a closing line, not a sitemap. Wordmark, minimal links, copyright sit beneath in muted small type. Stripe (older), Mailchimp pre-rebrand, agency portfolio closers.
+*Use when:* the page wants a *closing line* — editorial, manifesto, atmospheric. The sentence pairs with the page's argument.
+*Don't confuse with:* Ft1 Mast-headed (which leads with the wordmark, not a sentence).
+
+```html
+<footer class="foot-stmt">
+ <p class="foot-stmt__line">Build something they'll remember.</p>
+ <div class="foot-stmt__meta">
+ <span class="wordmark">Studio</span>
+ <span class="muted">© 2026 · MIT</span>
+ </div>
+</footer>
+```
+```css
+.foot-stmt { padding: var(--space-2xl) var(--page-gutter) var(--space-xl); display: grid; gap: var(--space-lg); }
+.foot-stmt__line { font-family: var(--font-display); font-size: clamp(1.75rem, 5vw, 3.25rem); line-height: 1.0; letter-spacing: -0.02em; max-width: 28ch; margin: 0; }
+.foot-stmt__meta { display: flex; justify-content: space-between; align-items: baseline; padding-block-start: var(--space-sm); border-top: var(--rule-hair) solid var(--color-rule); }
+```
+
+*Anti-pattern:* using a Statement footer on a docs root or hub. The sentence reads as marketing fluff there; default Ft3 instead.
diff --git a/skill/references/components/ft6-letter-close.md b/skill/references/components/ft6-letter-close.md
new file mode 100644
index 0000000..e41465d
--- /dev/null
+++ b/skill/references/components/ft6-letter-close.md
@@ -0,0 +1,19 @@
+### Ft6 · Letter close
+Closes the page like a letter — `Yours, the team. 2026.` Optional postscript line beneath. Sets the page as a piece of writing rather than a product.
+*Use when:* the page voice is warm, hand-written, editorial-quiet — Garden, Atelier, Salon, personal sites.
+*Don't confuse with:* Ft1 Mast-headed (which is a wordmark anchor, not a signoff).
+
+```html
+<footer class="foot-letter">
+ <p class="foot-letter__close">Yours,<br><span class="foot-letter__sign">— Studio</span></p>
+ <p class="foot-letter__ps muted">P.S. — letters back welcome at <a href="mailto:hello@studio">hello@studio</a>.</p>
+</footer>
+```
+```css
+.foot-letter { padding: var(--space-2xl) var(--page-gutter); max-width: 60ch; }
+.foot-letter__close { font-family: var(--font-display); font-style: italic; font-size: var(--text-lg); line-height: 1.4; }
+.foot-letter__sign { font-style: normal; font-weight: 600; }
+.foot-letter__ps { font-size: var(--text-sm); margin-top: var(--space-md); }
+```
+
+*Anti-pattern:* using Ft6 on a stat-led / B2B product page — voice mismatch reads as twee. Reserve for genuinely letter-shaped pages.
diff --git a/skill/references/components/ft7-newsletter-first.md b/skill/references/components/ft7-newsletter-first.md
new file mode 100644
index 0000000..df67edc
--- /dev/null
+++ b/skill/references/components/ft7-newsletter-first.md
@@ -0,0 +1,27 @@
+### Ft7 · Newsletter-first
+The form (label + input + submit) is the *primary* element of the footer; everything else (wordmark, links, copyright) is set in 12 px muted type beneath. Stratechery, Substack-shaped sites, indie magazines.
+*Use when:* the brand legitimately publishes — and the page above the fold has *already* offered a subscription. The footer is a final invitation, not an ambush.
+*Don't confuse with:* Ft1 (which doesn't ask for anything).
+
+```html
+<footer class="foot-news">
+ <form class="foot-news__form" action="/subscribe" method="post">
+ <label for="foot-email">Letters from the studio · monthly</label>
+ <div class="foot-news__row">
+ <input id="foot-email" name="email" type="email" required placeholder="you@domain">
+ <button type="submit" class="cta-fill">Subscribe</button>
+ </div>
+ </form>
+ <p class="foot-news__meta muted">Studio · © 2026 · <a href="/imprint">Imprint</a></p>
+</footer>
+```
+```css
+.foot-news { padding: var(--space-2xl) var(--page-gutter); display: grid; gap: var(--space-lg); max-width: 56ch; }
+.foot-news__form label { display: block; font-size: var(--text-sm); margin-block-end: var(--space-2xs); }
+.foot-news__row { display: flex; gap: var(--space-2xs); }
+.foot-news__row input { flex: 1; min-height: 44px; padding-inline: var(--space-sm); border: var(--rule-hair) solid var(--color-rule); border-radius: var(--radius-input); background: var(--color-paper); }
+.foot-news__row input:focus-visible { outline: 2px solid var(--color-focus); outline-offset: 1px; }
+.foot-news__meta { font-size: var(--text-xs); }
+```
+
+*Anti-pattern:* Ft7 when the page never said "subscribe" above the fold. The footer is an honest *conclusion*; if you didn't ask, don't ambush. Drop to Ft2 instead.
diff --git a/skill/references/components/ft8-marquee-scroll.md b/skill/references/components/ft8-marquee-scroll.md
new file mode 100644
index 0000000..e5a0f29
--- /dev/null
+++ b/skill/references/components/ft8-marquee-scroll.md
@@ -0,0 +1,25 @@
+### Ft8 · Marquee scroll
+A horizontal infinite-scroll line of repeating tagline + dot separator: `STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 ·`. Sport-genre sites, fashion lookbooks, brand-forward agencies.
+*Use when:* the brand voice is loud, kinetic, sport-or-manifesto.
+*Don't confuse with:* Ft4 Dense colophon (which is static text).
+
+```html
+<footer class="foot-marquee" aria-label="Footer">
+ <div class="foot-marquee__track" aria-hidden="true">
+ <span>STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 ·</span>
+ <span>STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 · STUDIO · 2026 ·</span>
+ </div>
+ <p class="visually-hidden">Studio · 2026 · MIT licensed</p>
+</footer>
+```
+```css
+.foot-marquee { overflow: hidden; border-top: 2px solid var(--color-ink); }
+.foot-marquee__track { display: flex; gap: var(--space-2xl); white-space: nowrap; padding-block: var(--space-md); animation: foot-marquee 32s linear infinite; }
+.foot-marquee__track span { font-family: var(--font-display); font-weight: 700; letter-spacing: 0.08em; font-size: clamp(1rem, 2.5vw, 1.5rem); }
+@keyframes foot-marquee { from { transform: translateX(0); } to { transform: translateX(-50%); } }
+@media (prefers-reduced-motion: reduce) { .foot-marquee__track { animation: none; } }
+```
+
+*Anti-pattern:* using Ft8 on editorial / quiet contexts — the motion reads as loud. Pair only with playful / sport / manifesto voices, and always honour `prefers-reduced-motion: reduce`.
+
+---
diff --git a/skill/references/components/h1-marquee.md b/skill/references/components/h1-marquee.md
new file mode 100644
index 0000000..b15087c
--- /dev/null
+++ b/skill/references/components/h1-marquee.md
@@ -0,0 +1,15 @@
+
+### H1 · Marquee
+A single statement fills the fold. No subhead, no CTA in view.
+*Use when:* the brand or person *is* the message.
+*Don't confuse with:* H4 Stat-Led (which is a number, not a statement).
+
+```html
+<section class="hero-marquee">
+ <h1 class="display-xxl">A statement.</h1>
+</section>
+```
+```css
+.hero-marquee { min-height: 80dvh; display: grid; align-content: end; padding: 0 var(--page-gutter) var(--space-2xl); }
+.display-xxl { font-size: clamp(4rem, 12vw, 12rem); line-height: 0.92; }
+```
diff --git a/skill/references/components/h2-split-diptych.md b/skill/references/components/h2-split-diptych.md
new file mode 100644
index 0000000..f5c8cae
--- /dev/null
+++ b/skill/references/components/h2-split-diptych.md
@@ -0,0 +1,15 @@
+### H2 · Split Diptych
+Headline + lede on one side, image or product capture on the other. 6/6 or 7/5 columns.
+*Use when:* you can pair every claim with a visual proof.
+*Don't confuse with:* H6 Photographic (which puts the image full-bleed, not paired).
+
+```html
+<section class="hero-split">
+ <div><h1>…</h1><p>…</p><a class="cta-outline">…</a></div>
+ <figure><img src="" /></figure>
+</section>
+```
+```css
+.hero-split { display: grid; grid-template-columns: 7fr 5fr; gap: var(--space-2xl); align-items: center; }
+@media (max-width: 56rem) { .hero-split { grid-template-columns: 1fr; } }
+```
diff --git a/skill/references/components/h3-quote-led.md b/skill/references/components/h3-quote-led.md
new file mode 100644
index 0000000..e2bb455
--- /dev/null
+++ b/skill/references/components/h3-quote-led.md
@@ -0,0 +1,11 @@
+### H3 · Quote-Led
+A pull-quote with attribution is the hero. Your headline is borrowed credibility.
+*Use when:* you have a real testimonial that earns the front page.
+*Don't confuse with:* T3 Single huge quote (which lives mid-page, not in the hero slot).
+
+```html
+<section class="hero-quote">
+ <blockquote class="display-italic">"…"</blockquote>
+ <p class="attribution">— Name, Role, Company</p>
+</section>
+```
diff --git a/skill/references/components/h4-stat-led.md b/skill/references/components/h4-stat-led.md
new file mode 100644
index 0000000..414815a
--- /dev/null
+++ b/skill/references/components/h4-stat-led.md
@@ -0,0 +1,14 @@
+### H4 · Stat-Led
+A giant number or metric is the hero. A small qualifier line below.
+*Use when:* you have one defensible, externally-verifiable number.
+*Don't confuse with:* T4 Numbered stat strip (which is several stats in a row, not one focal).
+
+```html
+<section class="hero-stat">
+ <p class="figure tnum">99.97<span class="unit">%</span></p>
+ <p class="qualifier">…</p>
+</section>
+```
+```css
+.figure { font-size: clamp(6rem, 18vw, 16rem); font-variant-numeric: tabular-nums; line-height: 0.85; }
+```
diff --git a/skill/references/components/h5-letter-hero.md b/skill/references/components/h5-letter-hero.md
new file mode 100644
index 0000000..19a7e74
--- /dev/null
+++ b/skill/references/components/h5-letter-hero.md
@@ -0,0 +1,11 @@
+### H5 · Letter Hero
+First-person opening — "Dear reader,". No buttons in fold. Reads as personal correspondence.
+*Use when:* the founder's voice is the brand.
+*Don't confuse with:* H1 Marquee (which is impersonal declaration).
+
+```html
+<section class="hero-letter">
+ <p class="salutation"><em>Dear reader,</em></p>
+ <p class="lede">…</p>
+</section>
+```
diff --git a/skill/references/components/h6-photographic-fold.md b/skill/references/components/h6-photographic-fold.md
new file mode 100644
index 0000000..4aaf01d
--- /dev/null
+++ b/skill/references/components/h6-photographic-fold.md
@@ -0,0 +1,16 @@
+### H6 · Photographic Fold
+Single full-bleed image fills the viewport. Caption sits in a corner.
+*Use when:* you have real photography that earns full-bleed.
+*Don't confuse with:* H2 Split (which pairs image with text in a grid).
+
+```html
+<section class="hero-photo">
+ <img class="bleed" src="" alt="" />
+ <p class="caption">Spring, 2026.</p>
+</section>
+```
+```css
+.hero-photo { position: relative; height: 80dvh; }
+.hero-photo .bleed { width: 100%; height: 100%; object-fit: cover; }
+.hero-photo .caption { position: absolute; bottom: var(--space-md); right: var(--space-md); }
+```
diff --git a/skill/references/components/h7-demo-video-clipped-by-viewport-edge.md b/skill/references/components/h7-demo-video-clipped-by-viewport-edge.md
new file mode 100644
index 0000000..5cc9ad6
--- /dev/null
+++ b/skill/references/components/h7-demo-video-clipped-by-viewport-edge.md
@@ -0,0 +1,27 @@
+### H7 · Demo Video — Clipped-by-viewport-edge
+Display headline left, demo video right, the rightmost ~10–20 % extending past the viewport so it's intentionally cut off. The clip *is* the design — implies "there's more product than fits the screen". Pioneered by Linear, refined by Vercel / Resend / Cursor.
+*Use when:* the brief is SaaS / dev-tool / dashboard / platform AND you have real footage of the product (or a hand-built CSS-art mockup of it).
+*Don't confuse with:* H4 Stat-Led (number-led, no video) or H8 Mockup Split (still screenshot, not video).
+
+See [`hero-enrichment.md`](hero-enrichment.md) for the full E1 recipe (codec chain, autoplay rules, `prefers-reduced-motion` fallback, mobile collapse). The cookbook entry below is the structural sketch.
+
+```html
+<section class="hero hero--clipped">
+ <div class="hero__copy">
+ <h1>Plan, build, ship.</h1>
+ <p>The project tracker your engineering team won't ignore.</p>
+ </div>
+ <figure class="hero__media">
+ <video autoplay muted loop playsinline preload="metadata"
+ poster="/hero-poster.webp" fetchpriority="high">
+ <source src="/hero.av1.mp4" type='video/mp4; codecs="av01.0.05M.08"'>
+ <source src="/hero.h264.mp4" type="video/mp4">
+ </video>
+ </figure>
+</section>
+```
+```css
+.hero--clipped { display: grid; grid-template-columns: 1fr 1.4fr; gap: var(--space-2xl); overflow: visible; }
+.hero__media { width: calc(100% + 12vw); aspect-ratio: 16 / 10; border-radius: 12px; overflow: hidden; }
+@media (max-width: 60rem) { .hero--clipped { grid-template-columns: 1fr; } .hero__media { width: 100%; } }
+```
diff --git a/skill/references/components/h8-mockup-split-browser-framed.md b/skill/references/components/h8-mockup-split-browser-framed.md
new file mode 100644
index 0000000..7159f77
--- /dev/null
+++ b/skill/references/components/h8-mockup-split-browser-framed.md
@@ -0,0 +1,23 @@
+### H8 · Mockup Split (browser-framed)
+Headline left, browser-frame mockup right, the mockup tilted 1–3° for life. Frame can be browser chrome, macOS toolbar, minimal hairline, or floating no-frame.
+*Use when:* you're selling a web app and you have a clean, well-lit screenshot.
+*Don't confuse with:* H7 Clipped-Edge (which extends past the viewport) or H2 Split Diptych (which uses photography or proof column, not a product mockup).
+
+```html
+<section class="hero-mock">
+ <div>
+ <h1>The studio's new mute button.</h1>
+ <p>Press <kbd>⌘ M</kbd> from anywhere.</p>
+ </div>
+ <figure class="mock">
+ <header class="mock__chrome"><span></span><span></span><span></span></header>
+ <div class="mock__body"><!-- screenshot or CSS-art mockup --></div>
+ </figure>
+</section>
+```
+```css
+.hero-mock { display: grid; grid-template-columns: 1fr 1.2fr; gap: var(--space-2xl); align-items: center; }
+.mock { transform: rotate(1.5deg); border-radius: 12px; overflow: hidden; box-shadow: 0 24px 60px -20px oklch(20% 0.02 60 / 0.18); }
+.mock__chrome { display: flex; gap: 6px; padding: 10px 12px; background: var(--color-paper-2); border-block-end: var(--rule-hair) solid var(--color-rule); }
+.mock__chrome span { width: 10px; height: 10px; border-radius: 50%; background: var(--color-rule-2); }
+```
diff --git a/skill/references/components/h9-custom-illustration-centerpiece.md b/skill/references/components/h9-custom-illustration-centerpiece.md
new file mode 100644
index 0000000..8a1dfdb
--- /dev/null
+++ b/skill/references/components/h9-custom-illustration-centerpiece.md
@@ -0,0 +1,27 @@
+### H9 · Custom Illustration Centerpiece
+A single hand-built SVG (Tier B in the enrichment hierarchy — or pure CSS at Tier A for simpler shapes) sitting on the hero as one illustrative element. The bakery loaf, the studio's mascot, the workflow diagram.
+*Use when:* the brand has a *thing* that benefits from being drawn — a craft, a character, a process.
+*Don't confuse with:* H6 Photographic (real photography) or H8 Mockup (a product screenshot, not artwork).
+
+The illustration itself is *built*, not picked from Storyset / Humaaans / unDraw / Lottie. See [`custom-craft.md`](custom-craft.md) for full recipes (CSS art, hand-built SVG, declarative animation). The cookbook entry below is the page-level structural sketch.
+
+```html
+<section class="hero-art">
+ <div>
+ <p class="eyebrow">Maple Street Bread · est. 2026</p>
+ <h1>Sourdough, every morning.</h1>
+ <p>Slow-fermented overnight, baked on stone, before you wake.</p>
+ </div>
+ <svg viewBox="0 0 200 100" class="loaf" aria-label="A loaf of bread">
+ <path class="loaf__body" d="M 20 70 Q 100 10 180 70 L 180 90 L 20 90 Z" />
+ <path class="loaf__score" d="M 60 50 L 90 30 M 100 45 L 130 25 M 140 50 L 165 35" />
+ </svg>
+</section>
+```
+```css
+.hero-art { display: grid; grid-template-columns: 1fr 1fr; gap: var(--space-2xl); align-items: center; }
+.loaf__body { fill: oklch(72% 0.14 50); }
+.loaf__score{ stroke: oklch(38% 0.10 35); stroke-width: 2; fill: none; stroke-linecap: round; }
+```
+
+---
diff --git a/skill/references/components/n1-wordmark-2-links.md b/skill/references/components/n1-wordmark-2-links.md
new file mode 100644
index 0000000..f74a5b0
--- /dev/null
+++ b/skill/references/components/n1-wordmark-2-links.md
@@ -0,0 +1,12 @@
+
+### N1 · Wordmark + 2 links
+Top-of-page bar: wordmark on the left, two text links on the right ("Pricing" / "Sign in"). No logo image, no menu icon.
+*Use when:* the page has very few destinations.
+*Don't confuse with:* N3 Side-rail (which is vertical).
+
+```html
+<nav class="nav-min">
+ <a class="wordmark">Studio</a>
+ <ul><li><a>Pricing</a></li><li><a>Sign in</a></li></ul>
+</nav>
+```
diff --git a/skill/references/components/n10-floating-on-scroll-morph.md b/skill/references/components/n10-floating-on-scroll-morph.md
new file mode 100644
index 0000000..b0116b4
--- /dev/null
+++ b/skill/references/components/n10-floating-on-scroll-morph.md
@@ -0,0 +1,19 @@
+### N10 · Floating-on-scroll morph
+A sticky bar at the top that **morphs into a floating pill** as the user scrolls past a threshold. Two visual modes share one DOM — `.nav` (outer) owns the bar look, `.nav__inner` (inner) owns the pill look. Cross-faded on a single class toggle (`.is-floating`) with one timing curve. Active layer feels seamless; AI defaults always botch this.
+*Use when:* atmospheric / modern-minimal pages where the kinetic micro-moment earns its place. Adds a single tasteful surprise; resists novelty.
+*Don't confuse with:* N5 Floating pill (always-on, no scroll behaviour). N10 is N5 plus a default-bar state that morphs *into* it.
+
+```html
+<header class="nav">
+ <div class="nav__inner">
+ <a class="wordmark">Hallmark</a>
+ <ul class="nav__links">…</ul>
+ </div>
+</header>
+```
+
+The full recipe — the four laws (height-constant, transform-for-offset, cross-fade-everything, single-curve), the property-morph table, the scroll-handler script, and the eight anti-patterns Hallmark refuses — lives in [`floating-nav.md`](floating-nav.md). Reach for that file *before* building this archetype. Skipping the four laws is what makes 90% of attempts read as broken.
+
+*Anti-pattern (one of eight in floating-nav.md):* swapping two `<header>` elements via opacity instead of cross-fading one DOM. Doubles markup, fights focus order, desyncs content.
+
+---
diff --git a/skill/references/components/n2-floating-chip.md b/skill/references/components/n2-floating-chip.md
new file mode 100644
index 0000000..b4dcc97
--- /dev/null
+++ b/skill/references/components/n2-floating-chip.md
@@ -0,0 +1,14 @@
+### N2 · Floating chip
+A small fixed chip in a corner — wordmark + a single action ("Try it"). Doesn't sit in document flow.
+*Use when:* the page is fold-heavy and traditional nav would fight the content.
+*Don't confuse with:* C4 Sticky bottom bar (which is full-width).
+
+```html
+<aside class="nav-chip">
+ <a class="wordmark">Studio</a>
+ <a class="cta-outline">Try →</a>
+</aside>
+```
+```css
+.nav-chip { position: fixed; top: var(--space-md); right: var(--space-md); display: inline-flex; gap: var(--space-md); padding: 0.5rem 0.75rem; background: var(--color-paper); border: 1px solid var(--color-rule); }
+```
diff --git a/skill/references/components/n3-side-rail.md b/skill/references/components/n3-side-rail.md
new file mode 100644
index 0000000..a31ddfb
--- /dev/null
+++ b/skill/references/components/n3-side-rail.md
@@ -0,0 +1,14 @@
+### N3 · Side-rail
+A thin vertical strip on the left edge — wordmark rotated, plus 2–3 dot-indicators for sections. Editorial / portfolio energy.
+*Use when:* the page is long and section-numbered.
+*Don't confuse with:* N1 Top wordmark (which is horizontal).
+
+```html
+<nav class="nav-rail">
+ <p class="wordmark vertical">Studio</p>
+ <ul class="dots"><li></li><li></li><li></li></ul>
+</nav>
+```
+```css
+.nav-rail { position: fixed; left: 0; top: 0; bottom: 0; width: 3rem; padding: var(--space-md); writing-mode: vertical-rl; }
+```
diff --git a/skill/references/components/n4-hidden-behind-k.md b/skill/references/components/n4-hidden-behind-k.md
new file mode 100644
index 0000000..24a4f3f
--- /dev/null
+++ b/skill/references/components/n4-hidden-behind-k.md
@@ -0,0 +1,9 @@
+### N4 · Hidden behind ⌘K
+No visible nav. The user opens a command palette via `⌘K` to get anywhere. Designed for keyboard-first audiences.
+*Use when:* the page is for technical users who expect this affordance.
+*Don't confuse with:* N2 Floating chip (which is visible always).
+
+```html
+<button class="kbd-hint">⌘ K</button>
+<dialog class="palette">…</dialog>
+```
diff --git a/skill/references/components/n5-floating-pill.md b/skill/references/components/n5-floating-pill.md
new file mode 100644
index 0000000..b6170f3
--- /dev/null
+++ b/skill/references/components/n5-floating-pill.md
@@ -0,0 +1,28 @@
+### N5 · Floating pill
+A rounded full-pill nav, *visibly detached* from the page edges, sitting ~`var(--space-md)` from the top, soft blur backdrop, soft shadow. Reads as contemporary modern-minimal — Vercel, Linear, Framer, Raycast.
+*Use when:* the page is modern-minimal / atmospheric and the hero has a distinct surface or imagery beneath the pill that the blur can sit over.
+*Don't confuse with:* N1 Wordmark + 2 links (which is full-width); N2 Floating chip (which is corner-anchored).
+
+```html
+<nav class="nav-pill" aria-label="Primary">
+ <a class="wordmark">Studio</a>
+ <ul class="nav-pill__links"><li><a>Catalog</a></li><li><a>Voice</a></li></ul>
+ <a class="cta-fill">Get →</a>
+</nav>
+```
+```css
+.nav-pill {
+ position: fixed; inset: var(--space-md) auto auto 50%;
+ transform: translateX(-50%);
+ display: inline-flex; align-items: center; gap: var(--space-md);
+ padding: 0.5rem 0.875rem;
+ background: color-mix(in oklch, var(--color-paper) 78%, transparent);
+ backdrop-filter: blur(14px) saturate(120%);
+ border: var(--rule-hair) solid var(--color-rule);
+ border-radius: 999px;
+ box-shadow: 0 8px 24px -12px oklch(0% 0 0 / 0.18);
+ z-index: 20;
+}
+```
+
+*Anti-pattern:* a "pill" that's ~95 % viewport-wide is just a full-width nav with rounded ends — defeats the point. The pill must be visibly detached and content-sized; if your link list pushes it past ~720 px, drop a link or switch to N1.
diff --git a/skill/references/components/n6-newspaper-masthead.md b/skill/references/components/n6-newspaper-masthead.md
new file mode 100644
index 0000000..24f055a
--- /dev/null
+++ b/skill/references/components/n6-newspaper-masthead.md
@@ -0,0 +1,24 @@
+### N6 · Newspaper masthead
+Full-width header, large centred wordmark on the top row, thin issue/date line above or below in serif small caps, optional inline link row beneath, double-rule below the whole thing. Reads as editorial, broadsheet — NYT, FT, Vogue.
+*Use when:* the page is editorial, magazine-shaped, or framed as an issue / edition.
+*Don't confuse with:* N1 Wordmark + 2 links (which is asymmetric and small).
+
+```html
+<header class="nav-mast">
+ <p class="mast-line muted">No 22 · Spring 2026 · Studio</p>
+ <h1 class="mast-name">STUDIO</h1>
+ <nav class="mast-nav" aria-label="Primary">
+ <ul><li><a>Catalog</a></li><li><a>Voice</a></li><li><a>Letters</a></li></ul>
+ </nav>
+ <hr class="mast-rule double" aria-hidden="true">
+</header>
+```
+```css
+.nav-mast { display: grid; gap: var(--space-2xs); padding: var(--space-md) var(--page-gutter) 0; text-align: center; }
+.mast-name { font-family: var(--font-display); font-size: clamp(2.25rem, 5vw, 3.75rem); letter-spacing: -0.01em; line-height: 0.95; margin: 0; }
+.mast-line { font-variant: small-caps; letter-spacing: 0.08em; font-size: var(--text-xs); }
+.mast-nav ul { display: inline-flex; gap: var(--space-md); list-style: none; padding: 0; margin: var(--space-2xs) 0 0; }
+.mast-rule.double { border: 0; border-top: var(--rule-hair) solid var(--color-rule); border-bottom: var(--rule-hair) solid var(--color-rule); height: 4px; margin: var(--space-sm) 0 0; }
+```
+
+*Anti-pattern:* using N6 on a SaaS dashboard or a developer-tool product page. The masthead vocabulary belongs to long-form / editorial sites; on a B2B product, it reads as costume.
diff --git a/skill/references/components/n7-brutal-slab.md b/skill/references/components/n7-brutal-slab.md
new file mode 100644
index 0000000..24d0f0f
--- /dev/null
+++ b/skill/references/components/n7-brutal-slab.md
@@ -0,0 +1,22 @@
+### N7 · Brutal slab
+A heavy, full-width nav with a 2 px solid border-bottom, all-caps wordmark and tracked uppercase link row, dense rhythm, no shadow, no rounded corners. Reads as Pentagram project pages, Liquid Death, brutalist-leaning agencies.
+*Use when:* the genre is playful (Brutal, Manifesto, Sport) or the brand voice is heavy / declarative.
+*Don't confuse with:* N1 Wordmark + 2 links (which is small and quiet).
+
+```html
+<header class="nav-slab">
+ <a class="slab-mark">STUDIO</a>
+ <nav class="slab-nav" aria-label="Primary">
+ <ul><li><a>CATALOG</a></li><li><a>VOICE</a></li><li><a>WORK</a></li></ul>
+ </nav>
+ <a class="cta-fill cta-fill--slab">GET</a>
+</header>
+```
+```css
+.nav-slab { display: flex; align-items: center; gap: var(--space-md); padding: var(--space-sm) var(--page-gutter); border-bottom: 2px solid var(--color-ink); background: var(--color-paper); }
+.slab-mark { font-family: var(--font-display); font-weight: 800; letter-spacing: 0.04em; }
+.slab-nav ul { display: flex; gap: var(--space-md); list-style: none; padding: 0; margin: 0 0 0 auto; }
+.slab-nav a { text-transform: uppercase; letter-spacing: 0.08em; font-size: var(--text-sm); font-weight: 600; }
+```
+
+*Anti-pattern:* combining N7 with rounded corners, soft shadows, or backdrop-blur — those vocabularies fight. If you reach for blur, drop to N5; if you reach for round, drop to N1.
diff --git a/skill/references/components/n8-terminal-command.md b/skill/references/components/n8-terminal-command.md
new file mode 100644
index 0000000..17c23a7
--- /dev/null
+++ b/skill/references/components/n8-terminal-command.md
@@ -0,0 +1,21 @@
+### N8 · Terminal command
+A nav formatted as a CLI prompt: `> studio --catalog --voice --get▮`. The "links" are command flags. The blinking cursor (`▮`) is allowed *only here* (it has purpose — signals "you'd type next"); never standalone elsewhere on the page. Reads as Vercel CLI docs landing, Charm, Mitchell Hashimoto's site.
+*Use when:* the page is a CLI tool, dev-tool docs, or carries the Terminal theme.
+*Don't confuse with:* N4 ⌘K-only (which is a palette, not a visible bar).
+
+```html
+<header class="nav-term">
+ <pre class="nav-term__line"><span class="prompt">&gt;</span> studio <a href="#catalog">--catalog</a> <a href="#voice">--voice</a> <a href="#get">--get</a><span class="caret" aria-hidden="true">▮</span></pre>
+</header>
+```
+```css
+.nav-term { padding: var(--space-sm) var(--page-gutter); border-bottom: var(--rule-hair) solid var(--color-rule); }
+.nav-term__line { font-family: var(--font-outlier, ui-monospace, "JetBrains Mono", monospace); font-size: var(--text-sm); margin: 0; }
+.nav-term__line .prompt { color: var(--color-accent); padding-right: 0.4ch; }
+.nav-term__line a { color: var(--color-ink); text-decoration: underline; text-underline-offset: 2px; }
+.caret { display: inline-block; width: 1ch; animation: blink 1.05s steps(2) infinite; color: var(--color-accent); }
+@keyframes blink { 50% { opacity: 0; } }
+@media (prefers-reduced-motion: reduce) { .caret { animation: none; opacity: 1; } }
+```
+
+*Anti-pattern:* using `>` prompt vocabulary on a non-developer site (a wedding photographer's portfolio with a `> view --gallery` nav reads as set decoration). N8 belongs to genuine terminal / CLI brands only.
diff --git a/skill/references/components/n9-edge-aligned-minimal.md b/skill/references/components/n9-edge-aligned-minimal.md
new file mode 100644
index 0000000..e9a11f0
--- /dev/null
+++ b/skill/references/components/n9-edge-aligned-minimal.md
@@ -0,0 +1,17 @@
+### N9 · Edge-aligned minimal
+Wordmark hard-left, single CTA hard-right, vast empty space between, no link row at all. The *absence* is the design — Apple product pages, Carl Hauser, luxury sites.
+*Use when:* the page is luxury / quiet / Atelier / Salon and the brand earns the silence.
+*Don't confuse with:* N1 Wordmark + 2 links (which fills the middle).
+
+```html
+<header class="nav-edge">
+ <a class="wordmark">Studio</a>
+ <a class="cta-outline">Get →</a>
+</header>
+```
+```css
+.nav-edge { display: flex; justify-content: space-between; align-items: center; padding: var(--space-md) var(--page-gutter); }
+.nav-edge .wordmark { font-family: var(--font-display); font-size: var(--text-md); }
+```
+
+*Anti-pattern:* adding 4 inline links between the wordmark and CTA "to fill the space". The space *is* the design; if you fill it, you've made N1 with extra steps.
diff --git a/skill/references/components/s1-left-margin-numbered.md b/skill/references/components/s1-left-margin-numbered.md
new file mode 100644
index 0000000..14a5938
--- /dev/null
+++ b/skill/references/components/s1-left-margin-numbered.md
@@ -0,0 +1,15 @@
+
+### S1 · Left-margin numbered
+A narrow left column holds `01 — LABEL.`; the wide right column holds the heading and content.
+*Use when:* the page is editorial / specimen.
+*Don't confuse with:* S5 Bottom-anchored (which puts the label *under* the section).
+
+```html
+<header class="head-margin">
+ <p class="num-label">01 — Foundations</p>
+ <h2>…</h2>
+</header>
+```
+```css
+.head-margin { display: grid; grid-template-columns: 10rem 1fr; gap: var(--space-xl); align-items: baseline; }
+```
diff --git a/skill/references/components/s2-hanging.md b/skill/references/components/s2-hanging.md
new file mode 100644
index 0000000..57531f3
--- /dev/null
+++ b/skill/references/components/s2-hanging.md
@@ -0,0 +1,13 @@
+### S2 · Hanging
+Heading floats above the section in negative space; no border, no rule.
+*Use when:* the content has a quiet, room-to-breathe energy.
+*Don't confuse with:* S3 Sticky-pinned (which moves with scroll).
+
+```html
+<header class="head-hang">
+ <h2>…</h2>
+</header>
+```
+```css
+.head-hang { padding-block: var(--space-3xl) var(--space-xl); }
+```
diff --git a/skill/references/components/s3-sticky-pinned.md b/skill/references/components/s3-sticky-pinned.md
new file mode 100644
index 0000000..77c68ec
--- /dev/null
+++ b/skill/references/components/s3-sticky-pinned.md
@@ -0,0 +1,14 @@
+### S3 · Sticky pinned
+Heading remains in viewport while content scrolls beneath. Orientation aid.
+*Use when:* the section is dense and the user benefits from always seeing where they are.
+*Don't confuse with:* S1 Left-margin (which doesn't move).
+
+```html
+<header class="head-sticky">
+ <p class="num-label">02</p>
+ <h2>…</h2>
+</header>
+```
+```css
+.head-sticky { position: sticky; top: 0; background: var(--color-paper); padding-block: var(--space-sm); border-bottom: 1px solid var(--color-ink); z-index: 10; }
+```
diff --git a/skill/references/components/s4-inline-no-break.md b/skill/references/components/s4-inline-no-break.md
new file mode 100644
index 0000000..6d6d03f
--- /dev/null
+++ b/skill/references/components/s4-inline-no-break.md
@@ -0,0 +1,11 @@
+### S4 · Inline (no break)
+The heading is a small caps phrase that emerges *inside* the body flow; no spatial break.
+*Use when:* the page is prose-led; reading should be continuous.
+*Don't confuse with:* S2 Hanging (which separates with negative space).
+
+```html
+<p>… <span class="head-inline">A small heading.</span> …</p>
+```
+```css
+.head-inline { font-variant-caps: all-small-caps; letter-spacing: 0.06em; font-weight: 500; }
+```
diff --git a/skill/references/components/s5-bottom-anchored.md b/skill/references/components/s5-bottom-anchored.md
new file mode 100644
index 0000000..1f84a97
--- /dev/null
+++ b/skill/references/components/s5-bottom-anchored.md
@@ -0,0 +1,13 @@
+### S5 · Bottom-anchored
+The label or heading sits *below* the section's content. Inverts hierarchy.
+*Use when:* the content is the primary act and the label is a footer to it.
+*Don't confuse with:* S1 Left-margin (which leads with the label).
+
+```html
+<section>
+ <div class="content">…</div>
+ <p class="num-label">— end of 02</p>
+</section>
+```
+
+---
diff --git a/skill/references/components/t1-pull-quote-with-marginalia.md b/skill/references/components/t1-pull-quote-with-marginalia.md
new file mode 100644
index 0000000..95c9207
--- /dev/null
+++ b/skill/references/components/t1-pull-quote-with-marginalia.md
@@ -0,0 +1,12 @@
+
+### T1 · Pull-quote with marginalia
+A quote sits in the wide column; the attribution and source link float in the narrow margin column.
+*Use when:* the page already has a marginalia rhythm (Tufte-leaning, editorial).
+*Don't confuse with:* T3 Single huge quote (which is centered and dominates).
+
+```html
+<aside class="proof-margin">
+ <blockquote class="serif-italic">"…"</blockquote>
+ <p class="attribution muted">— Name<br />Role, Company</p>
+</aside>
+```
diff --git a/skill/references/components/t2-logo-wall-hairline.md b/skill/references/components/t2-logo-wall-hairline.md
new file mode 100644
index 0000000..1ac2a14
--- /dev/null
+++ b/skill/references/components/t2-logo-wall-hairline.md
@@ -0,0 +1,19 @@
+### T2 · Logo wall (hairline)
+A row of customer logos, monochromatic, separated by hairline rules. No card boxes, no shadows.
+*Use when:* you have recognisable customers and want to surface them quietly.
+*Don't confuse with:* the AI-default 6-logo box grid; this version refuses card boxes.
+
+```html
+<section class="logo-wall">
+ <ul>
+ <li><img src="" /></li>
+ <li><img src="" /></li>
+ <li><img src="" /></li>
+ </ul>
+</section>
+```
+```css
+.logo-wall ul { display: grid; grid-template-columns: repeat(auto-fit, minmax(8rem, 1fr)); gap: 0; }
+.logo-wall li { padding: var(--space-md); border-right: 1px solid var(--color-rule); display: grid; place-items: center; }
+.logo-wall img { filter: grayscale(1); opacity: 0.7; }
+```
diff --git a/skill/references/components/t3-single-huge-quote.md b/skill/references/components/t3-single-huge-quote.md
new file mode 100644
index 0000000..71011d4
--- /dev/null
+++ b/skill/references/components/t3-single-huge-quote.md
@@ -0,0 +1,11 @@
+### T3 · Single huge quote
+One quote, set big, centered, taking a whole section. No supporting text, no attribution boxes — attribution is a small caps line beneath.
+*Use when:* one quote is so good it earns the room.
+*Don't confuse with:* T1 Margin pull-quote (which is the *side* mate, not the *room*).
+
+```html
+<section class="proof-room">
+ <blockquote class="display-italic">"…"</blockquote>
+ <p class="attribution"><span class="caps">— Name, Company</span></p>
+</section>
+```
diff --git a/skill/references/components/t4-numbered-stat-strip.md b/skill/references/components/t4-numbered-stat-strip.md
new file mode 100644
index 0000000..e534b42
--- /dev/null
+++ b/skill/references/components/t4-numbered-stat-strip.md
@@ -0,0 +1,14 @@
+### T4 · Numbered stat strip
+A horizontal strip of 3–5 stats (count + qualifier) running across one row. Tabular nums.
+*Use when:* you have multiple complementary metrics that work together.
+*Don't confuse with:* H4 Stat-led hero (which is one focal number, not several).
+
+```html
+<section class="stat-strip tnum">
+ <div><b>2.4M</b><span>users</span></div>
+ <div><b>99.97%</b><span>uptime</span></div>
+ <div><b>14</b><span>regions</span></div>
+</section>
+```
+
+---
diff --git a/skill/references/macrostructures.md b/skill/references/macrostructures.md
index 4811998..1f51c24 100644
--- a/skill/references/macrostructures.md
+++ b/skill/references/macrostructures.md
@@ -22,604 +22,31 @@ Each macrostructure also implies a **nav archetype** (N1–N9) and a **footer ar
---
-## 01 · Bento Grid
-
-Modular blocks of varying sizes laid out as an irregular grid. Each block is a feature, a quote, an image, a stat. Visual rhythm comes from size variation, not card uniformity.
-
-- **Heading:** centered display in a fixed-height hero (not full viewport).
-- **Body:** asymmetric grid — 8–15 blocks of mixed spans (1×1, 2×1, 1×2, 2×2).
-- **Divider:** consistent 12–24 px gap; no rules; the grid itself is the rhythm.
-- **Button:** outlined chip on the hero; tile-internal CTAs as typographic links.
-- **Image:** tightly cropped inside individual blocks; never full-bleed.
-- **Reveal:** none, or a subtle one-shot fade on grid-tile entry.
-
-Reach for it when the brief is "many small things to show", a feature page, a SaaS landing, or anywhere users have multiple equally-valid entry points.
-
-Avoid when the message is a single hero idea — Bento spreads attention; one-idea pages need Marquee or Stat-Led.
-
-Reference: Apple in-page sections, Framer feature pages, Tailwind UI templates.
-
-**Sample opening lines** (imitate the *specificity*, not the wording):
-> *"Tracejam · v0.4 · for SREs. Distributed tracing that explains itself."* — paraphrased from real observability tools
-> *"Resend is the email API for developers. Send transactional and marketing emails at scale."* — resend.com
-> *"The product development system for teams and agents."* — linear.app
-
-```html
-<header class="hero-fixed">…</header>
-<section class="bento">
- <article class="cell span-2x2">…</article> <!-- hero feature -->
- <article class="cell span-1x1">…</article>
- <article class="cell span-2x1">…</article> <!-- wide stat -->
- <article class="cell span-1x2">…</article> <!-- tall image -->
- <article class="cell span-1x1">…</article>
- <article class="cell span-1x1">…</article>
-</section>
-```
-
----
-
-## 02 · Long Document
-
-Reads like a memo, a letter, or a journal entry. No marketing structure. Continuous prose with inline section heads. The page is *literature* about the product.
-
-- **Heading:** inline with body — section heads emerge from the paragraph flow as small caps or bold short phrases.
-- **Body:** single column, generous line-height (1.65+), measure 60–65ch.
-- **Divider:** negative space; the gap is the divider; occasionally a centered ornament for emphasis.
-- **Button:** typographic link inside a paragraph, not a separate block.
-- **Image:** inline, sized to text measure; never full-bleed.
-- **Reveal:** none. The page is just *there*.
-
-Reach for it for case studies, founder posts, mission pages, products whose sale is *philosophical*. The brief is "tell a story", not "list features".
-
-Avoid when there's a single decisive action to take — Long Document hides CTAs, which is wrong for transactional pages.
-
-Reference: Frank Chimero's site, destroytoday.com, long-form Substack essays in product disguise.
-
-**Sample opening lines** (imitate the *specificity*, not the wording):
-> *"Saturday, 6:14 a.m. The dough went in at midnight."* — opens with a time-stamp; the brand introduces itself as a moment in the day
-> *"A monthly art publication featuring contributions by some of the most engaged thinkers working today."* — e-flux.com/journal
-> *"We design everything for everyone."* — pentagram.com — refusal of the verb, treats design as universal practice
-
-```html
-<article class="prose">
- <p class="lede">…</p>
- <p>…</p>
- <h2 class="inline">A small heading.</h2>
- <p>…</p>
- <blockquote>…</blockquote>
- <p>… <a href="">read more →</a> …</p>
-</article>
-```
-
----
-
-## 03 · Marquee Hero
-
-The hero IS the page above the fold. A single bold statement or visual fills the viewport. No subhead, no CTA in fold. Below the fold the page becomes something else (a list, a grid, prose).
-
-- **Heading:** display fills the fold — 8–14 vw type, hugging the viewport edges.
-- **Body:** below-fold becomes a list of work or a single content block; the hero doesn't continue.
-- **Divider:** a thick rule between hero and below-fold, OR a hard colour change.
-- **Button:** none in fold; first CTA arrives below.
-- **Image:** none in fold (typography is the visual), OR a single full-bleed photograph as the fold *background*.
-- **Reveal:** the fold is static; below-fold may sweep in horizontally.
-
-Reach for it when the brand or person *is* the message — designer/director portfolios, indie products with a single declarative voice, any "this is who we are" page.
-
-Avoid for products whose value requires explanation in seconds. Marquee makes the user scroll before they understand.
-
-Reference: 14islands.com, destroytoday.com, many design studio homepages.
-
-**Sample opening lines** (imitate the *specificity*, not the wording):
-> *"Type, set with care."* — Hallmark Specimen — refusal of the verb, treats type as material
-> *"A studio for what's next."* — italic editorial display, names the practice without explaining it
-> *"Design like print: warm, off-register, intentional."* — Hallmark Riso — declarative, three modifiers, full stop
-
-```html
-<section class="marquee">
- <h1 class="display-xxl">A statement.</h1>
-</section>
-<hr class="rule-thick" />
-<section class="below-fold">…</section>
-```
-
----
-
-## 04 · Stat-Led
-
-The hero is a giant number — a metric, a count, a percentage. Everything that follows supports or qualifies it. Data is the narrative.
-
-- **Heading:** numeric display (8–12 rem), tabular figures, small qualifier line below.
-- **Body:** sections each anchored by a supporting stat or chart.
-- **Divider:** hairline rules between stat blocks; tabular-nums everywhere.
-- **Button:** outlined chip aligned beneath the qualifier.
-- **Image:** charts and small data-viz; no photography.
-- **Reveal:** number-tick on the hero figure — counter from 0 to target over ~500 ms.
-
-Reach for it when the brief is "we have proof in numbers" — enterprise/B2B, fundraising platforms, climate or impact pages.
-
-Avoid for products without a defensible single metric. A fake big number is worse than no number.
-
-Reference: Ahrefs, Stripe Sessions stat blocks, climate-impact dashboards, venture firm portfolio pages.
-
-**Sample opening lines** (imitate the *specificity*, not the wording — the number does the work):
-> *"+47% · faster · decide late."* — italicised number, three-word qualifier
-> *"4 seconds. From the alert link to the slow span."* — pairs the number with what it bought
-> *"434 total posts. New CSS you feel like you could use today."* — adam argyle, nerdy.dev — the count grounds the page in real volume
-
-```html
-<section class="stat-hero">
- <div class="figure tnum">99.97<span class="unit">%</span></div>
- <p class="qualifier">uptime across 2026, measured externally.</p>
- <a class="cta-outline">Read the report →</a>
-</section>
-<section class="supporting-stats">…</section>
-```
-
----
-
-## 05 · Workbench
-
-Product screenshots in frames are the primary content. The page is a guided tour of the app in use. Less marketing copy, more "here's what you do with it."
-
-- **Heading:** small, functional — workbench pages don't shout.
-- **Body:** sequence of screenshot blocks, each with a short caption and an inline annotation arrow.
-- **Divider:** the screenshot frame *is* the divider; sections separate by gap and frame.
-- **Button:** sticky-bottom CTA bar after the third screenshot ("Try it →"), once context is built.
-- **Image:** central — browser/device frames around real product captures, with annotation arrows.
-- **Reveal:** type-unmask on captions; screenshots load instantly.
-
-Reach for it for SaaS, developer tools, IDE extensions — anywhere seeing the product in motion is the sale.
-
-Avoid when the product is conceptual or services-led. Workbench needs a UI to show.
-
-Reference: Linear.app, Vercel, Raycast, Arc Browser.
-
-**Sample opening lines** (imitate the *specificity*, not the wording — the page walks the user through):
-> *"$ streampipe parse access.log --filter status=5xx | jq"* — open on a real command, not a marketing claim
-> *"Read anything that emits lines. Files, pipes, sockets, kubectl logs."* — names the inputs, refuses abstraction
-> *"Open the trace, find the span, fix the regression. No glossary required."* — three concrete verbs, then a refusal
-
-```html
-<header class="lite">…</header>
-<section class="screenshot-frame">
- <figure><img src="step-1.png" /><figcaption>Open a project.</figcaption></figure>
-</section>
-<section class="screenshot-frame">…</section>
-<aside class="sticky-cta">Try it free →</aside>
-```
-
----
-
-## 06 · Conversational FAQ
-
-Bold questions, brief answers. The page reads like an honest interview with the product. Often each Q/A is a collapsible accordion.
-
-- **Heading:** each section *is* a question — a short, direct phrase ending in `?`.
-- **Body:** answer in 2–4 short paragraphs immediately below the question.
-- **Divider:** thin rule between Q/A pairs, or zero rule and a paper-colour swap.
-- **Button:** typographic link inside answers ("Read the full policy →"); one outlined CTA at the foot.
-- **Image:** sparse — maybe one diagram per long answer; mostly text.
-- **Reveal:** none on load; accordion expand uses 200 ms `--ease-out` on `grid-template-rows: 0fr → 1fr`.
-
-Reach for it near pricing, for products that meet skepticism, for educational/regulated industries.
-
-Avoid as the *primary* page. FAQ usually pairs with another macrostructure that opens the page.
-
-Reference: many SaaS pricing pages, Casper, Substack help pages.
-
-**Sample opening lines** (imitate the *specificity* — questions are real questions, answers are short and concrete):
-> *"What is this for? — A single-binary CLI for parsing log streams from stdin."* — names the form factor, names the input
-> *"How is this different from X? — It's about time."* — cron.com — answers obliquely, with a phrase that has weight
-> *"Who built this? — Three of us, in Lisbon, since 2014."* — date + place + count, no marketing
-
-```html
-<section class="faq">
- <details>
- <summary><h2>How long does setup take?</h2></summary>
- <div class="answer">…</div>
- </details>
- <details>…</details>
-</section>
-```
-
----
-
-## 07 · Manifesto
-
-Polemical large type. Declaration energy. The page tells the reader what to believe before it tells them what to buy. Often political-poster aesthetic.
-
-- **Heading:** all-caps display tilted slightly (`-2°` to `-4°`), or stacked colour-block highlights on the verb.
-- **Body:** short paragraphs each holding one assertion, large enough to read across the room.
-- **Divider:** bleed-colour blocks between sections; no hairlines.
-- **Button:** oversized solid block, accent colour, set far below the fold.
-- **Image:** none, or a single high-contrast B&W photograph used as a section bleed.
-- **Reveal:** horizontal sweep on section entry.
-
-Reach for it for brand repositioning announcements, mission-led indie products, design-studio beliefs pages.
-
-Avoid for transactional pages. Manifesto sells *agreement*, not action.
-
-Reference: Linear's positioning pages, agency rebrand sites, political campaign landing pages.
-
-**Sample opening lines** (imitate the *specificity* — manifestos commit, they don't hedge):
-> *"WE ARE A STUDIO. WE ARE NOT A PLATFORM."* — Meridian (test 04) — defines by refusal, all caps, a single accent word
-> *"We design products that last twelve years. We do not design products that need replacing every two."* — concrete number, paired declaration
-> *"Lightness above weightiness, elevate everyone you encounter."* — craigmod.com — one-line principle, no explanation needed
-
-```html
-<section class="manifesto bleed-ink">
- <h1 class="caps display-xxl">WE BELIEVE <em class="block-accent">DESIGN</em> IS SLOW.</h1>
-</section>
-<section class="bleed-paper">
- <p class="claim">It costs less than the rework you'll do without it.</p>
-</section>
-```
-
----
-
-## 08 · Photographic
-
-A single huge image dominates each fold. Text is small annotation, not headline. The design says *look* before it says *read*.
-
-- **Heading:** small caption near a corner of the image; never centered display.
-- **Body:** full-bleed image bands alternating with narrow text bands.
-- **Divider:** the image edge IS the divider; no rules.
-- **Button:** typographic link tucked under the caption.
-- **Image:** the whole point — full-bleed, edge to edge, often a single photo per fold.
-- **Reveal:** no spatial motion; let the photographs do the work.
-
-Reach for it for fashion, hospitality, photography portfolios, lifestyle e-commerce, any brand whose product is a *feeling*.
-
-Avoid without real photography. AI-generated stock undoes the macrostructure.
-
-Reference: Aimé Leon Dore, Mr Porter editorial, Stüssy lookbooks.
-
-**Sample opening lines** (imitate the *specificity* — captions for photographs are dates, places, plate numbers — not marketing):
-> *"Plate 47 · scored before the proof."* — Maple Street Bread (test 03) — a number, a moment in the process
-> *"Spring, 2026."* — Atelier-style — two words, full stop
-> *"From the working archive."* — gives the photograph provenance without explaining it
-
-```html
-<section class="photo-fold">
- <img class="bleed" src="hero.jpg" />
- <p class="caption">Spring, 2026.</p>
-</section>
-<section class="text-fold">
- <p class="lede">…</p>
-</section>
-<section class="photo-fold">…</section>
-```
-
----
-
-## 09 · Quote-Led
-
-The hero is a pull-quote with attribution. The headline is borrowed credibility, not the brand's voice. The page leads with social proof.
-
-- **Heading:** italic display setting a customer's quote (36–60 px), with attribution below in small caps.
-- **Body:** continues with additional testimonials, case studies, or a quiet feature list.
-- **Divider:** centered quote-mark glyph or an em-rule between testimonials.
-- **Button:** typographic link beneath the attribution ("Read the full case study →").
-- **Image:** small avatar or company logo by the attribution; otherwise none.
-- **Reveal:** none in fold; below-fold may stagger.
-
-Reach for it for B2B products with strong customer voices, agency case-study pages, fundraising sites, anywhere "people like me use this" is the unlock.
-
-Avoid for new products without real testimonials. Fake quotes destroy trust on inspection.
-
-Reference: many B2B SaaS landings, agency homepages, university development pages.
-
-**Sample opening lines** (imitate the *specificity* — quote-led pages let someone else say it, then attribute):
-> *"I started listening on a long bus ride. By the third episode I'd missed my stop, and I didn't mind."* — Tide (test 01) — story-shaped, attributed to a listener
-> *"Restraint, repeated, becomes a signature."* — Hallmark Atelier — short, philosophical, signed by the studio
-> *"It told me the span that regressed, the deploy that caused it, and the engineer to ask. We rolled back in eight minutes."* — Tracejam-style — names the outcome with a number
-
-```html
-<section class="quote-hero">
- <blockquote class="display-italic">"…"</blockquote>
- <p class="attribution">— Name, Title, Company</p>
- <a class="link">Read the case →</a>
-</section>
-<section class="more-quotes">…</section>
-```
-
----
-
-## 10 · Specimen *(no longer the default)*
-
-Numbered left-margin labels, huge serif display, asymmetric column spans, hairline rules, typographic-only CTA, generous whitespace. Editorial / type-foundry energy.
-
-- **Heading:** left-margin number + label (`01 — HELLO.`) beside a large serif phrase.
-- **Body:** asymmetric spans — narrow label column / wide content column.
-- **Divider:** hairline rules between sections.
-- **Button:** typographic link with arrow ("Open your studio →"); no box, no fill.
-- **Image:** none, or a hand-drawn SVG accent in the wide left margin.
-- **Reveal:** fade-up stagger on first load.
-
-Reach for it ONLY when the brief is explicitly editorial, type-foundry, journal, or "specimen sheet". Otherwise pick something else.
-
-**Banned as a default.** If the brief is vague and you've defaulted here, restart.
-
-Reference: type foundry homepages (Klim, Pangram Pangram, Production Type), some editorial portfolios.
-
-**Sample opening lines** (imitate the *specificity* — Specimen openings are foundry-voice, treating type as material culture):
-> *"A thing well made."* — klim.co.nz — refusal of the verb, treats design as material
-> *"Type, set with care."* — Hallmark Specimen — three words, a colon implied
-> *"Creative direction, design and type for culture since 2003."* — apracticeforeverydaylife.com — date-anchored, names verticals
-
-```html
-<header class="specimen">
- <p class="num-label">01 — HELLO.</p>
- <h1 class="serif-xxl">A quiet <em>instrument.</em></h1>
- <p class="lede narrow">…</p>
- <a class="link">Open your studio →</a>
-</header>
-```
-
----
-
-## 11 · Catalogue
-
-Uniform grid of variations of the same thing — typefaces, colour palettes, product SKUs. The page is a visual index of inventory.
-
-- **Heading:** brand mark + tagline only; no big display.
-- **Body:** grid of identical-sized cards (3–5 per row), each one variant of the core product.
-- **Divider:** hairline rules between rows; sometimes a category label band.
-- **Button:** card-internal link to detail page; no global CTA.
-- **Image:** specimen thumbnail per card, or a swatch.
-- **Reveal:** none.
-
-Reach for it for foundries, palette generators, font shops, colour systems, capsule collections.
-
-Avoid for narrative brands. Catalogue treats every item as equal — wrong for products with hierarchy.
-
-Reference: Klim Type Foundry, Pangram Pangram, Coolors palettes.
-
-**Sample opening lines** (imitate the *specificity* — Catalogue openings are inventory headers, dated, with a count):
-> *"Today's loaves."* — Maple Street Bread (test 03) — two words, ownership of the day
-> *"Five collections, in store now."* — names the count and the where
-> *"Thirty-eight items · Spring 2026 · all hand-stitched."* — count, date, qualifier; no adjectives
-
----
-
-## 12 · Letter
-
-First-person, written, intimate. Opens with a greeting ("Dear friend,"). No buttons in the fold. Reads as a personal note from the founder.
-
-- **Heading:** salutation in serif italic ("Dear reader,"), 1.5–2× body size.
-- **Body:** prose, single column, narrow measure (50ch), as if typed.
-- **Divider:** paragraph spacing only, occasional `* * *` separator.
-- **Button:** sign-off link at the foot ("p.s. join us if you'd like →").
-- **Image:** maybe one signature scan, or a quiet inline photograph.
-- **Reveal:** none.
-
-Reach for it for personal brands, indie founder announcements, sabbatical or pivot pages, donation appeals.
-
-Avoid for transactional commerce. Letter is intimate; commerce is functional.
-
-Reference: Frank Chimero's site, founder farewell posts, indie newsletter front pages.
-
-**Sample opening lines** (imitate the *specificity* — Letter openings are first-person greetings, dated, with a place if relevant):
-> *"Hello, I'm Anya."* — Anya (test 06) — single line, name, full stop
-> *"Saturday, 6:14 a.m. The dough went in at midnight."* — opens on a moment, then explains it
-> *"Hey there. This page is soft because the surface should be soft."* — Hallmark Plume — colloquial open + a principle
-
----
-
-## 13 · Index-First
-
-The page IS a list of links. No hero image, no narrative flow. Pure navigation as design.
-
-- **Heading:** one short paragraph at the top introducing the index, no display type.
-- **Body:** vertical list of categorised links; sometimes a sidebar of filters.
-- **Divider:** hairline rules between rows; or zero rules with paper-colour bands.
-- **Button:** the links themselves are the buttons.
-- **Image:** none, or tiny favicons by each entry.
-- **Reveal:** none.
-
-Reach for it for documentation hubs, knowledge bases, archive front pages, design system entries, link-in-bio pages with substance.
-
-Avoid for marketing pages. Index-First is for browsing audiences; selling needs structure.
-
-Reference: Are.na's homepage feel, archive sites, documentation indices.
-
-**Sample opening lines** (imitate the *specificity* — Index-First openings are headers for what's below, sometimes nothing more than a label):
-> *"Selected work · 2018 — 2026."* — date range, no preamble
-> *"Things Become Other Things · Lightness above weightiness."* — craigmod.com — two phrases joined by a divider
-> *"Writer + Photographer."* — craigmod.com — three words, summarises the whole site
-
----
-
-## 14 · Narrative Workflow
-
-Numbered stages tell the story of how the user uses the product over time. Each section is a phase (1.0 → 2.0 → 3.0 → 4.0). The page is a process timeline.
-
-- **Heading:** large numbered stage labels (`1.0 INTAKE`, `2.0 PLAN`).
-- **Body:** each stage has a short explanation and a small product visual.
-- **Divider:** thick numbered rule between stages.
-- **Button:** stage-internal links; one global "Start at stage 1 →" at the foot.
-- **Image:** small product capture per stage, often annotated.
-- **Reveal:** sweep horizontal as stages enter the viewport.
-
-Reach for it for products with explicit workflows — project management, design-to-dev pipelines, writing tools.
-
-Avoid for tools that work in *one* moment. Narrative Workflow needs a real sequence.
-
-Reference: Linear's how-it-works pages, some Figma marketing pages.
-
-**Sample opening lines** (imitate the *specificity* — Narrative Workflow openings are stage labels: numbered, declarative, in process language):
-> *"01 · sourdough overnight · 02 · score at dawn · 03 · pull at seven."* — three numbered stages, no marketing
-> *"1.0 · parse · 2.0 · filter · 3.0 · route."* — Streampipe (test 02) — versioned numbers, three concrete verbs
-> *"I. We design products that last twelve years. II. A material is sustainable when someone, somewhere, can repair it."* — Meridian — Roman numerals + declarative
-
----
-
-## 15 · Split Studio
-
-Diptych. Every major content block divides the screen — text on one side, proof on the other. The pairing alternates direction down the page.
-
-- **Heading:** half-screen wide; the other half holds a screenshot or a quote.
-- **Body:** alternating left-text/right-image and right-text/left-image modules.
-- **Divider:** a clear gutter between halves; no rules.
-- **Button:** outlined chip below the text half.
-- **Image:** anchored to the opposite half from the text in each row.
-- **Reveal:** opposite halves cross-fade in slightly staggered.
-
-Reach for it for SaaS feature pages, dev tools that pair explanation with code, anything where every claim wants a visual proof.
-
-Avoid for narrative or photographic brands. Split halves the attention; some pages need single focus.
-
-Reference: Vercel feature pages, Stripe Sessions program pages, many dev-tool homepages.
-
-**Sample opening lines** (imitate the *specificity* — Split Studio openings pair a positioning statement with a proof column):
-> *"A studio for what's next."* — italic display + selected-work column on the right
-> *"Print discipline, on screen."* — Hallmark Newsprint — two-phrase headline, masthead-style
-> *"We design and build distinctive products for ambitious teams."* — names the verb (design and build), names the audience
-
----
-
-## 16 · Feature Stack
-
-Sticky left pane (label / description) + scroll-synced right pane (screenshots cycling through related details). Cinematic pacing.
-
-- **Heading:** held inside the sticky pane; persists while content cycles beside it.
-- **Body:** two columns — left sticky, right scrolling; the right pane plays through 3–6 detail screens per section.
-- **Divider:** section bands; the sticky pane re-anchors per section.
-- **Button:** in the sticky pane, set when the user reaches the section's detail count.
-- **Image:** the scrolling-right column is mostly imagery.
-- **Reveal:** none of the spatial-fade kind; the sticky/scroll IS the motion.
-
-Reach for it for premium products, complex feature stories, anything where you want to control pacing as the user scrolls.
-
-Avoid on mobile-first audiences without strong fallback. Sticky+scroll-sync is rough on small screens.
-
-Reference: Apple product pages, some Stripe Sessions pages, Read.cv onboarding.
-
-**Sample opening lines** (imitate the *specificity* — Feature Stack openings pin a single statement and then walk the user through):
-> *"Plan, build, ship."* — three verbs, three sticky panes
-> *"Read anything that emits lines."* — Streampipe (test 02) — names what's possible, then walks through it
-> *"From stdin, through the pipe, into your dashboard."* — names the data path, then explains each step
-
----
-
-## 17 · Type Specimen
-
-The typeface IS the design. Foundry homepage or design-system marketing where a custom typeface is the brand's proof.
-
-- **Heading:** the typeface set at multiple sizes, demonstrating what it does.
-- **Body:** progressive demonstration — display size, body size, italic, language coverage, OpenType features.
-- **Divider:** centred caption labels between specimens.
-- **Button:** outlined "Buy" or "Use it" at the foot.
-- **Image:** none — typography is the imagery.
-- **Reveal:** type-unmask on first paint of each specimen block.
-
-Reach for it for type foundries, design systems where a custom face is the differentiator, font product pages.
-
-Avoid when the brand uses an off-the-shelf face. Type Specimen needs something distinctive to celebrate.
-
-Reference: Klim Type Foundry, Pangram Pangram, Geist Pixel announcement pages.
-
-**Sample opening lines** (imitate the *specificity* — Type Specimen openings are foundry-voice: name the typeface, the weights, the use):
-> *"Reckless Display, set in 96 pt."* — names the face and the size, nothing else
-> *"Eight weights. Three optical sizes. One good italic."* — counts the system in three short phrases
-> *"A type system for editorial."* — refusal of the verb, single noun phrase
-
----
-
-## 18 · Portfolio Grid
-
-Filterable cards of projects. Studio or designer homepages where the work is the product.
-
-- **Heading:** short tagline above the grid; no display.
-- **Body:** responsive grid of project cards, all same size or with subtle size variation.
-- **Divider:** filter bar above the grid; no internal rules.
-- **Button:** card-internal "View case study"; no global CTA.
-- **Image:** thumbnail per card.
-- **Reveal:** card-fade on filter change.
-
-Reach for it for design studios, agencies, photographer portfolios, any creative business where work is the pitch.
-
-Avoid for products. Portfolio Grid is service-business shape.
-
-Reference: Pentagram, 14islands, Locomotive, Bureau Borsche.
-
-**Sample opening lines** (imitate the *specificity* — Portfolio Grid openings name the volume and the era):
-> *"Selected work · 2018 — 2026."* — date range, two characters of meta
-> *"Twelve projects, six clients, two countries."* — three counts, no adjective
-> *"Work, indexed by year."* — five-word labels, the index is the whole site
-
----
-
-## 19 · Map / Diagram
-
-A single large spatial diagram organises the page — flowchart, floor plan, network graph, system map. Information is laid out *spatially*, not linearly.
-
-- **Heading:** a small orientation phrase above or beside the map.
-- **Body:** the map itself; nodes and edges; a legend somewhere.
-- **Divider:** the diagram has no internal sections — it's one composition.
-- **Button:** node-internal links; one outlined CTA below the map.
-- **Image:** the map IS the image; SVG with interactive hovers.
-- **Reveal:** node-by-node ink-on as the user enters viewport (cap to 5 nodes).
-
-Reach for it for system overviews, ecosystem maps, process diagrams, organisation charts.
-
-Avoid as a substitute for narrative. Some stories shouldn't be read spatially.
-
-Reference: process visualisation sites, ecosystem maps, knowledge-graph products.
-
-**Sample opening lines** (imitate the *specificity* — Map / Diagram openings name the path or the territory):
-> *"Browser → API → Database. Where Tracejam fits."* — names the layers, names the position
-> *"From stdin, through the pipe, into your dashboard."* — labels the spatial flow on the page below
-> *"Three tiers · two regions · one ledger."* — counts the system, geographic + structural
-
----
-
-## 20 · Ecosystem Index
-
-Multiple discovery surfaces — featured / latest / by category / by people. The platform's value is emergence and browsing, not declaration.
-
-- **Heading:** brief positioning paragraph; no display.
-- **Body:** several horizontal rails or grids — each surfacing a different cut of the platform's content.
-- **Divider:** rail-titled bands.
-- **Button:** "See more →" at each rail's edge; rarely a global CTA.
-- **Image:** thumbnails everywhere; the page is dense imagery.
-- **Reveal:** none.
-
-Reach for it for community platforms, content marketplaces, design-asset stores, any UGC/curated catalogue front page.
-
-Avoid for single-product pages. Ecosystem needs multiple things to surface.
-
-Reference: Are.na, Figma Community, Behance.
-
-**Sample opening lines** (imitate the *specificity* — Ecosystem Index openings are surface labels, dated, with a count):
-> *"Featured · Latest · By category."* — three discovery surfaces named, divided
-> *"What's on this week · Editor's pick · The whole catalogue."* — names cadence, curation, breadth
-> *"A toolkit for assembling new worlds from the scraps of the old."* — are.na — second-position copy that breaks template
-
----
-
-## 21 · Component Playground
-
-Interactive code-and-preview blocks are the page's primary content. Each block previews a thing and shows how to copy-paste it.
-
-- **Heading:** category labels (`Buttons`, `Forms`, `Cards`, `Layouts`).
-- **Body:** alternating preview-and-code blocks, often with a tab to switch frameworks.
-- **Divider:** category bands; horizontal rules between examples.
-- **Button:** "Copy" button on every code block (silent success).
-- **Image:** none — the previews ARE the imagery.
-- **Reveal:** none.
-
-Reach for it for design systems, component libraries, code-snippet sites, framework documentation.
-
-Avoid for marketing pages. Playground is utility, not pitch.
-
-Reference: shadcn/ui, Tailwind UI, Once UI, MUI demos, Framer Motion examples.
-
-**Sample opening lines** (imitate the *specificity* — Component Playground openings are tangible: open on a real example, not a claim):
-> *"Try it inline. Then take it home."* — two short imperatives
-> *"Every example is editable. Every output is real."* — pairs claim with proof
-> *"From `npm install` to your first chart in eight lines."* — names the step count, makes a concrete promise
+## The 21 macrostructures — index
+
+**Pick one. Then read ONLY that one file** from `references/macrostructures/`. Do not load the whole catalogue. Slugs are stable; the diversification rule reads the `<name>` from the `/* Hallmark · macrostructure: <name> · ... */` stamp.
+
+- **01 · Bento Grid** — Modular blocks of varying sizes laid out as an irregular grid. Each block is a feature, a quote, an image, a stat. Visual rhythm comes from size variation, not card uniformity. [`macrostructures/01-bento-grid.md`](macrostructures/01-bento-grid.md)
+- **02 · Long Document** — Reads like a memo, a letter, or a journal entry. No marketing structure. Continuous prose with inline section heads. The page is *literature* about the product. [`macrostructures/02-long-document.md`](macrostructures/02-long-document.md)
+- **03 · Marquee Hero** — The hero IS the page above the fold. A single bold statement or visual fills the viewport. No subhead, no CTA in fold. Below the fold the page becomes something else (a list, a grid, prose). [`macrostructures/03-marquee-hero.md`](macrostructures/03-marquee-hero.md)
+- **04 · Stat-Led** — The hero is a giant number — a metric, a count, a percentage. Everything that follows supports or qualifies it. Data is the narrative. [`macrostructures/04-stat-led.md`](macrostructures/04-stat-led.md)
+- **05 · Workbench** — Product screenshots in frames are the primary content. The page is a guided tour of the app in use. Less marketing copy, more "here's what you do with it." [`macrostructures/05-workbench.md`](macrostructures/05-workbench.md)
+- **06 · Conversational FAQ** — Bold questions, brief answers. The page reads like an honest interview with the product. Often each Q/A is a collapsible accordion. [`macrostructures/06-conversational-faq.md`](macrostructures/06-conversational-faq.md)
+- **07 · Manifesto** — Polemical large type. Declaration energy. The page tells the reader what to believe before it tells them what to buy. Often political-poster aesthetic. [`macrostructures/07-manifesto.md`](macrostructures/07-manifesto.md)
+- **08 · Photographic** — A single huge image dominates each fold. Text is small annotation, not headline. The design says *look* before it says *read*. [`macrostructures/08-photographic.md`](macrostructures/08-photographic.md)
+- **09 · Quote-Led** — The hero is a pull-quote with attribution. The headline is borrowed credibility, not the brand's voice. The page leads with social proof. [`macrostructures/09-quote-led.md`](macrostructures/09-quote-led.md)
+- **10 · Specimen** — Numbered left-margin labels, huge serif display, asymmetric column spans, hairline rules, typographic-only CTA, generous whitespace. Editorial / type-foundry energy. [`macrostructures/10-specimen.md`](macrostructures/10-specimen.md)
+- **11 · Catalogue** — Uniform grid of variations of the same thing — typefaces, colour palettes, product SKUs. The page is a visual index of inventory. [`macrostructures/11-catalogue.md`](macrostructures/11-catalogue.md)
+- **12 · Letter** — First-person, written, intimate. Opens with a greeting ("Dear friend,"). No buttons in the fold. Reads as a personal note from the founder. [`macrostructures/12-letter.md`](macrostructures/12-letter.md)
+- **13 · Index-First** — The page IS a list of links. No hero image, no narrative flow. Pure navigation as design. [`macrostructures/13-index-first.md`](macrostructures/13-index-first.md)
+- **14 · Narrative Workflow** — Numbered stages tell the story of how the user uses the product over time. Each section is a phase (1.0 → 2.0 → 3.0 → 4.0). The page is a process timeline. [`macrostructures/14-narrative-workflow.md`](macrostructures/14-narrative-workflow.md)
+- **15 · Split Studio** — Diptych. Every major content block divides the screen — text on one side, proof on the other. The pairing alternates direction down the page. [`macrostructures/15-split-studio.md`](macrostructures/15-split-studio.md)
+- **16 · Feature Stack** — Sticky left pane (label / description) + scroll-synced right pane (screenshots cycling through related details). Cinematic pacing. [`macrostructures/16-feature-stack.md`](macrostructures/16-feature-stack.md)
+- **17 · Type Specimen** — The typeface IS the design. Foundry homepage or design-system marketing where a custom typeface is the brand's proof. [`macrostructures/17-type-specimen.md`](macrostructures/17-type-specimen.md)
+- **18 · Portfolio Grid** — Filterable cards of projects. Studio or designer homepages where the work is the product. [`macrostructures/18-portfolio-grid.md`](macrostructures/18-portfolio-grid.md)
+- **19 · Map / Diagram** — A single large spatial diagram organises the page — flowchart, floor plan, network graph, system map. Information is laid out *spatially*, not linearly. [`macrostructures/19-map-diagram.md`](macrostructures/19-map-diagram.md)
+- **20 · Ecosystem Index** — Multiple discovery surfaces — featured / latest / by category / by people. The platform's value is emergence and browsing, not declaration. [`macrostructures/20-ecosystem-index.md`](macrostructures/20-ecosystem-index.md)
+- **21 · Component Playground** — Interactive code-and-preview blocks are the page's primary content. Each block previews a thing and shows how to copy-paste it. [`macrostructures/21-component-playground.md`](macrostructures/21-component-playground.md)
---
diff --git a/skill/references/macrostructures/01-bento-grid.md b/skill/references/macrostructures/01-bento-grid.md
new file mode 100644
index 0000000..ab6f035
--- /dev/null
+++ b/skill/references/macrostructures/01-bento-grid.md
@@ -0,0 +1,35 @@
+## 01 · Bento Grid
+
+Modular blocks of varying sizes laid out as an irregular grid. Each block is a feature, a quote, an image, a stat. Visual rhythm comes from size variation, not card uniformity.
+
+- **Heading:** centered display in a fixed-height hero (not full viewport).
+- **Body:** asymmetric grid — 8–15 blocks of mixed spans (1×1, 2×1, 1×2, 2×2).
+- **Divider:** consistent 12–24 px gap; no rules; the grid itself is the rhythm.
+- **Button:** outlined chip on the hero; tile-internal CTAs as typographic links.
+- **Image:** tightly cropped inside individual blocks; never full-bleed.
+- **Reveal:** none, or a subtle one-shot fade on grid-tile entry.
+
+Reach for it when the brief is "many small things to show", a feature page, a SaaS landing, or anywhere users have multiple equally-valid entry points.
+
+Avoid when the message is a single hero idea — Bento spreads attention; one-idea pages need Marquee or Stat-Led.
+
+Reference: Apple in-page sections, Framer feature pages, Tailwind UI templates.
+
+**Sample opening lines** (imitate the *specificity*, not the wording):
+> *"Tracejam · v0.4 · for SREs. Distributed tracing that explains itself."* — paraphrased from real observability tools
+> *"Resend is the email API for developers. Send transactional and marketing emails at scale."* — resend.com
+> *"The product development system for teams and agents."* — linear.app
+
+```html
+<header class="hero-fixed">…</header>
+<section class="bento">
+ <article class="cell span-2x2">…</article> <!-- hero feature -->
+ <article class="cell span-1x1">…</article>
+ <article class="cell span-2x1">…</article> <!-- wide stat -->
+ <article class="cell span-1x2">…</article> <!-- tall image -->
+ <article class="cell span-1x1">…</article>
+ <article class="cell span-1x1">…</article>
+</section>
+```
+
+---
diff --git a/skill/references/macrostructures/02-long-document.md b/skill/references/macrostructures/02-long-document.md
new file mode 100644
index 0000000..225ac77
--- /dev/null
+++ b/skill/references/macrostructures/02-long-document.md
@@ -0,0 +1,34 @@
+## 02 · Long Document
+
+Reads like a memo, a letter, or a journal entry. No marketing structure. Continuous prose with inline section heads. The page is *literature* about the product.
+
+- **Heading:** inline with body — section heads emerge from the paragraph flow as small caps or bold short phrases.
+- **Body:** single column, generous line-height (1.65+), measure 60–65ch.
+- **Divider:** negative space; the gap is the divider; occasionally a centered ornament for emphasis.
+- **Button:** typographic link inside a paragraph, not a separate block.
+- **Image:** inline, sized to text measure; never full-bleed.
+- **Reveal:** none. The page is just *there*.
+
+Reach for it for case studies, founder posts, mission pages, products whose sale is *philosophical*. The brief is "tell a story", not "list features".
+
+Avoid when there's a single decisive action to take — Long Document hides CTAs, which is wrong for transactional pages.
+
+Reference: Frank Chimero's site, destroytoday.com, long-form Substack essays in product disguise.
+
+**Sample opening lines** (imitate the *specificity*, not the wording):
+> *"Saturday, 6:14 a.m. The dough went in at midnight."* — opens with a time-stamp; the brand introduces itself as a moment in the day
+> *"A monthly art publication featuring contributions by some of the most engaged thinkers working today."* — e-flux.com/journal
+> *"We design everything for everyone."* — pentagram.com — refusal of the verb, treats design as universal practice
+
+```html
+<article class="prose">
+ <p class="lede">…</p>
+ <p>…</p>
+ <h2 class="inline">A small heading.</h2>
+ <p>…</p>
+ <blockquote>…</blockquote>
+ <p>… <a href="">read more →</a> …</p>
+</article>
+```
+
+---
diff --git a/skill/references/macrostructures/03-marquee-hero.md b/skill/references/macrostructures/03-marquee-hero.md
new file mode 100644
index 0000000..b88f729
--- /dev/null
+++ b/skill/references/macrostructures/03-marquee-hero.md
@@ -0,0 +1,31 @@
+## 03 · Marquee Hero
+
+The hero IS the page above the fold. A single bold statement or visual fills the viewport. No subhead, no CTA in fold. Below the fold the page becomes something else (a list, a grid, prose).
+
+- **Heading:** display fills the fold — 8–14 vw type, hugging the viewport edges.
+- **Body:** below-fold becomes a list of work or a single content block; the hero doesn't continue.
+- **Divider:** a thick rule between hero and below-fold, OR a hard colour change.
+- **Button:** none in fold; first CTA arrives below.
+- **Image:** none in fold (typography is the visual), OR a single full-bleed photograph as the fold *background*.
+- **Reveal:** the fold is static; below-fold may sweep in horizontally.
+
+Reach for it when the brand or person *is* the message — designer/director portfolios, indie products with a single declarative voice, any "this is who we are" page.
+
+Avoid for products whose value requires explanation in seconds. Marquee makes the user scroll before they understand.
+
+Reference: 14islands.com, destroytoday.com, many design studio homepages.
+
+**Sample opening lines** (imitate the *specificity*, not the wording):
+> *"Type, set with care."* — Hallmark Specimen — refusal of the verb, treats type as material
+> *"A studio for what's next."* — italic editorial display, names the practice without explaining it
+> *"Design like print: warm, off-register, intentional."* — Hallmark Riso — declarative, three modifiers, full stop
+
+```html
+<section class="marquee">
+ <h1 class="display-xxl">A statement.</h1>
+</section>
+<hr class="rule-thick" />
+<section class="below-fold">…</section>
+```
+
+---
diff --git a/skill/references/macrostructures/04-stat-led.md b/skill/references/macrostructures/04-stat-led.md
new file mode 100644
index 0000000..b2a7501
--- /dev/null
+++ b/skill/references/macrostructures/04-stat-led.md
@@ -0,0 +1,32 @@
+## 04 · Stat-Led
+
+The hero is a giant number — a metric, a count, a percentage. Everything that follows supports or qualifies it. Data is the narrative.
+
+- **Heading:** numeric display (8–12 rem), tabular figures, small qualifier line below.
+- **Body:** sections each anchored by a supporting stat or chart.
+- **Divider:** hairline rules between stat blocks; tabular-nums everywhere.
+- **Button:** outlined chip aligned beneath the qualifier.
+- **Image:** charts and small data-viz; no photography.
+- **Reveal:** number-tick on the hero figure — counter from 0 to target over ~500 ms.
+
+Reach for it when the brief is "we have proof in numbers" — enterprise/B2B, fundraising platforms, climate or impact pages.
+
+Avoid for products without a defensible single metric. A fake big number is worse than no number.
+
+Reference: Ahrefs, Stripe Sessions stat blocks, climate-impact dashboards, venture firm portfolio pages.
+
+**Sample opening lines** (imitate the *specificity*, not the wording — the number does the work):
+> *"+47% · faster · decide late."* — italicised number, three-word qualifier
+> *"4 seconds. From the alert link to the slow span."* — pairs the number with what it bought
+> *"434 total posts. New CSS you feel like you could use today."* — adam argyle, nerdy.dev — the count grounds the page in real volume
+
+```html
+<section class="stat-hero">
+ <div class="figure tnum">99.97<span class="unit">%</span></div>
+ <p class="qualifier">uptime across 2026, measured externally.</p>
+ <a class="cta-outline">Read the report →</a>
+</section>
+<section class="supporting-stats">…</section>
+```
+
+---
diff --git a/skill/references/macrostructures/05-workbench.md b/skill/references/macrostructures/05-workbench.md
new file mode 100644
index 0000000..1e14ed6
--- /dev/null
+++ b/skill/references/macrostructures/05-workbench.md
@@ -0,0 +1,32 @@
+## 05 · Workbench
+
+Product screenshots in frames are the primary content. The page is a guided tour of the app in use. Less marketing copy, more "here's what you do with it."
+
+- **Heading:** small, functional — workbench pages don't shout.
+- **Body:** sequence of screenshot blocks, each with a short caption and an inline annotation arrow.
+- **Divider:** the screenshot frame *is* the divider; sections separate by gap and frame.
+- **Button:** sticky-bottom CTA bar after the third screenshot ("Try it →"), once context is built.
+- **Image:** central — browser/device frames around real product captures, with annotation arrows.
+- **Reveal:** type-unmask on captions; screenshots load instantly.
+
+Reach for it for SaaS, developer tools, IDE extensions — anywhere seeing the product in motion is the sale.
+
+Avoid when the product is conceptual or services-led. Workbench needs a UI to show.
+
+Reference: Linear.app, Vercel, Raycast, Arc Browser.
+
+**Sample opening lines** (imitate the *specificity*, not the wording — the page walks the user through):
+> *"$ streampipe parse access.log --filter status=5xx | jq"* — open on a real command, not a marketing claim
+> *"Read anything that emits lines. Files, pipes, sockets, kubectl logs."* — names the inputs, refuses abstraction
+> *"Open the trace, find the span, fix the regression. No glossary required."* — three concrete verbs, then a refusal
+
+```html
+<header class="lite">…</header>
+<section class="screenshot-frame">
+ <figure><img src="step-1.png" /><figcaption>Open a project.</figcaption></figure>
+</section>
+<section class="screenshot-frame">…</section>
+<aside class="sticky-cta">Try it free →</aside>
+```
+
+---
diff --git a/skill/references/macrostructures/06-conversational-faq.md b/skill/references/macrostructures/06-conversational-faq.md
new file mode 100644
index 0000000..8ee3437
--- /dev/null
+++ b/skill/references/macrostructures/06-conversational-faq.md
@@ -0,0 +1,33 @@
+## 06 · Conversational FAQ
+
+Bold questions, brief answers. The page reads like an honest interview with the product. Often each Q/A is a collapsible accordion.
+
+- **Heading:** each section *is* a question — a short, direct phrase ending in `?`.
+- **Body:** answer in 2–4 short paragraphs immediately below the question.
+- **Divider:** thin rule between Q/A pairs, or zero rule and a paper-colour swap.
+- **Button:** typographic link inside answers ("Read the full policy →"); one outlined CTA at the foot.
+- **Image:** sparse — maybe one diagram per long answer; mostly text.
+- **Reveal:** none on load; accordion expand uses 200 ms `--ease-out` on `grid-template-rows: 0fr → 1fr`.
+
+Reach for it near pricing, for products that meet skepticism, for educational/regulated industries.
+
+Avoid as the *primary* page. FAQ usually pairs with another macrostructure that opens the page.
+
+Reference: many SaaS pricing pages, Casper, Substack help pages.
+
+**Sample opening lines** (imitate the *specificity* — questions are real questions, answers are short and concrete):
+> *"What is this for? — A single-binary CLI for parsing log streams from stdin."* — names the form factor, names the input
+> *"How is this different from X? — It's about time."* — cron.com — answers obliquely, with a phrase that has weight
+> *"Who built this? — Three of us, in Lisbon, since 2014."* — date + place + count, no marketing
+
+```html
+<section class="faq">
+ <details>
+ <summary><h2>How long does setup take?</h2></summary>
+ <div class="answer">…</div>
+ </details>
+ <details>…</details>
+</section>
+```
+
+---
diff --git a/skill/references/macrostructures/07-manifesto.md b/skill/references/macrostructures/07-manifesto.md
new file mode 100644
index 0000000..0b89da3
--- /dev/null
+++ b/skill/references/macrostructures/07-manifesto.md
@@ -0,0 +1,32 @@
+## 07 · Manifesto
+
+Polemical large type. Declaration energy. The page tells the reader what to believe before it tells them what to buy. Often political-poster aesthetic.
+
+- **Heading:** all-caps display tilted slightly (`-2°` to `-4°`), or stacked colour-block highlights on the verb.
+- **Body:** short paragraphs each holding one assertion, large enough to read across the room.
+- **Divider:** bleed-colour blocks between sections; no hairlines.
+- **Button:** oversized solid block, accent colour, set far below the fold.
+- **Image:** none, or a single high-contrast B&W photograph used as a section bleed.
+- **Reveal:** horizontal sweep on section entry.
+
+Reach for it for brand repositioning announcements, mission-led indie products, design-studio beliefs pages.
+
+Avoid for transactional pages. Manifesto sells *agreement*, not action.
+
+Reference: Linear's positioning pages, agency rebrand sites, political campaign landing pages.
+
+**Sample opening lines** (imitate the *specificity* — manifestos commit, they don't hedge):
+> *"WE ARE A STUDIO. WE ARE NOT A PLATFORM."* — Meridian (test 04) — defines by refusal, all caps, a single accent word
+> *"We design products that last twelve years. We do not design products that need replacing every two."* — concrete number, paired declaration
+> *"Lightness above weightiness, elevate everyone you encounter."* — craigmod.com — one-line principle, no explanation needed
+
+```html
+<section class="manifesto bleed-ink">
+ <h1 class="caps display-xxl">WE BELIEVE <em class="block-accent">DESIGN</em> IS SLOW.</h1>
+</section>
+<section class="bleed-paper">
+ <p class="claim">It costs less than the rework you'll do without it.</p>
+</section>
+```
+
+---
diff --git a/skill/references/macrostructures/08-photographic.md b/skill/references/macrostructures/08-photographic.md
new file mode 100644
index 0000000..17ba98a
--- /dev/null
+++ b/skill/references/macrostructures/08-photographic.md
@@ -0,0 +1,34 @@
+## 08 · Photographic
+
+A single huge image dominates each fold. Text is small annotation, not headline. The design says *look* before it says *read*.
+
+- **Heading:** small caption near a corner of the image; never centered display.
+- **Body:** full-bleed image bands alternating with narrow text bands.
+- **Divider:** the image edge IS the divider; no rules.
+- **Button:** typographic link tucked under the caption.
+- **Image:** the whole point — full-bleed, edge to edge, often a single photo per fold.
+- **Reveal:** no spatial motion; let the photographs do the work.
+
+Reach for it for fashion, hospitality, photography portfolios, lifestyle e-commerce, any brand whose product is a *feeling*.
+
+Avoid without real photography. AI-generated stock undoes the macrostructure.
+
+Reference: Aimé Leon Dore, Mr Porter editorial, Stüssy lookbooks.
+
+**Sample opening lines** (imitate the *specificity* — captions for photographs are dates, places, plate numbers — not marketing):
+> *"Plate 47 · scored before the proof."* — Maple Street Bread (test 03) — a number, a moment in the process
+> *"Spring, 2026."* — Atelier-style — two words, full stop
+> *"From the working archive."* — gives the photograph provenance without explaining it
+
+```html
+<section class="photo-fold">
+ <img class="bleed" src="hero.jpg" />
+ <p class="caption">Spring, 2026.</p>
+</section>
+<section class="text-fold">
+ <p class="lede">…</p>
+</section>
+<section class="photo-fold">…</section>
+```
+
+---
diff --git a/skill/references/macrostructures/09-quote-led.md b/skill/references/macrostructures/09-quote-led.md
new file mode 100644
index 0000000..36c1965
--- /dev/null
+++ b/skill/references/macrostructures/09-quote-led.md
@@ -0,0 +1,32 @@
+## 09 · Quote-Led
+
+The hero is a pull-quote with attribution. The headline is borrowed credibility, not the brand's voice. The page leads with social proof.
+
+- **Heading:** italic display setting a customer's quote (36–60 px), with attribution below in small caps.
+- **Body:** continues with additional testimonials, case studies, or a quiet feature list.
+- **Divider:** centered quote-mark glyph or an em-rule between testimonials.
+- **Button:** typographic link beneath the attribution ("Read the full case study →").
+- **Image:** small avatar or company logo by the attribution; otherwise none.
+- **Reveal:** none in fold; below-fold may stagger.
+
+Reach for it for B2B products with strong customer voices, agency case-study pages, fundraising sites, anywhere "people like me use this" is the unlock.
+
+Avoid for new products without real testimonials. Fake quotes destroy trust on inspection.
+
+Reference: many B2B SaaS landings, agency homepages, university development pages.
+
+**Sample opening lines** (imitate the *specificity* — quote-led pages let someone else say it, then attribute):
+> *"I started listening on a long bus ride. By the third episode I'd missed my stop, and I didn't mind."* — Tide (test 01) — story-shaped, attributed to a listener
+> *"Restraint, repeated, becomes a signature."* — Hallmark Atelier — short, philosophical, signed by the studio
+> *"It told me the span that regressed, the deploy that caused it, and the engineer to ask. We rolled back in eight minutes."* — Tracejam-style — names the outcome with a number
+
+```html
+<section class="quote-hero">
+ <blockquote class="display-italic">"…"</blockquote>
+ <p class="attribution">— Name, Title, Company</p>
+ <a class="link">Read the case →</a>
+</section>
+<section class="more-quotes">…</section>
+```
+
+---
diff --git a/skill/references/macrostructures/10-specimen.md b/skill/references/macrostructures/10-specimen.md
new file mode 100644
index 0000000..ab343b4
--- /dev/null
+++ b/skill/references/macrostructures/10-specimen.md
@@ -0,0 +1,32 @@
+## 10 · Specimen *(no longer the default)*
+
+Numbered left-margin labels, huge serif display, asymmetric column spans, hairline rules, typographic-only CTA, generous whitespace. Editorial / type-foundry energy.
+
+- **Heading:** left-margin number + label (`01 — HELLO.`) beside a large serif phrase.
+- **Body:** asymmetric spans — narrow label column / wide content column.
+- **Divider:** hairline rules between sections.
+- **Button:** typographic link with arrow ("Open your studio →"); no box, no fill.
+- **Image:** none, or a hand-drawn SVG accent in the wide left margin.
+- **Reveal:** fade-up stagger on first load.
+
+Reach for it ONLY when the brief is explicitly editorial, type-foundry, journal, or "specimen sheet". Otherwise pick something else.
+
+**Banned as a default.** If the brief is vague and you've defaulted here, restart.
+
+Reference: type foundry homepages (Klim, Pangram Pangram, Production Type), some editorial portfolios.
+
+**Sample opening lines** (imitate the *specificity* — Specimen openings are foundry-voice, treating type as material culture):
+> *"A thing well made."* — klim.co.nz — refusal of the verb, treats design as material
+> *"Type, set with care."* — Hallmark Specimen — three words, a colon implied
+> *"Creative direction, design and type for culture since 2003."* — apracticeforeverydaylife.com — date-anchored, names verticals
+
+```html
+<header class="specimen">
+ <p class="num-label">01 — HELLO.</p>
+ <h1 class="serif-xxl">A quiet <em>instrument.</em></h1>
+ <p class="lede narrow">…</p>
+ <a class="link">Open your studio →</a>
+</header>
+```
+
+---
diff --git a/skill/references/macrostructures/11-catalogue.md b/skill/references/macrostructures/11-catalogue.md
new file mode 100644
index 0000000..c4fd2a3
--- /dev/null
+++ b/skill/references/macrostructures/11-catalogue.md
@@ -0,0 +1,23 @@
+## 11 · Catalogue
+
+Uniform grid of variations of the same thing — typefaces, colour palettes, product SKUs. The page is a visual index of inventory.
+
+- **Heading:** brand mark + tagline only; no big display.
+- **Body:** grid of identical-sized cards (3–5 per row), each one variant of the core product.
+- **Divider:** hairline rules between rows; sometimes a category label band.
+- **Button:** card-internal link to detail page; no global CTA.
+- **Image:** specimen thumbnail per card, or a swatch.
+- **Reveal:** none.
+
+Reach for it for foundries, palette generators, font shops, colour systems, capsule collections.
+
+Avoid for narrative brands. Catalogue treats every item as equal — wrong for products with hierarchy.
+
+Reference: Klim Type Foundry, Pangram Pangram, Coolors palettes.
+
+**Sample opening lines** (imitate the *specificity* — Catalogue openings are inventory headers, dated, with a count):
+> *"Today's loaves."* — Maple Street Bread (test 03) — two words, ownership of the day
+> *"Five collections, in store now."* — names the count and the where
+> *"Thirty-eight items · Spring 2026 · all hand-stitched."* — count, date, qualifier; no adjectives
+
+---
diff --git a/skill/references/macrostructures/12-letter.md b/skill/references/macrostructures/12-letter.md
new file mode 100644
index 0000000..bb31f6f
--- /dev/null
+++ b/skill/references/macrostructures/12-letter.md
@@ -0,0 +1,23 @@
+## 12 · Letter
+
+First-person, written, intimate. Opens with a greeting ("Dear friend,"). No buttons in the fold. Reads as a personal note from the founder.
+
+- **Heading:** salutation in serif italic ("Dear reader,"), 1.5–2× body size.
+- **Body:** prose, single column, narrow measure (50ch), as if typed.
+- **Divider:** paragraph spacing only, occasional `* * *` separator.
+- **Button:** sign-off link at the foot ("p.s. join us if you'd like →").
+- **Image:** maybe one signature scan, or a quiet inline photograph.
+- **Reveal:** none.
+
+Reach for it for personal brands, indie founder announcements, sabbatical or pivot pages, donation appeals.
+
+Avoid for transactional commerce. Letter is intimate; commerce is functional.
+
+Reference: Frank Chimero's site, founder farewell posts, indie newsletter front pages.
+
+**Sample opening lines** (imitate the *specificity* — Letter openings are first-person greetings, dated, with a place if relevant):
+> *"Hello, I'm Anya."* — Anya (test 06) — single line, name, full stop
+> *"Saturday, 6:14 a.m. The dough went in at midnight."* — opens on a moment, then explains it
+> *"Hey there. This page is soft because the surface should be soft."* — Hallmark Plume — colloquial open + a principle
+
+---
diff --git a/skill/references/macrostructures/13-index-first.md b/skill/references/macrostructures/13-index-first.md
new file mode 100644
index 0000000..7527d8b
--- /dev/null
+++ b/skill/references/macrostructures/13-index-first.md
@@ -0,0 +1,23 @@
+## 13 · Index-First
+
+The page IS a list of links. No hero image, no narrative flow. Pure navigation as design.
+
+- **Heading:** one short paragraph at the top introducing the index, no display type.
+- **Body:** vertical list of categorised links; sometimes a sidebar of filters.
+- **Divider:** hairline rules between rows; or zero rules with paper-colour bands.
+- **Button:** the links themselves are the buttons.
+- **Image:** none, or tiny favicons by each entry.
+- **Reveal:** none.
+
+Reach for it for documentation hubs, knowledge bases, archive front pages, design system entries, link-in-bio pages with substance.
+
+Avoid for marketing pages. Index-First is for browsing audiences; selling needs structure.
+
+Reference: Are.na's homepage feel, archive sites, documentation indices.
+
+**Sample opening lines** (imitate the *specificity* — Index-First openings are headers for what's below, sometimes nothing more than a label):
+> *"Selected work · 2018 — 2026."* — date range, no preamble
+> *"Things Become Other Things · Lightness above weightiness."* — craigmod.com — two phrases joined by a divider
+> *"Writer + Photographer."* — craigmod.com — three words, summarises the whole site
+
+---
diff --git a/skill/references/macrostructures/14-narrative-workflow.md b/skill/references/macrostructures/14-narrative-workflow.md
new file mode 100644
index 0000000..cfe0a78
--- /dev/null
+++ b/skill/references/macrostructures/14-narrative-workflow.md
@@ -0,0 +1,23 @@
+## 14 · Narrative Workflow
+
+Numbered stages tell the story of how the user uses the product over time. Each section is a phase (1.0 → 2.0 → 3.0 → 4.0). The page is a process timeline.
+
+- **Heading:** large numbered stage labels (`1.0 INTAKE`, `2.0 PLAN`).
+- **Body:** each stage has a short explanation and a small product visual.
+- **Divider:** thick numbered rule between stages.
+- **Button:** stage-internal links; one global "Start at stage 1 →" at the foot.
+- **Image:** small product capture per stage, often annotated.
+- **Reveal:** sweep horizontal as stages enter the viewport.
+
+Reach for it for products with explicit workflows — project management, design-to-dev pipelines, writing tools.
+
+Avoid for tools that work in *one* moment. Narrative Workflow needs a real sequence.
+
+Reference: Linear's how-it-works pages, some Figma marketing pages.
+
+**Sample opening lines** (imitate the *specificity* — Narrative Workflow openings are stage labels: numbered, declarative, in process language):
+> *"01 · sourdough overnight · 02 · score at dawn · 03 · pull at seven."* — three numbered stages, no marketing
+> *"1.0 · parse · 2.0 · filter · 3.0 · route."* — Streampipe (test 02) — versioned numbers, three concrete verbs
+> *"I. We design products that last twelve years. II. A material is sustainable when someone, somewhere, can repair it."* — Meridian — Roman numerals + declarative
+
+---
diff --git a/skill/references/macrostructures/15-split-studio.md b/skill/references/macrostructures/15-split-studio.md
new file mode 100644
index 0000000..bf05bda
--- /dev/null
+++ b/skill/references/macrostructures/15-split-studio.md
@@ -0,0 +1,23 @@
+## 15 · Split Studio
+
+Diptych. Every major content block divides the screen — text on one side, proof on the other. The pairing alternates direction down the page.
+
+- **Heading:** half-screen wide; the other half holds a screenshot or a quote.
+- **Body:** alternating left-text/right-image and right-text/left-image modules.
+- **Divider:** a clear gutter between halves; no rules.
+- **Button:** outlined chip below the text half.
+- **Image:** anchored to the opposite half from the text in each row.
+- **Reveal:** opposite halves cross-fade in slightly staggered.
+
+Reach for it for SaaS feature pages, dev tools that pair explanation with code, anything where every claim wants a visual proof.
+
+Avoid for narrative or photographic brands. Split halves the attention; some pages need single focus.
+
+Reference: Vercel feature pages, Stripe Sessions program pages, many dev-tool homepages.
+
+**Sample opening lines** (imitate the *specificity* — Split Studio openings pair a positioning statement with a proof column):
+> *"A studio for what's next."* — italic display + selected-work column on the right
+> *"Print discipline, on screen."* — Hallmark Newsprint — two-phrase headline, masthead-style
+> *"We design and build distinctive products for ambitious teams."* — names the verb (design and build), names the audience
+
+---
diff --git a/skill/references/macrostructures/16-feature-stack.md b/skill/references/macrostructures/16-feature-stack.md
new file mode 100644
index 0000000..e693e6c
--- /dev/null
+++ b/skill/references/macrostructures/16-feature-stack.md
@@ -0,0 +1,23 @@
+## 16 · Feature Stack
+
+Sticky left pane (label / description) + scroll-synced right pane (screenshots cycling through related details). Cinematic pacing.
+
+- **Heading:** held inside the sticky pane; persists while content cycles beside it.
+- **Body:** two columns — left sticky, right scrolling; the right pane plays through 3–6 detail screens per section.
+- **Divider:** section bands; the sticky pane re-anchors per section.
+- **Button:** in the sticky pane, set when the user reaches the section's detail count.
+- **Image:** the scrolling-right column is mostly imagery.
+- **Reveal:** none of the spatial-fade kind; the sticky/scroll IS the motion.
+
+Reach for it for premium products, complex feature stories, anything where you want to control pacing as the user scrolls.
+
+Avoid on mobile-first audiences without strong fallback. Sticky+scroll-sync is rough on small screens.
+
+Reference: Apple product pages, some Stripe Sessions pages, Read.cv onboarding.
+
+**Sample opening lines** (imitate the *specificity* — Feature Stack openings pin a single statement and then walk the user through):
+> *"Plan, build, ship."* — three verbs, three sticky panes
+> *"Read anything that emits lines."* — Streampipe (test 02) — names what's possible, then walks through it
+> *"From stdin, through the pipe, into your dashboard."* — names the data path, then explains each step
+
+---
diff --git a/skill/references/macrostructures/17-type-specimen.md b/skill/references/macrostructures/17-type-specimen.md
new file mode 100644
index 0000000..dea1ae8
--- /dev/null
+++ b/skill/references/macrostructures/17-type-specimen.md
@@ -0,0 +1,23 @@
+## 17 · Type Specimen
+
+The typeface IS the design. Foundry homepage or design-system marketing where a custom typeface is the brand's proof.
+
+- **Heading:** the typeface set at multiple sizes, demonstrating what it does.
+- **Body:** progressive demonstration — display size, body size, italic, language coverage, OpenType features.
+- **Divider:** centred caption labels between specimens.
+- **Button:** outlined "Buy" or "Use it" at the foot.
+- **Image:** none — typography is the imagery.
+- **Reveal:** type-unmask on first paint of each specimen block.
+
+Reach for it for type foundries, design systems where a custom face is the differentiator, font product pages.
+
+Avoid when the brand uses an off-the-shelf face. Type Specimen needs something distinctive to celebrate.
+
+Reference: Klim Type Foundry, Pangram Pangram, Geist Pixel announcement pages.
+
+**Sample opening lines** (imitate the *specificity* — Type Specimen openings are foundry-voice: name the typeface, the weights, the use):
+> *"Reckless Display, set in 96 pt."* — names the face and the size, nothing else
+> *"Eight weights. Three optical sizes. One good italic."* — counts the system in three short phrases
+> *"A type system for editorial."* — refusal of the verb, single noun phrase
+
+---
diff --git a/skill/references/macrostructures/18-portfolio-grid.md b/skill/references/macrostructures/18-portfolio-grid.md
new file mode 100644
index 0000000..968ae6d
--- /dev/null
+++ b/skill/references/macrostructures/18-portfolio-grid.md
@@ -0,0 +1,23 @@
+## 18 · Portfolio Grid
+
+Filterable cards of projects. Studio or designer homepages where the work is the product.
+
+- **Heading:** short tagline above the grid; no display.
+- **Body:** responsive grid of project cards, all same size or with subtle size variation.
+- **Divider:** filter bar above the grid; no internal rules.
+- **Button:** card-internal "View case study"; no global CTA.
+- **Image:** thumbnail per card.
+- **Reveal:** card-fade on filter change.
+
+Reach for it for design studios, agencies, photographer portfolios, any creative business where work is the pitch.
+
+Avoid for products. Portfolio Grid is service-business shape.
+
+Reference: Pentagram, 14islands, Locomotive, Bureau Borsche.
+
+**Sample opening lines** (imitate the *specificity* — Portfolio Grid openings name the volume and the era):
+> *"Selected work · 2018 — 2026."* — date range, two characters of meta
+> *"Twelve projects, six clients, two countries."* — three counts, no adjective
+> *"Work, indexed by year."* — five-word labels, the index is the whole site
+
+---
diff --git a/skill/references/macrostructures/19-map-diagram.md b/skill/references/macrostructures/19-map-diagram.md
new file mode 100644
index 0000000..f2a035b
--- /dev/null
+++ b/skill/references/macrostructures/19-map-diagram.md
@@ -0,0 +1,23 @@
+## 19 · Map / Diagram
+
+A single large spatial diagram organises the page — flowchart, floor plan, network graph, system map. Information is laid out *spatially*, not linearly.
+
+- **Heading:** a small orientation phrase above or beside the map.
+- **Body:** the map itself; nodes and edges; a legend somewhere.
+- **Divider:** the diagram has no internal sections — it's one composition.
+- **Button:** node-internal links; one outlined CTA below the map.
+- **Image:** the map IS the image; SVG with interactive hovers.
+- **Reveal:** node-by-node ink-on as the user enters viewport (cap to 5 nodes).
+
+Reach for it for system overviews, ecosystem maps, process diagrams, organisation charts.
+
+Avoid as a substitute for narrative. Some stories shouldn't be read spatially.
+
+Reference: process visualisation sites, ecosystem maps, knowledge-graph products.
+
+**Sample opening lines** (imitate the *specificity* — Map / Diagram openings name the path or the territory):
+> *"Browser → API → Database. Where Tracejam fits."* — names the layers, names the position
+> *"From stdin, through the pipe, into your dashboard."* — labels the spatial flow on the page below
+> *"Three tiers · two regions · one ledger."* — counts the system, geographic + structural
+
+---
diff --git a/skill/references/macrostructures/20-ecosystem-index.md b/skill/references/macrostructures/20-ecosystem-index.md
new file mode 100644
index 0000000..5dfee94
--- /dev/null
+++ b/skill/references/macrostructures/20-ecosystem-index.md
@@ -0,0 +1,23 @@
+## 20 · Ecosystem Index
+
+Multiple discovery surfaces — featured / latest / by category / by people. The platform's value is emergence and browsing, not declaration.
+
+- **Heading:** brief positioning paragraph; no display.
+- **Body:** several horizontal rails or grids — each surfacing a different cut of the platform's content.
+- **Divider:** rail-titled bands.
+- **Button:** "See more →" at each rail's edge; rarely a global CTA.
+- **Image:** thumbnails everywhere; the page is dense imagery.
+- **Reveal:** none.
+
+Reach for it for community platforms, content marketplaces, design-asset stores, any UGC/curated catalogue front page.
+
+Avoid for single-product pages. Ecosystem needs multiple things to surface.
+
+Reference: Are.na, Figma Community, Behance.
+
+**Sample opening lines** (imitate the *specificity* — Ecosystem Index openings are surface labels, dated, with a count):
+> *"Featured · Latest · By category."* — three discovery surfaces named, divided
+> *"What's on this week · Editor's pick · The whole catalogue."* — names cadence, curation, breadth
+> *"A toolkit for assembling new worlds from the scraps of the old."* — are.na — second-position copy that breaks template
+
+---
diff --git a/skill/references/macrostructures/21-component-playground.md b/skill/references/macrostructures/21-component-playground.md
new file mode 100644
index 0000000..c6f65c6
--- /dev/null
+++ b/skill/references/macrostructures/21-component-playground.md
@@ -0,0 +1,23 @@
+## 21 · Component Playground
+
+Interactive code-and-preview blocks are the page's primary content. Each block previews a thing and shows how to copy-paste it.
+
+- **Heading:** category labels (`Buttons`, `Forms`, `Cards`, `Layouts`).
+- **Body:** alternating preview-and-code blocks, often with a tab to switch frameworks.
+- **Divider:** category bands; horizontal rules between examples.
+- **Button:** "Copy" button on every code block (silent success).
+- **Image:** none — the previews ARE the imagery.
+- **Reveal:** none.
+
+Reach for it for design systems, component libraries, code-snippet sites, framework documentation.
+
+Avoid for marketing pages. Playground is utility, not pitch.
+
+Reference: shadcn/ui, Tailwind UI, Once UI, MUI demos, Framer Motion examples.
+
+**Sample opening lines** (imitate the *specificity* — Component Playground openings are tangible: open on a real example, not a claim):
+> *"Try it inline. Then take it home."* — two short imperatives
+> *"Every example is editable. Every output is real."* — pairs claim with proof
+> *"From `npm install` to your first chart in eight lines."* — names the step count, makes a concrete promise
+
+---
diff --git a/skill/references/preview-examples.md b/skill/references/preview-examples.md
new file mode 100644
index 0000000..d1ad30e
--- /dev/null
+++ b/skill/references/preview-examples.md
@@ -0,0 +1,49 @@
+# Preview-block worked examples
+
+Four sample Step 5 preview blocks for the model to imitate, varied across macrostructure types. Load this file only when picking an unusual macrostructure or custom theme and the bullet-list spec in `SKILL.md § 5. Preview` doesn't give enough scaffolding on its own. Most builds don't need to read this file.
+
+---
+
+*Long Document (editorial, motion-cut):*
+> **Hallmark · v1.0.0**
+>
+> - **Macrostructure** · Long Document
+> - **Theme** · Linen (cool slate paper · steel-blue accent · geometric sans)
+> - **Enrichment** · Tier-B hand-built SVG (a 60-line coffee bean with `@property --rise` 6 s breathing-loop)
+> - **Sections** · Masthead · Letter · Three Notes · Visit · Colophon
+> - **Motion** · breathing-loop on bean only (respects `prefers-reduced-motion`)
+> - **Slop test** · 66 / 66 ✓
+> - **Diversification** · first run for this project
+
+*Bento Grid (SaaS, motion-on):*
+> **Hallmark · v1.0.0**
+>
+> - **Macrostructure** · Bento Grid
+> - **Theme** · Linen (cool slate paper · steel-blue accent · geometric sans)
+> - **Enrichment** · E1 Clipped-Edge Demo Video, Tier-A CSS-art trace waterfall
+> - **Sections** · Hero · 6-tile Bento (stat · sparkline · quote · code · integrations · spotlight) · Index Footer
+> - **Motion** · counter · pricing-lift · CSS marquee on integrations strip
+> - **Slop test** · 66 / 66 ✓
+> - **Diversification** · differs from Plain on paper hue (light-cool vs pure-white) + accent (indigo vs ink-blue)
+
+*Manifesto (declarative, no enrichment):*
+> **Hallmark · v1.0.0**
+>
+> - **Macrostructure** · Manifesto
+> - **Theme** · Manifesto (dark · Inter Tight 900 · single red bleed)
+> - **Enrichment** · none (typography only — voice carries the brand)
+> - **Sections** · Masthead · Title · Five Declarations · Bleed Band · What We Refuse · Working Rules · Practice · Reading · Colophon
+> - **Motion** · none — typography only
+> - **Slop test** · 66 / 66 ✓
+> - **Diversification** · differs from Linen on paper band (dark vs light) + display style (display-heavy vs geometric-sans)
+
+*Custom (Coffeebox archival café):*
+> **Hallmark · v1.0.0**
+>
+> - **Macrostructure** · Long Document
+> - **Theme** · custom (vibe: "archival warmth, hand-set, no varnish" · paper oklch(94% 0.020 65) · accent oklch(58% 0.16 35) terracotta · Fraunces italic display + Source Serif 4 body)
+> - **Enrichment** · Tier-A pure-CSS coffee bean (60-line SVG, breathing-loop optional)
+> - **Sections** · Masthead · Letter · Three Notes · Visit · Colophon
+> - **Motion** · breathing-loop on bean (with reduced-motion fallback)
+> - **Slop test** · 66 / 66 ✓
+> - **Diversification** · custom axes: light / italic-serif / chromatic-terracotta — differs from previous catalog Linen on accent hue + display style