Skip to content

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

CSS

Catalog and exemplars stop contradicting the floor they teach

Youssef563297f20cf8
diff --git a/skills/hallmark/SKILL.md b/skills/hallmark/SKILL.md
index b2dcf1d..1cfc72e 100644
--- a/skills/hallmark/SKILL.md
+++ b/skills/hallmark/SKILL.md
@@ -44,7 +44,7 @@ Everything above the Floor is a **Reflex** gate: a default a model falls into, w
6. Build: the hero first, then the page; stamp, `tokens.css`, log.
7. Sweep: sloplint with render, the judged gates, the fresh-context review.
-Codex CLI and OpenCode read [`references/flow.md`](references/flow.md) § Harnesses before Step 0; any other harness runs this file with sequential tool calls and questions in chat.
+Codex CLI and OpenCode read [`references/flow.md`](references/flow.md) § Harnesses first; other harnesses run this file as written.
### 0. Pre-flight
@@ -66,7 +66,7 @@ Skipped fields are opt-outs: infer them, state the inferences in one line at the
### 2. Shape
-**Material first.** Before the shape, write the inventory in one line: *real* (every concrete thing the brief and the project supply: the name, the claim, numbers, places, dates, inputs and outputs, images), *slots* (what the user will hand over later), *absent* (every proof the page will not have: logos, quotes, metrics nobody gave). The shape follows it: shapes built on screenshots (Bento, Workbench, Feature Stack) need two real visuals or the user's "leave slots"; with neither, choose a shape that carries type and facts (Long Document, Letter, Index-First, Manifesto, a spec sheet). Pages read as generated when they have nothing to show and pretend otherwise.
+**Material first.** Before the shape, write the inventory in one line: *real* (every concrete thing the brief and the project supply: the name, the claim, numbers, places, dates, inputs and outputs, images), *slots* (what the user will hand over later), *absent* (every proof the page will not have: logos, quotes, metrics nobody gave). The shape follows it: shapes built on screenshots (Bento, Workbench, Feature Stack) need two real visuals or the user's "leave slots"; with neither, choose a shape that carries type and facts (Long Document, Letter, Index-First, Manifesto, a spec sheet built on `components/f3-tabular-spec-sheet.md`). Pages read as generated when they have nothing to show and pretend otherwise.
Decide the page's shape, how it opens, how sections separate, what the nav and footer do, how tall the hero stands and what carries it. You are designing, not filling a form. The catalogs exist for when you want a starting point: 21 page shapes in [`references/macrostructures.md`](references/macrostructures.md), navs, footers and section archetypes in [`references/component-cookbook.md`](references/component-cookbook.md), enrichment in [`references/hero-enrichment.md`](references/hero-enrichment.md). Take a named shape and load only that one file; never read a whole catalog.
@@ -125,12 +125,12 @@ On signal 9, [`references/comp.md`](references/comp.md) runs here: two comps of
Emit code that satisfies the theme and the shape. Always:
-- **Start from the scaffold.** `node <skill-dir>/scripts/theme.mjs scaffold <slug>` (`--custom` on a derived run) writes `tokens.css` with the theme's tokens and the shared scale, and prints the base rules the Floor already decided under a stamp skeleton. Paste them, fill the stamp, and write only the page.
-- **Read the exemplar** for the genre, `references/exemplars/<genre>.html`, once: a finished page in another theme that passes every gate. Take how its stamp, tokens, slots, states and openings are written; never its shape, theme or copy. Skip it when it is in your theme.
+- **Start from the scaffold.** `node <skill-dir>/scripts/theme.mjs scaffold <slug>` (with the deal's `--dealt`; `--custom` on a derived run) writes `tokens.css` with the theme's tokens and the shared scale, and prints the base rules the Floor already decided under a stamp skeleton. Paste them, fill the stamp, and write only the page.
+- **Read the exemplar** for the genre, `references/exemplars/<genre>.html`, once: a finished page in another theme that passes every gate. Take how its stamp, tokens, slots, states and openings are written; never its shape, theme or copy. Skip it if it is in your theme.
- **Hero first.** Write the nav and the hero, run `node <skill-dir>/scripts/sloplint.mjs <file> --render --stage hero` (the fold at three widths, the hero's words, the visual's place, four first-screen shots), then the hero review in fresh context (`gates.md` § 6). Build the sections only once the hero ships: a hero rewrite after eight sections exist costs eight sections.
- **One idea per screen.** Hero: headline (seven words or fewer, 50 characters or fewer), one sentence (twelve words or fewer), one or two actions. A section: a heading of three to five words, at most one line, then its object (a slot, a figure, a drawn thing, a list of four or fewer, a table of five rows or fewer). Four to eight sections, footer included; 450 visible words at most, fewer when the brief has less to say. Never pad to a count.
- **Show, do not describe.** On a product page with material or "leave slots": at least two `data-slot` containers, the hero visual and a demo strip; with neither, the page shows what is real (Step 2). The user's images fill them; otherwise a designed placeholder in the theme's colours with a corner label (`craft.md` § Demo slots). Never a grey box, never a fake screenshot with invented figures.
-- **The fold.** The hero is the first screen and only the first screen at 1440 x 900 and 1920 x 1080, its visual beside the text (centres within 60px, 48 to 120px apart), never pinned in a corner; a Banner hero shares it with the first section.
+- **The fold.** The hero is the first screen and only the first screen at 1440 x 900 and 1920 x 1080, its visual beside the text (centres within 60px, 48 to 120px apart), never pinned in a corner; a Banner shares it with the first section.
- **Room.** 120px or more between sections at desktop, varied; 32 to 48px from a heading to its content; 24 to 40px between grid items. More space above a heading than below it.
- **Page invariants.** One primary button style, one container width, one column gap for every multi-column section below the hero, one radius per nesting level, and never more centred heading groups than left-aligned ones. A subhead over 120 characters is set left-aligned.
- **Type.** The theme's faces, two families (three with one outlier role); display tracking and leading per `craft.md` § 1; body 16px or more at 1.5 to 1.65, 45 to 75ch; heads roman. Labels per Floor 9, never mono unless mono is the material (64). A head is one weight and one colour throughout; the accented word is a tell (38iii).
@@ -160,7 +160,7 @@ then any `waive` and `answered` lines, then a custom run's direction contract. E
### 7. Sweep
-1. `node <skill-dir>/scripts/sloplint.mjs <files> --genre <genre> --render` (add `--scope component` on a component; in a framework project with a dev server running, add `--url http://localhost:<port>/<route>`). Fix every FAIL, re-run until clean. The render tier writes the screenshots you need next; do not run Chrome by hand.
+1. `node <skill-dir>/scripts/sloplint.mjs <files> --genre <genre> --render` (add `--scope component` on a component; in a framework project with a dev server running, add `--url http://localhost:<port>/<route>`). Fix every FAIL, re-run until clean. The render tier writes the screenshots; never run Chrome by hand.
2. Load [`references/gates.md`](references/gates.md) § 5 and walk the J and R/J gates. Confirm or dismiss every WARN. Fix every open Floor finding; fix or waive every Reflex one; answer every Finish one.
3. Review in fresh context per `gates.md` § 6, which lists its inputs. Act on its first word (`recapture`, `rebuild`, `fix`, `ship`). Two rounds is the ceiling.
4. Close with the material ask: every slot, its size and what belongs there, then the one piece of material that would most improve the page ("two screenshots of the import screen would replace both demo placeholders").
diff --git a/skills/hallmark/references/component-cookbook.md b/skills/hallmark/references/component-cookbook.md
index 69cae36..2a52ed4 100644
--- a/skills/hallmark/references/component-cookbook.md
+++ b/skills/hallmark/references/component-cookbook.md
@@ -12,7 +12,7 @@ The same page shape (say, Bento Grid) can be built from many combinations of the
### Heroes
-- **H1 · Marquee.** A single statement fills the fold. No subhead; the primary action is the fold's one other visible control. [`components/h1-marquee.md`](components/h1-marquee.md)
+- **H1 · Marquee.** A single statement fills the fold; one sentence and the primary action sit small at its foot. [`components/h1-marquee.md`](components/h1-marquee.md)
- **H2 · Split.** Headline, one sentence and the action on one side; one visual on the other, beside the text: a capture plate, a clipped demo video, a built illustration or a photograph, each with its enrichment recipe. [`components/h2-split-diptych.md`](components/h2-split-diptych.md)
- **H3 · Quote led.** A pull-quote with attribution is the hero, both the user's material. The headline is borrowed credibility. [`components/h3-quote-led.md`](components/h3-quote-led.md)
- **H4 · Stat led.** One figure the user gave, with its unit, is the hero. A small qualifier line below says what it means. [`components/h4-stat-led.md`](components/h4-stat-led.md)
diff --git a/skills/hallmark/references/components/c2-inline-form-as-cta.md b/skills/hallmark/references/components/c2-inline-form-as-cta.md
index 75a1dac..4034acd 100644
--- a/skills/hallmark/references/components/c2-inline-form-as-cta.md
+++ b/skills/hallmark/references/components/c2-inline-form-as-cta.md
@@ -4,8 +4,8 @@ The CTA is the form: one email field and a verb button on the same rule. No sepa
*Not:* a two-step flow ("Continue" is for a second step); a field and a button sharing one border (`craft.md` § 9); a button that says "Submit" (`craft.md` § 6).
```html
-<form class="cta-form" action="/subscribe" method="post">
- <label for="email" class="visually-hidden">Email address</label>
+<form class="cta-form" method="post" data-endpoint="">
+ <label for="email">Email address</label>
<input id="email" name="email" type="email" autocomplete="email" placeholder="[email protected]" required />
<button type="submit">Send the letter</button>
<p class="cta-form__help" aria-live="polite"></p>
@@ -13,12 +13,15 @@ The CTA is the form: one email field and a verb button on the same rule. No sepa
```
```css
.cta-form { display: grid; grid-template-columns: minmax(0, 1fr) auto; column-gap: var(--space-md); align-items: end; border-bottom: var(--rule-hair) solid var(--color-ink); }
+.cta-form label { grid-column: 1 / -1; font-size: var(--text-sm); color: var(--color-muted); }
.cta-form input { min-height: 44px; padding: var(--space-sm) 0; background: none; border: 0; color: var(--color-ink); }
.cta-form input:focus-visible { outline: 2px solid var(--color-focus); outline-offset: -2px; }
.cta-form button { min-height: 44px; padding: var(--space-sm) var(--space-md); }
.cta-form__help { grid-column: 1 / -1; min-height: 1lh; margin: 0; font-size: var(--text-sm); color: var(--color-muted); }
```
+`data-endpoint` stays empty until the brief gives the endpoint; until then the form validates and never prints a success (`craft.md` § 9, gate 70).
+
## Knobs
- Fields: one · two (email and name)
@@ -27,4 +30,4 @@ The CTA is the form: one email field and a verb button on the same rule. No sepa
## Mobile
-- Below 40rem: field and button stack, both full width; the label shows above the field.
+- Below 40rem: field and button stack, both full width, under the label.
diff --git a/skills/hallmark/references/components/f4-step-sequence.md b/skills/hallmark/references/components/f4-step-sequence.md
index de735f6..7d716f9 100644
--- a/skills/hallmark/references/components/f4-step-sequence.md
+++ b/skills/hallmark/references/components/f4-step-sequence.md
@@ -12,7 +12,7 @@ Numbered stages flow vertically: a heading, one paragraph, sometimes a small vis
```css
.steps { list-style: none; counter-reset: stage; margin: 0; padding: 0; display: grid; gap: var(--space-xl); }
.steps > li { counter-increment: stage; }
-.steps > li > h3::before { content: counter(stage) ". "; font-family: var(--font-body); font-weight: 400; }
+.steps > li > h3::before { content: counter(stage) ". "; }
```
## Knobs
diff --git a/skills/hallmark/references/components/ft4-dense-typographic.md b/skills/hallmark/references/components/ft4-dense-typographic.md
index 54eae8a..4e93468 100644
--- a/skills/hallmark/references/components/ft4-dense-typographic.md
+++ b/skills/hallmark/references/components/ft4-dense-typographic.md
@@ -5,12 +5,13 @@ One block of text, credits, references, licence and address, in the body face a
```html
<footer class="foot-dense">
- <p>Set in the display and body faces named in the stamp. MIT licensed. 137 Marlow Street, 2026.</p>
+ <div class="foot-dense__inner"><p>Set in the display and body faces named in the stamp. MIT licensed. 137 Marlow Street, 2026.</p></div>
</footer>
```
```css
-.foot-dense { padding: var(--space-2xl) var(--gutter); max-width: 65ch; font-size: var(--text-sm); color: var(--color-muted); line-height: 1.6; }
-.foot-dense p { margin: 0; }
+.foot-dense { padding-block: var(--space-2xl); }
+.foot-dense__inner { max-width: var(--container); margin-inline: auto; padding-inline: var(--gutter); }
+.foot-dense p { max-width: 65ch; margin: 0; font-size: var(--text-sm); color: var(--color-muted); line-height: 1.6; }
```
## Knobs
diff --git a/skills/hallmark/references/components/h1-marquee.md b/skills/hallmark/references/components/h1-marquee.md
index 3479f61..06462d3 100644
--- a/skills/hallmark/references/components/h1-marquee.md
+++ b/skills/hallmark/references/components/h1-marquee.md
@@ -12,7 +12,7 @@ A single statement fills the fold; one sentence and one action sit small at its
```css
.hero-marquee { min-height: 80dvh; display: grid; align-content: end; gap: var(--space-lg); padding: 0 var(--gutter) var(--space-2xl); }
.hero-marquee__foot { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: baseline; gap: var(--space-md); max-width: 60rem; }
-.display-xxl { font-size: clamp(3.5rem, 8vw, 7rem); line-height: 1; letter-spacing: -0.03em; max-width: 12ch; overflow-wrap: break-word; min-width: 0; text-wrap: balance; }
+.display-xxl { font-size: clamp(4rem, 9vw, 12rem); line-height: 1; letter-spacing: var(--tracking-display); max-width: 12ch; overflow-wrap: break-word; min-width: 0; text-wrap: balance; }
```
## Knobs
diff --git a/skills/hallmark/references/components/n12-banner-retract.md b/skills/hallmark/references/components/n12-banner-retract.md
index 53d71b8..1579f34 100644
--- a/skills/hallmark/references/components/n12-banner-retract.md
+++ b/skills/hallmark/references/components/n12-banner-retract.md
@@ -1,7 +1,7 @@
### N12 · Announcement banner and retracting nav
A coloured banner stacked above one real nav. Scrolling down, the banner slides up out of view and the bar docks to the top; scrolling up brings it back. A dismiss control removes it for good and zeroes its height so no gap remains. The banner's colour is what stops it reading as two navs.
*Use when:* there is a real, time-bound announcement (a launch, a sale, shipping) worth a strip over a product or commerce page.
-*Not:* a second row of links (the two-bar smell this exists to avoid); a static strip that never moves. One line, one link, one dismiss; no glyph before the text (63); the height is never animated, the whole `.nav` translates.
+*Not:* a second row of links (the two-bar smell this exists to avoid); a static strip that never moves (on a theme that keeps still, the bar simply scrolls away with the page instead). One line, one link, one dismiss; no glyph before the text (63); the height is never animated, the whole `.nav` translates.
```html
<header class="nav" id="nav">
diff --git a/skills/hallmark/references/craft.md b/skills/hallmark/references/craft.md
index 12ce1bb..33484bc 100644
--- a/skills/hallmark/references/craft.md
+++ b/skills/hallmark/references/craft.md
@@ -13,7 +13,7 @@ Type carries the page. Two families: a display face and a body face. A third is
- **Labels, captions, table heads, meta, tags, chips, nav links:** the body face, a step smaller, sentence case, untracked (67). Never uppercase, never small caps, never letter-spaced. Mono only when the content is code, a figure or a measurement, or when mono is the theme's material (64). Capitals belong to a wordmark and to a theme whose display voice is uppercase; there a control may follow the display's case at 0.04em of tracking or less.
- **Headline sizing by copy length.** Count the rendered `h1`: 20 characters or fewer, full display (a single word may grow to 7rem); 21 to 50, display; 51 to 90, one step down (`--text-display-s`) or split at the sense break with `<br>`; over 90, rewrite. Self-written headlines aim for seven words and 50 characters.
- **Heading measure rides on the element**, in `ch`: display ~20ch, display-s ~24ch, 4xl ~30ch, 3xl ~35ch, 2xl ~40ch, xl ~45ch. Never a `max-width` on the heading group's wrapper.
-- **Required:** `font-display: swap`; fallback metrics with `size-adjust` and the override properties; `font-variant-numeric: tabular-nums` on any figures that compare; `text-wrap: balance` on heads, `pretty` on ledes and body; curly quotes, a true ellipsis, a non-breaking space inside unit pairs (`10 MB`, `⌘ K`) in a proportional face (in mono the unit sits outside the mono span or takes a plain space, since a mono space is a full cell). No `--` and no em or en dash anywhere in rendered copy; a comma, a colon or a full stop does the work.
+- **Required:** `font-display: swap`; a fallback stack of the same build (a grotesk falls back to `system-ui`, a serif to Georgia), with `size-adjust` and the overrides only where the face's metrics are published, never guessed; `font-variant-numeric: tabular-nums` on any figures that compare; `text-wrap: balance` on heads, `pretty` on ledes and body; curly quotes, a true ellipsis, a non-breaking space inside unit pairs (`10 MB`, `⌘ K`) in a proportional face (in mono the unit sits outside the mono span or takes a plain space, since a mono space is a full cell). No `--` and no em or en dash anywhere in rendered copy; a comma, a colon or a full stop does the work.
- **Wordmark.** May take a different face from the body; on tone-rich themes it should. Collapse to one family only when the body voice is the brand (a letter, a manifesto, a long document).
- **Load only the weights you use.** Never synthesise bold or italic.
@@ -75,6 +75,7 @@ Every posture, every hero:
## 5. Motion
+- **Who decides.** The theme's Motion section; a shape's reveal runs only where the theme allows one, and the genre's default holds only where the theme is silent.
- **Only `transform` and `opacity`** (10). Blur, `clip-path`, mask and shadow may join when they stay smooth on the element alone.
- **Three easings, tokenised:** `--ease-out: cubic-bezier(0.16, 1, 0.3, 1)` for things arriving, `--ease-in: cubic-bezier(0.7, 0, 0.84, 0)` for things leaving, `--ease-in-out: cubic-bezier(0.65, 0, 0.35, 1)` for toggles. The browser's `ease` and `linear` (outside progress) read as uncrafted; overshoot on UI state is dated (12).
- **Three durations:** `--dur-micro` 120ms (press, tick, colour), `--dur-short` 220ms (hover, tooltip, menu), `--dur-long` 420ms (modal, drawer, accordion, page reveal). Exits run 60 to 75% of the enter. Stagger 30 to 50ms between rows, 60 to 100ms between blocks, 500ms total, one-shot, never re-fired on scroll.
@@ -93,6 +94,7 @@ Words are design material. Specific verbs (`Save changes`, never `Submit`); labe
- **Openers.** Name the place, the date, the vertical, the number the user gave, the input the product reads. Refuse the verb-less claim. Never *Built for the modern team*, *Unleash*, *Where A meets B*, *Empower*, *Reimagine*, *Supercharge*, *seamless*, *robust*, *effortless*, *next-generation*, *world-class*, *In today's landscape* (19). The rebuttal cadence (*Not a feature. A platform.*) is fine once and a tic three times.
- **Buttons:** the verb of the action. `Continue` only as the secondary step of a flow. **Errors:** what happened (past tense), why if known, what to do (imperative); no *Oops*, no exclamation marks, no humour in a frustration path. **Empty states:** one line naming what is empty, one on why it matters, one action. **Loading:** spinner alone under 2s, plus *Loading…* past it, plus honest progress past 10s.
- **Never** placeholder people (Jane Doe), startup clichés (Acme, Nexus), *Click here*, *Enter your email below*, *Quietly trusted by*, a version string in marketing copy, or a number the user did not give (46a).
+- **Sample data** inside a code surface or a slot's sketch uses the reserved `example.com`, the field names the brief gives and values that read as samples (`Example Domain`, a word count that matches the text shown); never a figure a visitor could take as a claim.
- **Punctuation is typeset:** curly quotes, `…`, a proper apostrophe, no `--`, no em or en dash (a comma, a colon, a full stop or parentheses instead), non-breaking spaces before units. Periods on every standalone sentence, none on list items, consistently.
## 7. Opening a section
@@ -103,7 +105,7 @@ The reflex is a small caps label above the heading, and the reflex is the tell (
2. **The heading announces itself.** Move the subject into its first two words. Usually the best move; the label existed because the heading was vague.
3. **A lead-in inside the paragraph**, in a heavier weight, never on its own line.
4. **A drop cap.** One per page, first paragraph only.
-5. **A rule that does more than rule**: hairline, fleuron, double rule, colour edge, or pure gap; one divider language down the whole page.
+5. **A rule that does more than rule**: hairline, fleuron, double rule, colour edge, or pure gap; one divider language down the page, varied in weight and placement from seam to seam (9).
6. **A numeral at graphic scale** (8 to 18rem), one per page, only when the number is real (an issue, a year, a version, a chapter).
7. **A real `<ol>`** with `counter()` when the sequence is genuine.
8. **A caption below** the content instead of above it: a plate in a catalogue, not a slide title.
diff --git a/skills/hallmark/references/enrichment/hp4-decorative-numeral.md b/skills/hallmark/references/enrichment/hp4-decorative-numeral.md
index d2a4872..d90cfc2 100644
--- a/skills/hallmark/references/enrichment/hp4-decorative-numeral.md
+++ b/skills/hallmark/references/enrichment/hp4-decorative-numeral.md
@@ -1,6 +1,6 @@
### HP4 · Decorative numeral
-A huge edition number, year or chapter set at display scale in a hero corner. The numeral means something: issue 22, year 2026, chapter 03, version 0.8. Roman, never italic: a display-scale figure is display type, and an italic one is an italic display system (38ii) with everything that entails.
+A huge edition number, year or chapter set at display scale behind or beside the hero's head, never as the hero's visual pinned in a corner. The numeral means something: issue 22, year 2026, chapter 03, version 0.8. Roman, never italic: a display-scale figure is display type, and an italic one is an italic display system (38ii) with everything that entails.
*Use when:* the page has a real edition, issue, chapter or version semantic: magazines, journals, archived work, dated essays.
*Avoid when:* the numeral has no anchor. A random "42" in the corner is decoration text (66). If you cannot name what the number is, drop it.
diff --git a/skills/hallmark/references/exemplars/atmospheric.html b/skills/hallmark/references/exemplars/atmospheric.html
index 510f26c..602944f 100644
--- a/skills/hallmark/references/exemplars/atmospheric.html
+++ b/skills/hallmark/references/exemplars/atmospheric.html
@@ -250,7 +250,7 @@ body::after { content: ""; position: fixed; top: 0; right: 0; bottom: 0; left: 0
<h2 id="tasting-title">When’s the next tasting?</h2>
<p>A few bottles opened side by side, once a month, at <span class="price">£25</span>. Leave your email and we’ll send the date.</p>
</div>
-<form class="signup" action="#" method="post" novalidate>
+<form class="signup" action="#" method="post" data-endpoint="" novalidate>
<label for="t-email">Email address</label>
<div class="signup__row">
<input id="t-email" name="email" type="email" autocomplete="email" required>
diff --git a/skills/hallmark/references/exemplars/editorial.html b/skills/hallmark/references/exemplars/editorial.html
index 655ea16..64d07f0 100644
--- a/skills/hallmark/references/exemplars/editorial.html
+++ b/skills/hallmark/references/exemplars/editorial.html
@@ -278,7 +278,7 @@ main { counter-reset: stage; }
<h2 id="order-title">Start an order</h2>
<p>Tell us the cloth, the metres and the room. We write back with a start date.</p>
</div>
-<form class="order__form" action="#order" method="post">
+<form class="order__form" action="#order" method="post" data-endpoint="">
<div class="field">
<label for="o-name">Your name</label>
<input id="o-name" name="name" type="text" autocomplete="name" required aria-describedby="o-name-help">
diff --git a/skills/hallmark/references/exemplars/playful.html b/skills/hallmark/references/exemplars/playful.html
index 7666e73..fc14c9e 100644
--- a/skills/hallmark/references/exemplars/playful.html
+++ b/skills/hallmark/references/exemplars/playful.html
@@ -257,7 +257,7 @@ button, input, select, textarea { font: inherit; }
<h2 class="band__title" id="sizes-title">Four sizes, from £12</h2>
<p>Tap a size to see how full the crate gets.</p>
</div>
-<form class="card box" action="#" method="post">
+<form class="card box" action="#" method="post" data-endpoint="">
<fieldset class="box__pick">
<legend>Box size</legend>
<label class="chip"><input type="radio" name="size" value="1" checked>Small</label>
@@ -321,8 +321,10 @@ button, input, select, textarea { font: inherit; }
const box = document.querySelector('.box');
if (box) box.addEventListener('submit', (e) => {
e.preventDefault();
-const size = box.querySelector('input[name="size"]:checked');
-box.querySelector('.box__status').textContent = (size ? size.parentElement.textContent.trim() : 'Your') + ' box chosen. The first one arrives on a Thursday.';
+const status = box.querySelector('.box__status');
+const endpoint = box.dataset.endpoint;
+if (!endpoint) { status.textContent = 'Ordering opens soon. Nothing was sent.'; return; }
+fetch(endpoint, { method: 'POST', body: new FormData(box) }).then((r) => { status.textContent = r.ok ? 'Your box is ordered. The first one arrives on a Thursday.' : 'That did not go through. Try again in a minute.'; }).catch(() => { status.textContent = 'That did not go through. Try again in a minute.'; });
});
})();
window.hallmarkSlots = (m) => { for (const [k, v] of Object.entries(m)) { const s = document.querySelector(`[data-slot="${k}"]`); if (!s) continue; const im = new Image(); im.src = typeof v === 'string' ? v : v.src; im.alt = (typeof v === 'object' && v.alt) || s.dataset.alt || ''; s.prepend(im); } };
diff --git a/skills/hallmark/references/macrostructures.md b/skills/hallmark/references/macrostructures.md
index 1950fb3..db0a1de 100644
--- a/skills/hallmark/references/macrostructures.md
+++ b/skills/hallmark/references/macrostructures.md
@@ -15,7 +15,7 @@ Twenty-one named landing-page shapes. Each is a complete fingerprint (heading pl
- **07 · Manifesto.** Polemical large type. The page tells the reader what to believe before it tells them what to buy. [`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 quote the user supplied, with its attribution. The headline is someone else's voice. [`macrostructures/09-quote-led.md`](macrostructures/09-quote-led.md)
-- **10 · Specimen.** Large serif display, asymmetric spans, hairline rules, a typographic CTA, generous whitespace. Editorial and foundry briefs only. [`macrostructures/10-specimen.md`](macrostructures/10-specimen.md)
+- **10 · Specimen.** Large serif display, asymmetric spans, hairline rules, a typographic CTA, generous whitespace. Only for briefs about type, publishing or writing (a foundry, a journal, a press); the editorial genre alone does not qualify. [`macrostructures/10-specimen.md`](macrostructures/10-specimen.md)
- **11 · Catalogue.** Uniform grid of variations of the same thing: typefaces, palettes, 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. 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. Navigation as design. [`macrostructures/13-index-first.md`](macrostructures/13-index-first.md)
@@ -71,7 +71,7 @@ For non-SaaS work (Editorial, Manifesto, Letter, Long Document, Quote-Led) this
0. **Read the material inventory** (SKILL.md Step 2). A shape built on screenshots or figures needs them, real or as slots the user asked for; with neither, pick a shape that carries type and facts.
1. **Read the brief.** Note any words that strongly signal one shape ("data heavy", "tell a story", "a list of links", "many small features", "personal note").
2. **Read `.hallmark/log.json`** (newest first) and the `shape:` field of any Hallmark stamp in the project; the last three shapes are excluded.
-3. **Match the brief to a shape** using the "Reach for it" lines. Most briefs match two to four; pick the one most distant from the logged shapes, and check the mirror test in SKILL.md Step 2.
+3. **Match the brief to a shape** using the index lines above and § Domain to trio below, then open only the file you land on. Most briefs match two to four; pick the one most distant from the logged shapes, and check the mirror test in SKILL.md Step 2.
4. **State the pick once**, in the Picks block's Shape row, then write the code with the stamp's `shape:` field set. The stamp reads `/* Hallmark · shape: <shape> · genre: <genre> · theme: <theme> ... */`; the full form is in SKILL.md Step 6.
5. If genuinely torn, offer three from different families (§ Domain to trio, below) and let the user pick.
@@ -83,9 +83,9 @@ Two pages Hallmark builds for two different briefs must look like different site
**2. Body composition.** Single column · Two-column asymmetric (wide body, narrow margin for captions) · Multi-column justified with hyphenation · Marginalia (sidenotes in the outer margin) · Three equal columns (reference density) · Full-bleed with margin reset (65ch body, pull quotes and images bleed) · Asymmetric spans (2-1-3 ratios on a grid).
-**3. Divider language.** Hairline rule (0.5 to 1px, inset or full-bleed) · Ornament (a fleuron, a dot, a mark) · Negative space (the gap is the divider) · Bleed-colour block (a paper change is the edge) · Double rule. Pick one and let it run the whole page.
+**3. Divider language.** Hairline rule (0.5 to 1px, inset or full-bleed) · Ornament (a fleuron, a dot, a mark) · Negative space (the gap is the divider) · Bleed-colour block (a paper change is the edge) · Double rule. Pick one language for the page and vary its weight and placement by seam (9): the same rule at the same gap at every seam is the template.
-**4. Button voice.** Outlined · Unstyled link (an underlined word) · Oversized solid · Typographic only (a word in a weight, no box) · Form as CTA (the action is fill-this-field).
+**4. Button voice.** Solid (one filled primary) · Outlined · Unstyled link (an underlined word) · Oversized solid · Typographic only (a word in a weight, no box) · Form as CTA (the action is fill-this-field).
**5. Image treatment.** Full-bleed · Tightly cropped to the grid · Inline with the text · Margin-aligned · None.
@@ -114,4 +114,4 @@ When the brief gives no shape, offer three shapes from different families (grid-
| conference, event, speaker | Marquee Hero · Manifesto · Photographic |
| no signal at all | Bento Grid · Long Document · Manifesto |
-Developer docs and developer marketing are different briefs (a walkthrough wants Workbench; the landing wants Bento plus Stat-Led), as are a one-pager and a case-study portfolio; ask one question when it is ambiguous. A vague tone word ("modern", "clean") is not an answer; re-ask with the trio. Whichever of the three is most distant from the last logged shape is the right pick.
+Developer docs and developer marketing are different briefs (a walkthrough wants Workbench; the landing wants Bento plus Stat-Led), as are a one-pager and a case-study portfolio; ask one question when it is ambiguous. A vague tone word ("modern", "clean") is read through the genre and stated as an inference, never a second question (SKILL.md Step 1). Whichever of the three is most distant from the last logged shape is the right pick.
diff --git a/skills/hallmark/references/macrostructures/03-marquee-hero.md b/skills/hallmark/references/macrostructures/03-marquee-hero.md
index 5ad5988..6ff5d37 100644
--- a/skills/hallmark/references/macrostructures/03-marquee-hero.md
+++ b/skills/hallmark/references/macrostructures/03-marquee-hero.md
@@ -2,7 +2,7 @@
The hero is the page above the fold. A single statement or visual fills the viewport. Below the fold the page becomes something else (a list, a grid, prose).
-- **Heading:** display fills the fold, 8 to 14vw, hugging the viewport edges; `line-height` 1.0 or more when it can wrap (55a).
+- **Heading:** display fills the fold at `clamp(4rem, 9vw, 12rem)` (`craft.md` § 1), hugging the container's edges; `line-height` 1.0 or more when it can wrap (55a).
- **Body:** below the fold, a list of work or one content block; the hero does not continue.
- **Divider:** a thick rule between hero and below-fold, or a hard change of paper.
- **Button:** one action in the fold under the statement, with the one sentence (Floor 12, 13): a typographic link or a single button. The statement owns the screen; the action and the sentence sit small at its foot.
diff --git a/skills/hallmark/references/macrostructures/14-narrative-workflow.md b/skills/hallmark/references/macrostructures/14-narrative-workflow.md
index 0970c7f..df60f2b 100644
--- a/skills/hallmark/references/macrostructures/14-narrative-workflow.md
+++ b/skills/hallmark/references/macrostructures/14-narrative-workflow.md
@@ -3,11 +3,11 @@
Numbered stages tell the story of how the user uses the product over time. Each section is a phase; the page is a process timeline.
- **Heading:** the stage number rides inside the heading (`<h2>1.0 Intake</h2>`) or is generated by `<ol>` with `counter()`. Never a separate label beside the heading: that is an eyebrow at stage scale (54).
-- **Body:** each stage has a short explanation and a small product capture.
-- **Divider:** a thick numbered rule between stages.
+- **Body:** each stage has a short explanation and one object: a small product capture when the user gave screens, otherwise a drawn object or a figure from the brief (a timer, a count, the thing the stage makes).
+- **Divider:** a numbered rule between stages, in the theme's rule weight.
- **Button:** links inside stages; one global button at the foot ("Start at stage one").
-- **Image:** a small real capture per stage, often annotated, in a `<figure>` or a slot.
-- **Reveal:** horizontal sweep as stages enter the viewport. A scrub-linked stage sequence may use [`../scroll-choreography.md`](../scroll-choreography.md) § 1 Pinned chapter instead: one pattern per page.
+- **Image:** a small real capture per stage, often annotated, in a `<figure>` or a slot; with one screen or none, never a slot per stage (68).
+- **Reveal:** horizontal sweep as stages enter the viewport, when the theme allows a reveal. A scrub-linked stage sequence may use [`../scroll-choreography.md`](../scroll-choreography.md) § 1 Pinned chapter instead: one pattern per page.
Reach for it for products with explicit workflows: project management, design-to-dev pipelines, writing tools.
diff --git a/skills/hallmark/references/macrostructures/19-map-diagram.md b/skills/hallmark/references/macrostructures/19-map-diagram.md
index 4e1a915..75b1729 100644
--- a/skills/hallmark/references/macrostructures/19-map-diagram.md
+++ b/skills/hallmark/references/macrostructures/19-map-diagram.md
@@ -5,7 +5,7 @@ A single large spatial diagram organises the page: flowchart, floor plan, networ
- **Heading:** a small orientation phrase above or beside the map.
- **Body:** the map itself, nodes and edges, with a legend.
- **Divider:** none inside; the diagram is one composition.
-- **Button:** links inside nodes; one outlined CTA below the map.
+- **Button:** links inside nodes; one CTA below the map, in the theme's control pair.
- **Image:** the map is the image: hand-built SVG with hover states, labelled or `aria-hidden` with a text legend carrying every fact (33). Geometry that is geometry is a first-class medium (47c).
- **Reveal:** node-by-node ink-on as the map enters the viewport, capped at five nodes, once.
diff --git a/skills/hallmark/references/themes/cobalt.md b/skills/hallmark/references/themes/cobalt.md
index 90cba54..ebfe81f 100644
--- a/skills/hallmark/references/themes/cobalt.md
+++ b/skills/hallmark/references/themes/cobalt.md
@@ -61,7 +61,7 @@ Declarative, technical, specific: name the endpoint, the command, the number. No
- Never a warm accent; the signal is cobalt at hue 256.
- Never a pill or gradient button; one solid cobalt button at 6px plus typographic links.
- Never a floating pill nav; chrome is a flush bar with a single hairline.
-- Never fake code; a snippet compiles, resolves or returns, and an invented endpoint is the theme's worst failure.
+- Never fake code; a snippet compiles, resolves or returns, and an invented endpoint is the theme's worst failure. A brief with no endpoint still gets the pair: its own command or call as written, against `example.com`, with the field names it gives and sample values.
- Never a second dark beat; two graphite bands turn the light theme into a striped one.
## Build hint
diff --git a/skills/hallmark/scripts/sloplint.mjs b/skills/hallmark/scripts/sloplint.mjs
index aff1935..dc89309 100644
--- a/skills/hallmark/scripts/sloplint.mjs
+++ b/skills/hallmark/scripts/sloplint.mjs
@@ -3011,11 +3011,17 @@ function check69(ctx) {
}
function check70(ctx) {
- const SUCCESS = /(["'`])\s*(?:sent|thanks|thank you|reserved|booked|you're on the list|you are on the list|subscribed|we'll be in touch|request received|done)\b[^"'`]{0,60}\1/i;
+ const SUCCESS = /\b(sent|thanks|thank you|reserved|booked|on the list|subscribed|in touch|received|confirmed|ordered|chosen|on its way|signed up|all set|you're in|you are in|done)\b/i;
+ const NEG = /\b(not|nothing|no|never|isn't|wasn't|didn't|cannot|can't|failed|try again|soon)\b/i;
for (const doc of ctx.docs) {
const js = (doc.scripts && typeof doc.scripts === 'string') ? doc.scripts : (doc.src.match(/<script\b[^>]*>([\s\S]*?)<\/script>/gi) || []).join('\n');
if (!/<form\b|type\s*=\s*["']submit/i.test(doc.src) || !js) continue;
- const m = SUCCESS.exec(js);
+ let m = null;
+ for (const x of js.matchAll(/(["'`])((?:(?!\1)[^\\\n]|\\.){4,140})\1/g)) {
+ const str = x[2];
+ const head = str.trim().split(/\s+/).slice(0, 4).join(' ');
+ if (str.trim().split(/\s+/).length >= 2 && SUCCESS.test(head) && !NEG.test(str)) { m = [x[0]]; break; }
+ }
if (!m) continue;
if (/\bfetch\s*\(|XMLHttpRequest|navigator\.sendBeacon|\.submit\s*\(\s*\)|axios|\$\.ajax/.test(js)) continue;
report(70, 'WARN', doc.file, doc.lineOf ? doc.lineOf(doc.src.indexOf(m[0]) >= 0 ? doc.src.indexOf(m[0]) : 0) : 1, `a script prints success ("${trunc(m[0].replace(/["'`]/g, ''), 30)}") with no request behind it`, 'No success state until the form posts somewhere; an empty data-endpoint and a handoff note');
diff --git a/skills/hallmark/scripts/theme.mjs b/skills/hallmark/scripts/theme.mjs
index 089c37b..65c4e2d 100644
--- a/skills/hallmark/scripts/theme.mjs
+++ b/skills/hallmark/scripts/theme.mjs
@@ -16,7 +16,7 @@ const has = (k) => args.includes('--' + k);
function usage() {
console.error(`usage:
node theme.mjs deal --genre <g> --brief "<brief>" [--log .hallmark/log.json] [--n 3] [--reroll 0] [--json]
- node theme.mjs scaffold <slug> [--dir .] [--force]
+ node theme.mjs scaffold <slug> [--dealt "<n>/3, seed <seed>"] [--dir .] [--force]
node theme.mjs scaffold --custom [--dir .] [--force]
node theme.mjs check --axes "<paper>/<display>/<accent>" [--face "<display face>"] [--hue <accent hue>] [--log .hallmark/log.json]
node theme.mjs index
@@ -138,11 +138,11 @@ function deal() {
console.log(`deal: ${seedKey} · genre ${genre}${reroll ? ` · reroll ${reroll}` : ''}`);
picked.forEach((s, i) => {
const why = s.hits.length ? `fits: ${s.hits.slice(0, 4).join(', ')}` : (s.t.genre === genre ? 'genre fit' : 'adjacent genre');
- console.log(`${i + 1}. ${s.t.name} · ${triple(s.t)} · ${s.t.material} · ${why} · ${s.t.file}${s.t.picture ? ` + ${s.t.picture}` : ''}`);
+ console.log(`${i + 1}. ${s.t.name} · ${triple(s.t)} · ${s.t.material} · ${why} · ${s.t.file}${s.t.picture ? ` + ${s.t.picture}` : ''}${s.t.pictured ? ` (pictured as ${s.t.pictured})` : ''}`);
});
if (recent.length) console.log(`avoid: ${recent.map((r) => `${r.theme || '?'} (${r.axes || 'no axes'})`).join(' · ')}`);
else console.log('avoid: nothing logged yet (first run for this project)');
- console.log(`next: look at the three pictures side by side and pick the material this brief wants, then node <skill-dir>/scripts/theme.mjs scaffold <slug> to write tokens.css and print the base rules`);
+ console.log(`next: look at the three pictures side by side and pick the material this brief wants (a picture in your own shape asks for a different section order), then node <skill-dir>/scripts/theme.mjs scaffold <slug> --dealt "<n>/${n}, seed ${seedKey}"`);
}
const PAPER_BANDS = new Set(['light', 'mid', 'dark']);
@@ -252,7 +252,7 @@ function scaffold() {
writeFileSync(out, css);
const stamp = custom
? `/* Hallmark · shape: <shape> · genre: <genre> · custom: draw n/7 (seed <slug>·<date>·r0)\n * hero: <posture> · nav: <shape> · footer: <shape> · enrichment: <none or the file> · signature: <the one move>\n * axes: <paper>/<display>/<accent> · posture: <posture> · contrast: pass · fold: pass · v${VERSION} */`
- : `/* Hallmark · shape: <shape> · genre: ${header.genre} · theme: ${name} (deal n/3, seed <from the deal>)\n * hero: <posture> · nav: <shape> · footer: <shape> · enrichment: <none or the file> · signature: <the one move>\n * axes: ${triple(header)} · posture: ${header.posture} · contrast: pass · fold: pass · v${VERSION} */`;
+ : `/* Hallmark · shape: <shape> · genre: ${header.genre} · theme: ${name} (${flag('dealt', '') ? `deal ${flag('dealt', '')}` : 'by request'})\n * hero: <posture> · nav: <shape> · footer: <shape> · enrichment: <none or the file> · signature: <the one move>\n * axes: ${triple(header)} · posture: ${header.posture} · contrast: pass · fold: pass · v${VERSION} */`;
console.log(`wrote ${out} (${custom ? 'the shared scale; fill every --color-* and --font-* from direction.md § B and § C before building' : `${name} tokens plus the shared scale`})`);
if (!custom) {
const pic = join(THEMES, `${slug}.jpg`);