Skip to content

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

CSS

Themes go back to being the main road; custom is the asked-for exception

Youssef0e74745a104a
diff --git a/README.md b/README.md
index 57fdcda..4461c6f 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
**A design skill for Claude Code, Cursor, and Codex that refuses to look AI-generated.**
-[Live demo →](https://www.usehallmark.com)  ·  a derived world per brief  ·  twenty-three themes  ·  five verbs  ·  press `T` to cycle.
+[Live demo →](https://www.usehallmark.com)  ·  twenty-three themes  ·  a custom world on request  ·  five verbs  ·  press `T` to cycle.
Made by Together AI.
@@ -10,7 +10,7 @@ Made by Together AI.
<img src="site/OG-hallmark.png" alt="Hallmark, a design skill that refuses to look AI-generated" />
</p>
-Hallmark holds a hard floor and then gets out of the way. It derives a visual world made-to-measure for each brief (an outside draw picks among grounded directions, so the model cannot repeat its favourite), keeps twenty-three named themes as a fast path, runs a fifty-eight-gate slop test plus a pre-emit self-critique, and refuses the on-distribution defaults every LLM was trained into.
+Hallmark holds a hard floor and then gets out of the way. It dresses the brief in one of twenty-three themes, derives a world made-to-measure when the user asks for **custom** (an outside draw picks among grounded directions, so the model cannot repeat its favourite), runs a fifty-eight-gate slop test plus a pre-emit self-critique, and refuses the on-distribution defaults every LLM was trained into.
Thirty-four of those gates are a **floor**: contrast, focus order, reduced motion, invented metrics, layout that breaks on a phone, and the eyebrow above the heading. Nothing ships through them. Eighteen are **reflex** gates, the defaults a language model falls into rather than laws, and a build with an argument can overrule one on the record, with the reason named in the CSS stamp and the guard re-derived by the checker. There is no cap on how many: a colour-field poster that wants a black stage, achromatic neutrals and one face doing everything is allowed to say so and ship. The last six are polish and bookkeeping and never block a ship.
@@ -79,9 +79,9 @@ Each page is self-contained HTML + CSS, stamped with its macrostructure in the C
## Custom
-When a brief carries creative intent that no catalog theme fits, Hallmark switches to **Custom** and designs the page from scratch: a made-to-measure palette, type, and layout. Same fifty-eight gates at the same tiers, no template underneath.
+When the user asks for **custom** (or "derive it", "bespoke", "no theme"), Hallmark leaves the catalog and designs the page from scratch: a made-to-measure palette, type, and layout. Same fifty-eight gates at the same tiers, no template underneath.
-In v1.2 the custom route runs a full art-direction ritual: it names and rejects the category's reflex aesthetics, writes a slate of seven grounded directions, and a deterministic **draw** (`scripts/seed.mjs`) picks which one gets built, dealing three **challengers** from a curated atlas of complete design systems (a graphic system, an instrument language, an atmosphere world), each judged against the drawn direction on audience identification and product clarity; even a losing challenger donates one discipline it does best. A scene sentence sets the light, a colour posture (Restrained · Committed · Full palette · Drenched) sets how far the palette commits, and a five-block direction contract written into the artifact gets audited promise by promise before shipping.
+The custom route, taken when the user asks for it by name, runs a full art-direction ritual: it names and rejects the category's reflex aesthetics, writes a slate of seven grounded directions, and a deterministic **draw** (`scripts/seed.mjs`) picks which one gets built, dealing three **challengers** from a curated atlas of complete design systems (a graphic system, an instrument language, an atmosphere world), each judged against the drawn direction on audience identification and product clarity; even a losing challenger donates one discipline it does best. A scene sentence sets the light, a colour posture (Restrained · Committed · Full palette · Drenched) sets how far the palette commits, and a five-block direction contract written into the artifact gets audited promise by promise before shipping.
<table>
<tr>
diff --git a/eval/briefs.json b/eval/briefs.json
index e2da050..83d182c 100644
--- a/eval/briefs.json
+++ b/eval/briefs.json
@@ -59,7 +59,7 @@
"brief": "--fast Build a landing page for a two-person bookbinding workshop that takes commissions.",
"expect": {
"scope": "page",
- "notes": "Route coverage for the catalog fast path after derivation became the default. --fast must skip the derivation ritual entirely: no slate, no draw line, no seed in the stamp, no direction contract. The stamp must name one of the 23 catalog themes rather than 'custom'. Its twin is b1, which names no theme and must therefore derive."
+ "notes": "Route coverage for the catalog default. --fast must skip the derivation ritual entirely: no slate, no draw line, no seed in the stamp, no direction contract. The stamp must name one of the 23 catalog themes rather than 'custom'. Its twin is b1, which names no theme and, taking no custom route either, must also land on a catalog theme."
}
}
]
diff --git a/skills/hallmark/SKILL.md b/skills/hallmark/SKILL.md
index 3d38e4d..7155961 100644
--- a/skills/hallmark/SKILL.md
+++ b/skills/hallmark/SKILL.md
@@ -41,7 +41,7 @@ These bind on every output, in every verb, on every model, and **none of them is
0.5. Signal 8 only (a reference archive is connected): the archive builds, Hallmark skips Steps 1-6 and enters at Step 7.
1. Ask Audience / Use case / Tone plus the vibe, once; detect genre.
2. Design the page's shape, nav, footer, hero, and section entry; run the Rotation rules. (Catalogs available, never required.)
-2.6. Direction: derive the world (the default, ritual in [`references/direction.md`](references/direction.md)), or take the catalog fast path when one of its four conditions holds.
+2.6. Direction: pick a theme from the catalog (the default), or run the derivation ritual in [`references/direction.md`](references/direction.md) when the user asked for **custom**.
3. Load ONLY the listed reference files.
4. Enrichment decision (scene sentence first; most pages are typography-only).
5. The Picks block (the run's only prose recital), then pause a beat before code.
@@ -69,7 +69,7 @@ If the input does not clearly map to a verb, treat it as default. If the user at
**Implementation safety rail.** Hallmark is a design skill, not a license to bulldoze a codebase. In any existing project: never delete production files, route trees, or component directories unless the user explicitly approves a file-level plan that lists the deletions; default to in-place edits or additive components wired through existing routes; treat PDFs, READMEs, briefs, and decks as reference material, never copied verbatim without instruction; before editing, state the exact files you expect to modify, create, or delete.
-**Direction, in one breath.** Every build **derives its own visual world** from the brief, by the ritual in [`references/direction.md`](references/direction.md): name the category's reflex, list seven grounded directions from the audience's own world, and let an outside draw pick which one gets built. The model's favourite is deterministic, so letting it choose is letting it repeat itself. The **23 named themes** are a fast path, taken only when the user names one, `--fast` is passed, a `design.md` or real brand already exists, or the scope is a single component. Silence derives.
+**Direction, in one breath.** Every build dresses the brief in one of the **23 named themes**, picked per Rotation so consecutive builds move: the catalog is Hallmark's main road and its default. A user who wants a world of their own says **custom** (or "derive it", "bespoke", "no theme"), and that build runs the ritual in [`references/direction.md`](references/direction.md) instead: name the category's reflex, list seven grounded directions from the audience's own world, and let an outside draw pick which one gets built, because the model's favourite is deterministic and letting it choose is letting it repeat itself. Silence takes a theme.
---
@@ -204,7 +204,7 @@ Two things the catalogs are not: a checklist you owe, and a rotation you must wa
**Rotation (the canonical block - every other file defers here):**
- **Structure:** the page's shape must differ from the last three Hallmark outputs for this project (read `.hallmark/log.json`, newest first; a CSS stamp counts when the log is missing). Whether you named a catalog shape or invented one, the log records what you built and the next run has to move.
-- **Theme:** two consecutive systems must differ on at least one of three axes: **paper band** (dark < 30% L · mid 30-85% · light > 85%), **display style**, **accent hue** (warm 10-60° · cool 200-300° · neutral · chromatic-other). A derived system declares its own triple ([`references/direction.md`](references/direction.md) § D) and must additionally clear the worn-coordinates digest carried in that same section; it never opens the catalog to do so. On the fast path, the table in [`references/theme-axes.md`](references/theme-axes.md) is the lookup: two of three matching means pick a more distant theme.
+- **Theme:** two consecutive systems must differ on at least one of three axes: **paper band** (dark < 30% L · mid 30-85% · light > 85%), **display style**, **accent hue** (warm 10-60° · cool 200-300° · neutral · chromatic-other). The catalog table in [`references/theme-axes.md`](references/theme-axes.md) is the lookup: two of three matching means pick a more distant theme. A custom system declares its own triple ([`references/direction.md`](references/direction.md) § D) and must additionally clear all 23 catalog coordinates ([`references/theme-axes.md`](references/theme-axes.md) § The rejection reading).
- **Chrome:** the nav and the footer must not be the same shape as the last three runs, across consecutive runs and across test builds of the same theme. This is the single most-violated rule. If you reach for the default nav, the stamp has to name it (gate 42) — the default is allowed, arriving at it by reflex is not.
- **Hero:** vary the hero's stance run to run. Nothing but the fold-fit floor (gate 44b) constrains how tall or how anchored it is.
- **Enrichment:** do not repeat the previous run's enrichment approach back-to-back.
@@ -229,21 +229,22 @@ The `axes` and `fingerprint` fields are how Rotation and gate 32 become checkabl
### 2.6. Direction
-**Derive, unless one of the fast-path conditions holds.** Check them in order; the first match wins.
+**Take a theme, unless the user asked for a custom world.** Check in order; the first match wins.
0. **A `study` diagnosis emitted earlier and the user says build with it** → route **studied-DNA**: the diagnosis's paper OKLCH, accent OKLCH, type roles, macrostructure, and archetypes become the locked system. Diversification is suspended. Stamp `theme: studied-DNA (source: <URL or image>)` with the values inline. The user pivoting ("use Newsprint instead", "ignore the DNA") re-enters the dispatch.
-1. **The catalog fast path**, on any one of four conditions and no others: the user **names a theme**; `--fast` was passed; a `design.md` or a real brand already exists (Step 0 caught it, and that branch never reached here); or the scope is a **single component**. Then pick per Rotation from the catalog (the lookup table in [`references/theme-axes.md`](references/theme-axes.md) lists every theme with its axes and arbitrates distance) and load that one theme's file from `references/themes/`. Do not enumerate or browse the catalog on any other route.
-2. **Everything else derives.** Load [`references/direction.md`](references/direction.md) and run the ritual: reflex check → spent defaults → slate → draw → scene sentence → colour posture → direction contract → build → finish review. Tuned keeps Hallmark's structures; bespoke (the structure itself is the ask) designs from first principles. Do not ask which route; do not mention the catalog.
+1. **The user named a theme** → build it. An explicit pick beats everything below.
+2. **The user asked for custom** → load [`references/direction.md`](references/direction.md) and run the ritual: reflex check → spent defaults → slate → draw → challengers → scene sentence → colour posture → direction contract → build → finish review. The ask is any of **custom**, "derive it", "bespoke", "no theme", "something of its own", or an explicit refusal of the catalog. Tuned keeps Hallmark's structures; bespoke (the structure itself is the ask) designs from first principles.
+3. **Everything else takes the catalog.** Pick per Rotation from the 23 themes; the lookup table in [`references/theme-axes.md`](references/theme-axes.md) carries every theme's axes and arbitrates distance. Load that one theme's file from `references/themes/` and nothing else from the catalog. Do not ask which route, and do not offer the custom path unprompted: silence is a theme.
-A derived system is complete (palette + pairing + axes), never a colour swap; its diversification axes are recorded exactly like a catalog theme's. All 58 slop-test gates fire unchanged, at their usual tiers, and the Step 5 Picks block surfaces everything before code.
+A custom system is complete (palette + pairing + axes), never a colour swap; its diversification axes are recorded exactly like a catalog theme's. All 58 slop-test gates fire unchanged on both routes, at their usual tiers, and the Step 5 Picks block surfaces everything before code.
-**Two consequences, stated once.** Every derived run stamps `posture:`, so gate 23 reads its posture-aware branch as the normal path rather than the occasional one; nothing about the gate changed. And a derived triple still has somewhere it may not land: the worn-coordinates digest in [`references/direction.md`](references/direction.md) § D lists the axis triples Hallmark has already worn out, with no theme names attached.
+**Two consequences, stated once.** A custom run stamps `posture:`, so gate 23 reads its posture-aware branch; nothing about the gate changed. And a custom triple still has somewhere it may not land: [`references/theme-axes.md`](references/theme-axes.md) § The rejection reading is the list of coordinates the catalog already occupies.
### 3. Load the visual ruleset
**Do:** load exactly what this build needs; over-eager loading is the largest avoidable cost of running Hallmark.
-**Always (2-3 files):** the genre file from Step 1; [`references/enrichment/hero-discipline.md`](references/enrichment/hero-discipline.md) (the hero rules bind on every page hero, enriched or not); plus, **on the catalog fast path only**, `references/themes/<theme>.md` for the picked theme (every theme has one). A derived run loads [`references/direction.md`](references/direction.md) instead and touches nothing under the catalog.
+**Always (2-3 files):** the genre file from Step 1; [`references/enrichment/hero-discipline.md`](references/enrichment/hero-discipline.md) (the hero rules bind on every page hero, enriched or not); plus `references/themes/<theme>.md` for the picked theme (every theme has one). A custom run loads [`references/direction.md`](references/direction.md) instead, and reads [`references/theme-axes.md`](references/theme-axes.md) § The rejection reading rather than the whole file.
**Index-then-pick (only when you are taking a named starting point; skip entirely when you are not):**
- [`references/macrostructures.md`](references/macrostructures.md) → one file from `references/macrostructures/`.
@@ -255,7 +256,7 @@ A derived system is complete (palette + pairing + axes), never a colour swap; it
Two of those carry sections you should skip rather than read whole: `typography.md` § The font catalog is dead weight when a catalog theme has already named the faces, and `copy.md` § Voice samples per tone is seven blocks of which six are not your tone. Skipping both saves roughly 200 lines a build.
-**Conditionally (be honest, no defensive pre-loads):** [`references/microinteractions.md`](references/microinteractions.md) when anything is interactive (most pages); [`references/interaction-and-states.md`](references/interaction-and-states.md) for stateful UI; [`references/responsive.md`](references/responsive.md) when mobile is in scope; [`references/structure.md`](references/structure.md) only when deviating from a named macrostructure; [`references/assets.md`](references/assets.md) only when an enrichment needs an external asset; [`references/texture.md`](references/texture.md) only when the picked theme earns texture (Riso, Carnival, Arcade, faint Newsprint) or a custom draw has print lineage; [`references/scroll-choreography.md`](references/scroll-choreography.md) only when the brief asks for scroll story / cinematic pacing or the macro is Feature-stack / Narrative Workflow; [`references/dark-mode.md`](references/dark-mode.md) only when the user asks for both modes; [`references/data-viz.md`](references/data-viz.md) when the brief involves charts / data / dashboards or the macro is Stat-Led / Workbench; [`references/brand-truth.md`](references/brand-truth.md) when the brief names a real brand or company to build for; [`references/theme-axes.md`](references/theme-axes.md) only when picking from the catalog, never on a derived run; [`references/comp.md`](references/comp.md) only when signal 9 fired, at Step 5.5, never earlier; [`references/design-md.md`](references/design-md.md) only when the user asks to lock the system; [`references/preview-examples.md`](references/preview-examples.md) only if the Step 5 spec is not scaffolding enough.
+**Conditionally (be honest, no defensive pre-loads):** [`references/microinteractions.md`](references/microinteractions.md) when anything is interactive (most pages); [`references/interaction-and-states.md`](references/interaction-and-states.md) for stateful UI; [`references/responsive.md`](references/responsive.md) when mobile is in scope; [`references/structure.md`](references/structure.md) only when deviating from a named macrostructure; [`references/assets.md`](references/assets.md) only when an enrichment needs an external asset; [`references/texture.md`](references/texture.md) only when the picked theme earns texture (Riso, Carnival, Arcade, faint Newsprint) or a custom draw has print lineage; [`references/scroll-choreography.md`](references/scroll-choreography.md) only when the brief asks for scroll story / cinematic pacing or the macro is Feature-stack / Narrative Workflow; [`references/dark-mode.md`](references/dark-mode.md) only when the user asks for both modes; [`references/data-viz.md`](references/data-viz.md) when the brief involves charts / data / dashboards or the macro is Stat-Led / Workbench; [`references/brand-truth.md`](references/brand-truth.md) when the brief names a real brand or company to build for; [`references/theme-axes.md`](references/theme-axes.md) § The rejection reading on every custom run, and in full when picking from the catalog; [`references/comp.md`](references/comp.md) only when signal 9 fired, at Step 5.5, never earlier; [`references/design-md.md`](references/design-md.md) only when the user asks to lock the system; [`references/preview-examples.md`](references/preview-examples.md) only if the Step 5 spec is not scaffolding enough.
**At the end only:** [`references/slop-test.md`](references/slop-test.md) strictly at Step 7 (pre-loading it costs thousands of tokens for nothing; `anti-patterns.md` is the pre-emit list); [`references/contract.md`](references/contract.md) at handoff; [`references/export-formats.md`](references/export-formats.md) only on `design.md` projects.
@@ -280,7 +281,7 @@ Then run the image-need table at [`references/hero-enrichment.md` § Image-need
- **Structure** · Workbench (last 3: Bento, Long Document, Manifesto) — genre modern-minimal
- **Direction** · Line-printer output (draw 4/7 · challengers declined · raise: tabular state discipline from the dealt instrument) · posture committed
-- **System** · pale greenbar paper · rust accent ~35 · Syne over IBM Plex Mono (worn coordinates clear; nearest occupied triple differs on display class)
+- **System** · pale greenbar paper · rust accent ~35 · Syne over IBM Plex Mono (clears Ledger on paper band, Grid on display face, Terminal on display class)
- **Chrome** · nav N13 (prev N5) · footer: a single justified colophon line
- **Hero** · Stage/H2 (prev Settled)
- **Section entry** · a hairline rule, repeated, plus one change of paper
@@ -290,7 +291,7 @@ Then run the image-need table at [`references/hero-enrichment.md` § Image-need
- **Slop test** · Floor 34/34 ✓ · Reflex 18 · Finish clean (run after Build)
```
-Name a catalog code where you took one, plain words where you designed it. **Direction** carries the draw plus the challenger verdicts and any raise; **System** carries the derived palette and pairing plus confirmation that the worn coordinates were cleared. SaaS deck runs add `**Deck** · -logos +worked-example`. Any page may add `**Signature** · <the one move>`.
+Name a catalog code where you took one, plain words where you designed it. **Direction** carries the draw plus the challenger verdicts and any raise; **System** carries the custom palette and pairing plus which catalog coordinates it cleared. SaaS deck runs add `**Deck** · -logos +worked-example`. Any page may add `**Signature** · <the one move>`.
**On the catalog fast path**, the two rows collapse into one, because the theme name already says the system: `- **Theme** · Coral (near-white paper · quiet neutrals · coral accent; differs from Newsprint on paper band + display style)`.
diff --git a/skills/hallmark/references/direction.md b/skills/hallmark/references/direction.md
index 1825b53..9e12a70 100644
--- a/skills/hallmark/references/direction.md
+++ b/skills/hallmark/references/direction.md
@@ -1,27 +1,28 @@
# Direction - deriving the world
-**This is the default path.** Loaded on every build that is not on the catalog fast path (see below). The direction is **made-to-measure for one brief**, written inline into the page's `:root`, never a permanent catalog entry. It spans two depths: **tuned** (a complete OKLCH palette + free-font pairing on Hallmark's structures) and **bespoke** (structure and composition designed from first principles too). One route, chosen depth.
+**This is the opt-in path.** A build takes it only when the user asks for one, most often by saying **custom** (or "derive it", "something bespoke", "no theme", "make me a world"). Everything else takes the catalog, which is Hallmark's default and its main road: see [`SKILL.md`](../SKILL.md) § 2.6. When this file does run, the direction is **made-to-measure for one brief**, written inline into the page's `:root`, never a permanent catalog entry. It spans two depths: **tuned** (a complete OKLCH palette + free-font pairing on Hallmark's structures) and **bespoke** (structure and composition designed from first principles too). One route, chosen depth.
**The freedom is the combination, never the floor.** Every constraint in [`color.md`](color.md), [`typography.md`](typography.md), and [`anti-patterns.md`](anti-patterns.md) still applies, and **every slop-test gate fires unchanged at every depth** (unpicked variants drafts alone defer the sweep to promotion, per [`verbs/variants.md`](verbs/variants.md)). The Step 5 Picks block surfaces the direction, posture, palette, and pairing in plain text before any code is emitted, so the user can redirect.
-Derivation is the default because **the model's own taste is an attractor**. Left alone, a model asked for "something unique" ships the same two or three looks per category, every time; its favourite is deterministic, so asking it to choose is asking it to repeat itself. The ritual below is a set of outside interventions that break that pull: named rejections, a deterministic draw, a scene the palette must obey, and a contract the build is audited against.
+The ritual exists because **the model's own taste is an attractor**. Left alone, a model asked for "something unique" ships the same two or three looks per category, every time; its favourite is deterministic, so asking it to choose is asking it to repeat itself. A user who asks for custom is asking to escape the catalog, and handing them the model's argmax instead is the same repetition wearing a different label. The steps below are outside interventions that break that pull: named rejections, a deterministic draw, a scene the palette must obey, and a contract the build is audited against.
-## The catalog fast path
+## When the catalog takes it back
-The 23 named themes are still here, and they are the right answer four times:
+Even after a custom ask, three things still route to the catalog, because they are stronger instructions:
-1. **The user names one.** "Use Newsprint", "give me that Ledger feel" is an instruction.
-2. **`--fast`.** Speed is the ask; the catalog is the pre-built answer.
-3. **A `design.md` or a real brand already exists.** Pre-flight found the system; inherit it. That branch never reaches this file.
-4. **Component scope.** One button does not need a derived world.
+1. **The user names a theme.** "Custom, something like Newsprint" is a theme pick with a mood note, not a derivation.
+2. **A `design.md` or a real brand already exists.** Pre-flight found the system; inherit it. That branch never reaches this file.
+3. **Component scope.** One button does not need a derived world.
-Anything else derives. Do not ask which; do not mention the catalog. A brief that says nothing gets a world of its own, and the coordinates it must not land on are in § D § The worn coordinates below; the catalog itself stays shut on a derived run.
+`--fast` on a custom ask is a contradiction; take the catalog and say so in one line.
+
+The coordinates a custom system must not land on are the catalog's own, in [`theme-axes.md`](theme-axes.md) § The rejection reading.
---
## § The ritual
-Runs on every derived build, both depths, in order, before any palette work. Each step produces one or two written lines in the reply; the whole ritual reads as a short paragraph of decisions, not a form.
+Runs on every custom build, both depths, in order, before any palette work. Each step produces one or two written lines in the reply; the whole ritual reads as a short paragraph of decisions, not a form.
### R.1 · Reflex check
@@ -64,7 +65,7 @@ The spent look can still be *earned* if the draw lands on a direction that genui
A pinned world pins the world, not its softest rendition: the pinned world's full material range stays in play, and a rendition that matches what any model ships for that world failed at execution, not selection.
-Note that the axis triples Hallmark's own catalog occupies are spent too, on every derived run. § D § The worn coordinates carries that list and the tolerance that defines a collision; the catalog files themselves are never opened for this.
+Note that the catalog's own twenty-three coordinates are spent too, on every custom run. [`theme-axes.md`](theme-axes.md) § The rejection reading carries that list and the tolerance that defines a collision.
### R.3 · The slate
@@ -92,7 +93,7 @@ The script prints a reproducible line: `draw: n/7 (seed <slug>·<date>·r0) · c
**Fusion, not costume.** A winning challenger supplies the form and its system grammar; the product supplies every fact, name, number, and claim; clarity wins every conflict. The page is the product wearing the challenger's system, never the challenger with the product's logo pasted on.
-**The raise.** A challenger that loses does not just vanish: the strongest loser donates the one discipline of its system grammar the drawn direction lacks (a state language, a navigation topology, a material rule), named in one line: *"raise: the mixing desk's per-function control colouring, applied to the pricing tiers."* Every derived run ships either a winning challenger or one named raise; a run with neither treated the deal as ceremony.
+**The raise.** A challenger that loses does not just vanish: the strongest loser donates the one discipline of its system grammar the drawn direction lacks (a state language, a navigation topology, a material rule), named in one line: *"raise: the mixing desk's per-function control colouring, applied to the pricing tiers."* Every custom run ships either a winning challenger or one named raise; a run with neither treated the deal as ceremony.
**Script-less fallback** (no Node, no shell): N = (letter count of the brief, spaces and punctuation excluded) mod 7, pick slate entry N + 1; each re-roll adds 3 (mod 7). Print the arithmetic so the pick is reproducible: *"draw fallback: 142 letters mod 7 = 2, entry 3."* Skip challengers, and stamp the seed as `seed: fallback-<letters>·<date>·r<n>`.
@@ -129,7 +130,7 @@ If a block reads like a mood ("elegant, premium feel"), the direction is not dec
### R.7b · What the stamp and the log carry
-The base stamp and the base log entry are specified in [`SKILL.md`](../SKILL.md) § 6 and § 2. A derived run extends both:
+The base stamp and the base log entry are specified in [`SKILL.md`](../SKILL.md) § 6 and § 2. A custom run extends both:
```css
/* Hallmark · macrostructure: <name or "bespoke: <one-line shape>"> · <hero archetype + knobs>
@@ -147,7 +148,7 @@ The base stamp and the base log entry are specified in [`SKILL.md`](../SKILL.md)
## § Bespoke depth
-Most derived runs are tuned. **Bespoke** is the deep end: the brief's structure itself is the ask and no catalog shape fits. The ritual runs identically (R.1 through R.7); bespoke changes what the build may drop:
+Most custom runs are tuned. **Bespoke** is the deep end: the brief's structure itself is the ask and no catalog shape fits. The ritual runs identically (R.1 through R.7); bespoke changes what the build may drop:
**It drops:** the fixed macrostructure + archetype catalog (compose the structure for the idea; a novel hero, nav, or section is encouraged when it serves the FORM block); the genre cluster routing; the diversification rotation (bespoke is a one-off, though it must not clone a recent bespoke run).
@@ -238,27 +239,7 @@ A derived system declares its diversification values explicitly so the Rotation
- **Accent hue band:** warm 10-60° · cool 200-300° · neutral (chroma < 0.05) · chromatic-other (sub-tag the anchor: `chromatic-moss ~140°`).
- **Posture** (fourth logged value): restrained · committed · full-palette · drenched.
-Before the triple is final, check it against the digest below. A triple that survives it is the thing the route was built to produce.
-
-### The worn coordinates
-
-The axis triples Hallmark's own catalog already occupies, deduplicated, with no theme names attached. **A constructed system that lands within tolerance of one has failed the reflex check** - not "is unoriginal", not "should be reconsidered": failed, the same way R.1 fails when the slate lands on the category default. **Within tolerance** means all three at once: same paper band; same display class at this digest's grain (`grotesk-sans` and `grotesk-heavy` are different classes, and `roman-serif`, `high-contrast-serif` and `slab-serif` are three); same accent band, or hues within **20°** of each other for two `chromatic-other` entries. Matching two of three is fine and common; it is the full triple that means you re-derived something that already exists.
-
-Occupied triples, grouped by paper band:
-
-- **Light** (the most worn band by far; a derived light-paper system has the least room, which is itself a nudge): high-contrast-serif / warm · roman-serif / warm · roman-serif / chromatic-green ~140-145 · slab-serif / warm · display-heavy / warm · display-heavy / chromatic-amber ~95 · display-condensed / warm · geometric-sans / warm · grotesk-sans / warm · grotesk-sans / cool · grotesk-heavy / warm ~28 and cool ~264 and chromatic-yellow ~95 · rounded-sans / chromatic-amber ~95 · classical-serif / cool ~265
-- **Mid**: grotesk-sans / cool · grotesk-heavy / cool
-- **Dark**: display-condensed-bold / warm · mono / chromatic-phosphor ~138 · geometric-sans / cool · geometric-sans / chromatic-teal ~172 · classical-serif / warm · grotesk-sans / chromatic-teal ~185, chromatic-sage ~150, and cool ~215 · pixel-display / warm ~25-72, cool ~242, chromatic ~90-115
-
-Three of those rows are multi-dial themes that occupy several accent bands at one paper-and-display coordinate, so check the whole row rather than its first value.
-
-**When you land there.** Move one axis, and prefer the one the brief cares least about - usually accent hue, occasionally paper band, rarely display class (the display carries the direction and is the most expensive thing to trade away). Then say it happened in one line: *"Landed on an occupied triple (light / grotesk-sans / cool); moved accent to chromatic-moss ~145."* Silence here is the failure mode, not the collision.
-
-**Siblings count as occupied too.** Rotation reads one project's `.hallmark/log.json`, so builds made side by side in separate projects (a batch of pages, a showcase, several briefs answered in one session) are blind to each other and converge without either noticing. When a run is one of several, treat the siblings' triples as occupied on top of this digest, and check the display *face* as well as the class: two pages sharing a paper band, a display family, and an accent family read as relatives even when their briefs have nothing in common.
-
-**Two exceptions, both narrow.** The user asking for a named theme's look is the catalog fast path, not a collision. And the draw can earn a coordinate: a direction that genuinely demands it (a line-printer draw wanting dark paper and a mono display) may keep it, with the same one-line argument R.2 requires for landing on a spent default; a draw that "happens to" land on an occupied triple twice in one project is not a draw, it is a preference.
-
-This is not as tight a constraint as it looks: three paper bands times a display class times an accent band leaves a derived system nearly the whole space, minus the couple dozen places Hallmark has already been. Maintenance: this digest is edited by hand whenever a theme enters or leaves `references/themes/`; the reminder lives in [`themes/README.md`](themes/README.md).
+Before the triple is final, check it against the rejection table in [`theme-axes.md`](theme-axes.md) § The rejection reading: the catalog's twenty-three coordinates, live on every custom run. A triple that survives it is the thing this route was built to produce.
---
diff --git a/skills/hallmark/references/genres/atmospheric.md b/skills/hallmark/references/genres/atmospheric.md
index 89aa442..a2d6442 100644
--- a/skills/hallmark/references/genres/atmospheric.md
+++ b/skills/hallmark/references/genres/atmospheric.md
@@ -6,6 +6,11 @@ For the AI-creative product page. Dark canvas with warm radial blooms, confident
Brief mentions any of: *AI tool, generative, music, video, image, voice, late-night, atmospheric, dark mode, expressive, creative tool, model playground, vibe-coded, dreamlike, nocturnal*. Also pick when the user names a *mood* that requires darkness (e.g. "moody", "cinematic", "after hours").
+## Themes that belong
+
+`Bloom` (canonical light-paper), `Midnight`, `Terminal`, `Aurora`, `Lumen`. Five themes; the rotation walks them when atmospheric is active.
+
+`Lumen` is the premium AI-tool register — Modal / Anthropic / Together / ElevenLabs / Cluely / Adept / Granola. One focal CSS artefact and a classical serif headline set upright and all-lowercase (Lumen ships no italic anywhere). **Two palette drops** (Night Foundry — dark amber-gold, emits; Day Foundry — light indigo, refracts). The only atmospheric theme with a serif display and the only one whose canvas treatment is one *built* artefact rather than two diffuse blooms.
## Voice
diff --git a/skills/hallmark/references/genres/editorial.md b/skills/hallmark/references/genres/editorial.md
index ee8e468..38aa0b4 100644
--- a/skills/hallmark/references/genres/editorial.md
+++ b/skills/hallmark/references/genres/editorial.md
@@ -8,6 +8,11 @@ This is what Hallmark looks like when no other genre signal fires. It is the sil
Default. Pick editorial when the brief does not name a specialised aesthetic — when the user said "a landing page for X" without telling you whether X is enterprise, atmospheric, or playful. Most briefs land here.
+## Themes that belong
+
+`Specimen`, `Newsprint`, `Atelier`, `Garden`, `Almanac`, `Studio`, `Riso`, `Sport`, `Brutal`, `Manifesto`, `Editorial`, `Carnival`, `Grid`. Thirteen themes - plenty of variety inside the genre. `Grid` is the Swiss / neo-grotesque exception here: rational, exposed-grid, near-monochrome with one signal ink spent on geometry, where the rest are serif-led.
+
+`Carnival` is the loud-maximalist editorial register — Dropout TV / Fly.io / Stones Throw / Third Man Records. Duo-tone accent system (mustard + oxblood), chunky variable display, decorative ornaments, hard-offset shadows. The loud sibling to Riso / Manifesto / Brutal.
## Voice
diff --git a/skills/hallmark/references/genres/modern-minimal.md b/skills/hallmark/references/genres/modern-minimal.md
index 7f2b5df..fb61fd9 100644
--- a/skills/hallmark/references/genres/modern-minimal.md
+++ b/skills/hallmark/references/genres/modern-minimal.md
@@ -6,6 +6,13 @@ For the polished enterprise / dev-tool / API page. Stripe / Linear / ElevenLabs
Brief mentions any of: *SaaS, enterprise, API, platform, developer tool, infra, B2B, dashboard, billing, Stripe-like, Linear-like, ElevenLabs-like, dev experience, ship fast*. Also pick when the user names a brand colour but the rest of the brief is restrained.
+## Themes that belong
+
+`Coral` (canonical) — warm-grey paper, single warm coral accent, Geist throughout, soft pill CTAs. The "Stripe-not-Linear" warmth.
+
+`Cobalt` — the cool dev-tool / API / docs register (the GitBook + Firecrawl school, executed **cobalt-on-light, not orange**). Cool engineered near-white paper, one electric cobalt signal accent, Space Grotesk display + Inter body + JetBrains Mono code, ruler-drawn hairlines, tight 6 px radii, a bordered ⌘K nav, and a live code/API request–response hero. The technical, instrument-panel sibling to Coral's warmth — the rotation walks Coral ⇄ Cobalt when modern-minimal is active.
+
+The two differ on every axis a glance registers: Coral is warm-grey + coral + Geist + pills; Cobalt is cool-white + electric blue + Space Grotesk/mono + tight-radius bordered controls. `Ledger` joins as the cluster's one dark option: a ruled navy account book (banded, columnar, or journal), Instrument Sans over tabular IBM Plex Mono, and two inks with one job each - teal for credits and matched rows, brass for debits and pending ones, never red. Totals close under a double rule and every figure states its as-of. Data-as-hero, the same restraint executed dark, which also gives the rotation a dark-vs-light lever inside the genre. It is a book, not a dashboard: no KPI card grids. Future themes can join too - anything monochrome or near-monochrome with an Inter-class sans display and a single restrained accent.
## Voice
diff --git a/skills/hallmark/references/genres/playful.md b/skills/hallmark/references/genres/playful.md
index c300cf4..aa1e5cb 100644
--- a/skills/hallmark/references/genres/playful.md
+++ b/skills/hallmark/references/genres/playful.md
@@ -6,6 +6,15 @@ For the consumer / friendly / onboarding-led page. Soft surfaces, mild colour, m
Brief mentions any of: *fun, consumer, casual, family, kids, friendly, approachable, onboarding-heavy, community, social, tactile-but-soft, post-Linear-soft*. Pick playful sparingly — most consumer briefs still belong to editorial (warm-paper, hand-set) unless the user explicitly asks for *softer* and *friendlier*.
+## Themes that belong
+
+`Hum` (vibrant, alive) is the genre's canonical theme — the post-Brilliant-alive register: multi-accent cream + pear + cyan + coral, mandatory motion, a single character moment. Pick it when the brief wants "feels alive in the room with you." For the quieter, more restrained end of friendly — "friendly but soft" rather than "alive" — reach instead for modern-minimal (Coral): a single low-chroma accent on warm paper, smooth easings, motion optional.
+
+`Arcade` joins the cluster as the retro-nostalgia end: an aubergine-black sheet under a real CRT stack (aperture grille, scanline, vignette, tight phosphor bloom), marquee lettering over a readable Chivo body, an ember + acid duo, and pixel type kept to the HUD. Playful and loud, but the re-drawn-chrome ban still holds (no fake OS windows, title bars, or monitor bezels; the retro comes from the screen texture and the lettering, not from furniture). Every Arcade page also carries one deliberately quiet, unbloomed instruction card, which is what makes the loud parts land. The two give the genre range: alive (Hum) and retro-loud (Arcade).
+
+For a warm, credible, friendly-but-quiet brief, reach for modern-minimal (Coral) or editorial (Garden, Almanac) rather than stretching playful to cover it.
+
+`Hum` is the catalog's only **rounded-sans-multi-accent** theme — it relaxes several playful defaults: bouncy spring easings are allowed (and canonical) on its primary CTA, accent chroma goes higher than 0.16, and motion is mandatory not optional. It answers a specific brief: a learning platform for curious adults, a daily-curiosity app, a habit tracker with character — products that should feel warm and alive, not merely tidy.
## Voice
diff --git a/skills/hallmark/references/hero-enrichment.md b/skills/hallmark/references/hero-enrichment.md
index 48bfe2c..6e8fc93 100644
--- a/skills/hallmark/references/hero-enrichment.md
+++ b/skills/hallmark/references/hero-enrichment.md
@@ -68,7 +68,7 @@ If the brief contains explicit visual cues, pick from this map:
• "bakery", "kitchen", "café", "atelier" + craft brief → E5 custom illustration (Tier B SVG)
• "agency", "studio", "portfolio" → E8 photography or no enrichment
• "manifesto", "essay", "book", "letter" → no enrichment (typography only)
- • a restraint-led system (quiet-minimal direction/theme) → no enrichment (the restraint IS the design)
+ • Coral theme picked → no enrichment (the theme IS restraint)
Else if the brief is genuinely ambiguous, ask one question:
"Want me to add a demo video, an illustration, or keep it
diff --git a/skills/hallmark/references/theme-axes.md b/skills/hallmark/references/theme-axes.md
index 9987d7a..30278e7 100644
--- a/skills/hallmark/references/theme-axes.md
+++ b/skills/hallmark/references/theme-axes.md
@@ -1,8 +1,11 @@
-# Theme axes - the catalog Rotation lookup
+# Theme axes - the Rotation lookup, and the rejection table
-The three diversification axes for every catalog theme, derived from the canonical token values. **This file is read on the catalog fast path only.** The Rotation block in [`SKILL.md`](../SKILL.md) reads it to pick the next theme: two consecutive themes must differ on at least one axis, and two candidates matching on two of three means pick a more distant one.
+The three diversification axes for every catalog theme, derived from the canonical token values. This table is read two ways depending on the route, and both readings are live:
-A derived run never opens this file. The anonymous digest of these coordinates lives in [`direction.md`](direction.md) § D § The worn coordinates; the two are maintained together by hand whenever a theme enters or leaves the catalog.
+- **As a lookup (catalog route).** The Rotation block in [`SKILL.md`](../SKILL.md) reads it to pick the next theme; two consecutive themes must differ on at least one axis.
+- **As a rejection table (custom route).** A constructed system declares its own axes per [`direction.md`](direction.md) § D, and this table is the list of triples it must not land on. See § The rejection reading below.
+
+The second reading is what the 23 themes are *for* on a custom run, where nothing picks a catalog theme. They stop being destinations and become the twenty-three most-worn coordinates in Hallmark's own space: precisely what [`direction.md`](direction.md) § R.2 means by house defaults, with values attached.
Bands: paper **dark** < 30% L · **mid** 30-85% · **light** > 85%. Accent: **warm** 10-60° · **cool** 200-300° · **neutral** chroma < 0.05 · **chromatic-other** anything else (sub-tag the hue).
@@ -36,4 +39,31 @@ When two candidate themes match on two of the three axes, pick a more distant on
---
+## The rejection reading
+
+**A constructed system that lands within tolerance of a catalog row has failed the reflex check.** Not "is unoriginal", not "should be reconsidered": failed, the same way R.1 fails when the slate lands on the category default. The whole point of the custom route is that it goes somewhere the catalog does not already stand.
+
+**Within tolerance** means all three of these at once:
+
+1. **Same paper band** (dark / mid / light), and
+2. **Same display class** at the table's grain - `grotesk-sans` and `grotesk-heavy` are different classes, and `roman-serif`, `high-contrast-serif` and `slab-serif` are three, and
+3. **Same accent band**, or for two `chromatic-other` entries, hues within **20°** of each other.
+
+Matching two of the three is fine and common: a light paper with a roman serif and a teal accent collides with nothing. It is the full triple that means you re-derived a theme that already exists.
+
+**When you land there.** Move one axis, and prefer the one the brief cares least about - usually accent hue, occasionally paper band, rarely display class (the display carries the direction and is the most expensive thing to trade away). Then say it happened in one line: *"Landed on Cobalt's triple (light / grotesk-sans / cool ~250); moved accent to chromatic-moss ~145."* Silence here is the failure mode, not the collision.
+
+**Two exceptions, both narrow.**
+
+- **The user asked for it.** "Make it look like Terminal", "we want that Ledger feel" is an instruction, not a reflex. Build it, and record `axes: <triple> (Terminal, by request)` in the stamp so a later audit does not read it as drift.
+- **The draw earned it.** A direction from R.4 that genuinely demands the coordinate - a line-printer draw wanting a dark paper with a mono display - may keep it, but only with the same one-line argument R.2 requires for landing on a spent default. A draw that "happens to" land on a catalog triple twice in a project is not a draw, it is a preference.
+
+**Siblings count as occupied too.** Rotation reads one project's `.hallmark/log.json`, so pages built side by side in separate projects (a batch, a showcase, several briefs answered in one session) are blind to each other and converge without either noticing. When a run is one of several, treat the siblings' triples as occupied on top of this table, and check the display *face* as well as the class: two pages sharing a paper band, a display family, and an accent family read as relatives even when their briefs have nothing in common.
+
+**This is not as tight a constraint as it looks.** Three paper bands times a display class times an accent band leaves a constructed system nearly the whole space, minus the twenty-three places Hallmark has already been.
+
+---
+
+---
+
The rules governing what a theme *file* may and may not carry live in [`themes/README.md`](themes/README.md). Read that only when writing or editing a theme, never when building a page.
diff --git a/skills/hallmark/references/themes/README.md b/skills/hallmark/references/themes/README.md
index 048a5c2..f581c9f 100644
--- a/skills/hallmark/references/themes/README.md
+++ b/skills/hallmark/references/themes/README.md
@@ -25,6 +25,6 @@ A theme file **may not** carry:
- an eyebrow, in any form (gate 54)
- counts that fix a layout ("always three cells, never two, never four")
-**When a theme enters or leaves this directory**, two lookups are edited by hand in the same change: the axes table in [`../theme-axes.md`](../theme-axes.md) (the catalog Rotation lookup) and the worn-coordinates digest in [`../direction.md`](../direction.md) § D (the anonymous triples a derived run must clear). Neither updates itself.
+**When a theme enters or leaves this directory**, edit the axes table in [`../theme-axes.md`](../theme-axes.md) by hand in the same change. It is both the catalog Rotation lookup and the rejection table a custom run must clear, and it does not update itself.
Where a theme genuinely invented something structural worth keeping, it belongs in the Library as an **optional** entry any brief can reach for, never as a thing this theme's builds must contain. The `## Build hint` block in each file is a token sketch, not a page: `:root` values and the two or three face rules that make the theme recognisable, and nothing that names a page part.