Skip to content

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

CSS

Hero postures: six named fold geometries replace the single silhouette

Youssefc4a7b837d5af
diff --git a/skills/hallmark/SKILL.md b/skills/hallmark/SKILL.md
index a43031b..2b94744 100644
--- a/skills/hallmark/SKILL.md
+++ b/skills/hallmark/SKILL.md
@@ -35,7 +35,7 @@ These bind on every output, in every verb, on every model. Read nothing else and
0. Pre-flight scan of the existing project.
1. Ask Audience / Use case / Tone once; detect genre; note custom signals.
-2. Pick macrostructure + nav + footer from the slim indexes; run the Rotation rules; say the Picks block.
+2. Pick macrostructure + nav + footer + hero posture from the slim indexes; run the Rotation rules; say the Picks block.
2.6. Theme route: studied-DNA, catalog, or custom (custom runs the ritual in [`references/custom-theme.md`](references/custom-theme.md)).
3. Load ONLY the listed reference files.
4. Enrichment decision (scene sentence first; most pages are typography-only).
@@ -177,19 +177,20 @@ Two non-default signals firing (rare): ask one short either/or. State the genre
**Macrostructure first.** Read the index at [`references/macrostructures.md`](references/macrostructures.md), pick ONE of the 21 named shapes, then load ONLY that per-macro file from `references/macrostructures/`. Never load the whole catalogue. The macrostructure picks five of the six structural axes; the deeper axis catalogue in [`references/structure.md`](references/structure.md) is only for deviating.
-**Nav and footer at the same step.** Read the index + routing tables in [`references/component-cookbook.md`](references/component-cookbook.md); pick a nav archetype (N1a-N13, fourteen of them) and a footer archetype (Ft1-Ft8); load ONLY the picked files from `references/components/`. A typical build loads 5-7 archetype files total. **Default away from N1a and Ft3**, the two most-recognised AI fingerprints; reach for N1b / N5 / N11 / N13 and Ft1 / Ft2 / Ft4-Ft8 unless the page genuinely has two destinations or is a docs hub.
+**Nav, footer, and hero at the same step.** Read the index + routing tables in [`references/component-cookbook.md`](references/component-cookbook.md); pick a nav archetype (N1a-N13, fourteen of them) and a footer archetype (Ft1-Ft8); load ONLY the picked files from `references/components/`. A typical build loads 5-7 archetype files total. **Default away from N1a and Ft3**, the two most-recognised AI fingerprints; reach for N1b / N5 / N11 / N13 and Ft1 / Ft2 / Ft4-Ft8 unless the page genuinely has two destinations or is a docs hub. Then pick the **hero posture** (Settled · Banner · Poster · Ledge · Corridor · Stage) and content archetype (H1-H9); the envelope table lives in [`references/enrichment/hero-discipline.md`](references/enrichment/hero-discipline.md) § Hero postures.
**Rotation (the canonical block - every other file defers here):**
- **Macro:** 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). Specimen is never a default; reach for it only on explicit editorial / foundry briefs.
- **Theme:** two consecutive themes 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 24-row lookup lives in [`references/theme-axes.md`](references/theme-axes.md). Two of three matching: pick a more distant theme.
- **Nav + footer:** across consecutive runs and across test builds of the same theme, no repeated N code and no repeated Ft code. This is the single most-violated rule; rotate deliberately through the routing table's alternates.
+- **Hero:** no non-Settled posture repeats back-to-back; Settled may repeat twice, never three runs in a row. The content archetype H# follows the nav/footer no-repeat rule.
- **Enrichment:** do not repeat the previous run's E# archetype back-to-back.
- **Log schema** (`.hallmark/log.json`, newest entry first, trimmed to 20):
```json
{ "date": "2026-04-30", "macrostructure": "Bento Grid", "theme": "Coral",
- "nav": "N5", "footer": "Ft2", "enrichment": "E1 clipped-edge",
+ "hero": "Stage/H2", "nav": "N5", "footer": "Ft2", "enrichment": "E1 clipped-edge",
"brief": "Tracejam · SaaS observability" }
```
@@ -199,8 +200,8 @@ First run for a project: no constraint, note it in one line. User explicitly re-
```
Picks · genre: modern-minimal · macro: Workbench (last 3: Bento, Long Document, Manifesto)
-· theme: Cobalt (differs on paper band + display style) · nav: N13 (prev N5) · footer: Ft5
-· enrichment: tbd (Step 4) · custom: no
+· theme: Cobalt (differs on paper band + display style) · hero: Stage/H2 (prev Settled)
+· nav: N13 (prev N5) · footer: Ft5 · enrichment: tbd (Step 4) · custom: no
```
The enrichment cell may read `tbd (Step 4)`; the decision lands there and the Step 5 preview carries the final value. On a custom run the Picks block emits after the 2.6 ritual instead, so it can carry the draw line.
@@ -220,7 +221,7 @@ A custom system is complete (palette + pairing + axes), never a colour swap; its
**Do:** load exactly what this build needs; over-eager loading is the largest avoidable cost of running Hallmark.
-**Always (1-2 files):** the genre file from Step 1; plus `references/themes/<theme>.md` when it exists for the picked catalog theme (only some themes have one; silent no-op when absent; studied-DNA and custom skip this).
+**Always (2-3 files):** the genre file from Step 1; [`references/enrichment/hero-discipline.md`](references/enrichment/hero-discipline.md) (the posture envelope + hero rules bind on every page hero, enriched or not); plus `references/themes/<theme>.md` when it exists for the picked catalog theme (only some themes have one; silent no-op when absent; studied-DNA and custom skip this).
**Index-then-pick (read the slim index, load only the picks):**
- [`references/macrostructures.md`](references/macrostructures.md) → one file from `references/macrostructures/`.
@@ -280,7 +281,7 @@ Emit code that satisfies the tone and the structural fingerprint. Match code com
- A distinctive display face + refined body face (single-font pages only when the single font IS the design).
- Eight states for every interactive element; animate `transform` / `opacity` only; the three named easings, never `ease`, never bounce on UI state; `prefers-reduced-motion` support; instant `:focus-visible` ring at >= 3:1.
- Microinteraction recipes per [`references/microinteractions.md`](references/microinteractions.md): silent success over toasts, optimistic + Undo over confirms, 800ms hover / 0ms focus tooltips. Cut motion before adding it.
-- **Stamp the output.** Canonical top-of-file order: line 1 the macrostructure stamp `/* Hallmark · macrostructure: <name> · tone: <tone> · anchor hue: <hue> */` plus the nav / footer / contrast / mobile records the gates ask for; line 2 the pre-emit critique comment; then (custom only) the direction contract block. Custom and studied-DNA stamps carry their extended fields per [`references/custom-theme.md`](references/custom-theme.md) § E and the output contract in [`references/study.md`](references/study.md).
+- **Stamp the output.** Canonical top-of-file order: line 1 the macrostructure stamp `/* Hallmark · macrostructure: <name> · tone: <tone> · anchor hue: <hue> · hero: <Posture>/<H#> */` plus the nav / footer / contrast / mobile records the gates ask for; line 2 the pre-emit critique comment; then (custom only) the direction contract block. Custom and studied-DNA stamps carry their extended fields per [`references/custom-theme.md`](references/custom-theme.md) § E and the output contract in [`references/study.md`](references/study.md).
- **Append to project memory:** update `.hallmark/log.json` (schema in Step 2), newest first, trimmed to 20. Create `.hallmark/` if needed; respect any existing `.gitignore`.
- **Never clobber an existing global stylesheet.** Entry stylesheets (`app/globals.css`, `src/index.css`, `src/styles/global.css`) are **append-only**: keep `@tailwind` / `@import "tailwindcss"` directives in place, add Hallmark's `:root` block and base rules below them, keep any new `@import` at the very top above all rules, and reuse the project's own token names (`--background`, `--foreground`, a Tailwind `@theme`) where they exist. Full rewrite only on explicit request: silently removing a framework's CSS entry directives un-styles the entire app. See [`references/contract.md`](references/contract.md).
- **Always emit `tokens.css`** at the project root with every `--color-*`, `--font-*`, `--space-*`, `--text-*`, `--ease-*`, `--dur-*`, `--rule-*`, and `--radius-*` token used, imported by the page CSS (or included by the project's entry point). Even single-page builds. On `design.md` projects, also refresh the `## Exports` section with all four formats (tokens.css, Tailwind v4 `@theme`, DTCG `tokens.json`, shadcn/ui variables) per [`references/export-formats.md`](references/export-formats.md).
diff --git a/skills/hallmark/references/enrichment/hero-discipline.md b/skills/hallmark/references/enrichment/hero-discipline.md
index f2fb04d..480a500 100644
--- a/skills/hallmark/references/enrichment/hero-discipline.md
+++ b/skills/hallmark/references/enrichment/hero-discipline.md
@@ -1,14 +1,28 @@
# Hero discipline: space, motion, and the ship gate
-Load this file alongside whichever archetype (E1-E8) or polish pattern (HP1-HP4) you picked. These rules bind on every hero; the eight pre-flight questions decide whether the enrichment ships at all.
+Load this file for EVERY page hero, enriched or not: the posture below is picked at Step 2 alongside nav and footer, and the eight pre-flight questions decide whether an enrichment ships at all.
+
+## Hero postures - pick one, stamp it
+
+The posture sets the hero's geometry envelope. **Settled is the neutral default**; every other posture is opt-in, named in the Picks block, the CSS stamp (`· hero: <Posture>/<H#>`), and the log. Gate 44 reads the posture from the stamp (no field = Settled). Fold-fit at 1280x800 and the two-centred-elements ceiling (gate 6) bind on all six. Rotation lives in SKILL.md § Rotation.
+
+| Posture | Character | Min-height | Padding rule | Alignment | Pairs with | Genre affinity |
+| --- | --- | --- | --- | --- | --- | --- |
+| **Settled** | balanced fold; sits into the page | `clamp(60vh, 75dvh, 88dvh)` (70-90% of viewport) | block-end >= 1.3x block-start | <= 2 centred | any H1-H9 | any (default) |
+| **Banner** | compressed opener; the page starts fast | 40-55dvh (cap ~`min(52dvh, 34rem)`) | block-end >= 1.3x block-start | 0-1 centred, edge-led | H1 (short), H4, H5 | reference / docs / utility (Almanac, Ledger, Grid, Cobalt) |
+| **Poster** | full-bleed canvas; the fold IS the artwork | 92-100dvh (100dvh legal only here) | waived when content is edge/corner-anchored, else 1.3x | centred only under gate 6's genre carve-outs | H1, H6 | atmospheric · playful-canvas · Manifesto / Sport |
+| **Ledge** | tall top void; content rests at the base | 70-88dvh | inverted: block-start >= 2x block-end, content `align-content: end` | <= 1 centred | H1, H4, H6 | sport · brutal · manifesto · photographic |
+| **Corridor** | tall centred reading column | 66-85dvh | block-end >= 1.3x block-start | centred column <= 44ch; eyebrow OR CTA off-axis | H3, H5, H1 | editorial · atelier (gate 6 centred-narrow rule) |
+| **Stage** | text column + full-height visual that may bleed | 70-92dvh | 1.3x on the text column; visual may touch the hero's edges | <= 1 centred | H2, H7, H8 | modern-minimal · playful product |
+
+Mobile (< 48rem): every posture collapses to content height (`min-height: auto` or <= 60dvh); Poster may stay full-bleed. Fold-fit (gate 44b) is posture-independent: at 1280x800 the essential content is complete without scrolling on every posture, including Ledge (content bottom = hero bottom minus block-end padding, and the hero itself stays <= 88dvh) and Poster (content anchored inside the first 800px).
## Hero space discipline
-Every hero — enriched or not, polished or not — obeys these rules.
+These bind on every hero, whatever the posture.
-- **Footprint.** The hero takes 70–90 % of the first viewport's height — no more, no less. `min-height: 100vh / 100dvh` is the AI fingerprint (gate 6); a hero that's only 20 % of the viewport feels like a header. Aim for `min-height: clamp(60vh, 75dvh, 88dvh)` and let content settle inside.
-- **Fit the fold — content, not just the box.** The Footprint rule caps the hero's *height*; this caps its *content*. On a 13″ laptop (~800 px tall) the eyebrow + headline + lede + primary CTA must all be visible **without scrolling**. When they aren't, it's almost always wasted vertical space — an oversized display `clamp()` max, display line-height near 1.2, a 3-line lede, or `padding-block` bloat. Pull the clamp max down, set display line-height 1.0–1.1, hold the lede to ~2 lines, trim the padding. **Right-size, don't cramp** — a hero that already fits needs no shrinking, and this never means tiny type or no whitespace. Slop-test gate 44 enforces this.
-- **Asymmetric padding.** `padding-block-end` ≥ 1.3× `padding-block-start`. The hero sits *into* the page; symmetric padding floats. Slop-test gate 44 enforces this.
+- **Fit the fold — content, not just the box.** The posture caps the hero's *height*; this caps its *content*. On a 13″ laptop (~800 px tall) the eyebrow + headline + lede + primary CTA must all be visible **without scrolling**. When they aren't, it's almost always wasted vertical space — an oversized display `clamp()` max, display line-height near 1.2, a 3-line lede, or `padding-block` bloat. Pull the clamp max down, set display line-height 1.0–1.1, hold the lede to ~2 lines, trim the padding. **Right-size, don't cramp** — a hero that already fits needs no shrinking, and this never means tiny type or no whitespace. Slop-test gate 44 enforces this.
+- **Padding per posture.** The posture table above owns the padding rule (1.3x bottom-heavy on most, inverted on Ledge, waived on an anchored Poster). Symmetric padding on a Settled/Banner/Corridor/Stage hero floats off the page; gate 44 reads the stamped posture and enforces the matching rule.
- **Never centre everything.** Eyebrow + title + lede + CTA all stacked centred is the AI fingerprint. Pick at most *two* centred elements; break alignment for the others. Gate 6 enforces this. Centred-narrow heroes are admissible only when the genre is editorial / atelier *and* the eyebrow or CTA breaks alignment.
- **Entrance animation.** Pick one of {fade, sweep, none} per element — never both fade *and* sweep on the same element. Duration ≤ 220 ms. Disable on `prefers-reduced-motion: reduce`. Cross-reference the "One orchestrated reveal per page" rule below.
- **Headline typography.** Prefer one display weight + tight tracking (-0.02em to -0.04em) over default 0; line-height 0.95–1.05 for display, never 1.2 (which inherits the body line-height and reads as un-set type). Avoid two display weights on the same headline (a `<strong>` in a different weight inside the title is AI's idea of "emphasis"; pick one weight, let the words carry).
diff --git a/skills/hallmark/references/slop-test.md b/skills/hallmark/references/slop-test.md
index f8d4871..d6c0b8c 100644
--- a/skills/hallmark/references/slop-test.md
+++ b/skills/hallmark/references/slop-test.md
@@ -57,7 +57,7 @@ Record the six scores in a one-line stamp comment directly below the macrostruct
3. **[M]** Is there a 3-equal-column card grid with icon-above-heading tiles?
4. **[M]** Is any card nested inside another card?
5. **[M]** Is any card using a thick coloured left/right side-stripe border?
-6. **[J]** **Hero shape — centred-everything.** Is the hero `min-height: 100vh` with everything centred, OR are the eyebrow, title, lede, AND CTA all stacked on the same centred vertical axis? Auto-fail. Pick at most two centred elements and break alignment for the rest; the eyebrow or CTA should sit off-axis (margin-aligned, right-flush, numeral-anchored). *Genre note: atmospheric and playful allow a centred hero when the canvas itself is the design (Suno-style); editorial / atelier allow a centred-narrow hero, but even then the eyebrow or CTA sits off-axis.*
+6. **[J]** **Hero shape — centred-everything.** Is the hero `min-height: 100vh`/`100dvh` outside a stamped **Poster** posture, OR are the eyebrow, title, lede, AND CTA all stacked on the same centred vertical axis? Auto-fail. Pick at most two centred elements and break alignment for the rest; the eyebrow or CTA should sit off-axis (margin-aligned, right-flush, numeral-anchored). *Genre note: atmospheric and playful allow a centred hero when the canvas itself is the design (Suno-style); editorial / atelier allow a centred-narrow hero, but even then the eyebrow or CTA sits off-axis.* *Posture note: a stamped Poster hero may run 92-100dvh (hero-discipline.md § Hero postures); the centred-element ceiling still binds per the genre carve-outs.*
7. **[M]** Is pure `#000` or pure `#fff` used as a base colour anywhere? *Genre note: modern-minimal allows pure `#fff` paper (the Stripe / ElevenLabs school).*
## Structural
@@ -158,7 +158,7 @@ Universal — apply to every genre. These gates catch the most-recognised AI fin
43. **[M]** **Footer fingerprint.** Is the `<footer>` the AI default — 4 columns of links (Product / Company / Resources / Legal) + social-icon row + tiny copyright at the very bottom + 1 px hairline top-border + neutral grey background? If yes, fail unless the page is a genuine docs root or hub. Default to Ft1, Ft2, Ft4, Ft5, Ft6, Ft7, or Ft8 from [`component-cookbook.md`](component-cookbook.md) § Footers.
-44. **[R/J]** **Hero fit — sits into the page and fits the fold.** Two checks, both on the rendered hero: (a) Is `padding-block-end` ≥ 1.3× `padding-block-start`? Symmetric or top-heavy padding makes the hero float off the page; heavier bottom padding pulls it into the next section's rhythm. (b) On a standard laptop viewport — test at **1280×800** (13″), not just 1440×900 — can the hero's essential content (eyebrow, headline, lede, **and the primary CTA**, plus any hero visual's focal point) all be seen **without scrolling**? This is the other half of gate 6 (which caps the hero's *shape*): this caps its *content*. A hero can satisfy `min-height` and still overflow because the content is intrinsically too tall — usual culprits are an **oversized display clamp**, **loose line-height** (display at ~1.2 instead of 1.0–1.1), a **lede that runs 3+ lines**, or **bloated `padding-block`**. Right-size to the fold: pull the display `clamp()` max down until the headline fits 2–3 lines, set display line-height 1.0–1.1, hold the lede to ~2 lines (≤ ~60 ch), trim hero padding. **Don't overcorrect:** a hero that already fits passes untouched — this never means tiny type or stripped whitespace. Long-form / art-directed statements (a poem broadside, a scroll-poster) may legitimately run taller, but even then the **first screen must read as a complete, deliberate composition** — never a headline sliced in half by the fold. For models that cannot render or see, the numeric heuristics above are the text-only verification path: display `clamp()` max sized so the headline lands in 2-3 lines, display line-height 1.0-1.1, lede at most ~2 lines and at most ~60 ch, and `padding-block` within budget.
+44. **[R/J]** **Hero fit — posture envelope + fits the fold.** Two checks, both on the rendered hero: (a) Does the hero obey its declared posture's envelope ([`hero-discipline.md`](enrichment/hero-discipline.md) § Hero postures; the stamp's `hero:` field, Settled when absent)? Settled / Banner / Corridor / Stage: `padding-block-end` ≥ 1.3× `padding-block-start` inside the posture's min-height range. Ledge inverts it (block-start ≥ 2× block-end, content anchored to the base). Poster waives the ratio only when content is edge- or corner-anchored. A hero matching no envelope, or claiming one and breaking it, fails. (b) On a standard laptop viewport — test at **1280×800** (13″), not just 1440×900 — can the hero's essential content (eyebrow, headline, lede, **and the primary CTA**, plus any hero visual's focal point) all be seen **without scrolling**? This is the other half of gate 6 (which caps the hero's *shape*): this caps its *content*. A hero can satisfy `min-height` and still overflow because the content is intrinsically too tall — usual culprits are an **oversized display clamp**, **loose line-height** (display at ~1.2 instead of 1.0–1.1), a **lede that runs 3+ lines**, or **bloated `padding-block`**. Right-size to the fold: pull the display `clamp()` max down until the headline fits 2–3 lines, set display line-height 1.0–1.1, hold the lede to ~2 lines (≤ ~60 ch), trim hero padding. **Don't overcorrect:** a hero that already fits passes untouched — this never means tiny type or stripped whitespace. Long-form / art-directed statements (a poem broadside, a scroll-poster) may legitimately run taller, but even then the **first screen must read as a complete, deliberate composition** — never a headline sliced in half by the fold. For models that cannot render or see, the numeric heuristics above are the text-only verification path: display `clamp()` max sized so the headline lands in 2-3 lines, display line-height 1.0-1.1, lede at most ~2 lines and at most ~60 ch, and `padding-block` within budget.
45. **[J]** **Decorative-without-purpose.** Does the hero contain a decorative element (cursor, scanline, gradient blob, abstract shape, ornament, badge, sticker) that has no semantic anchor in the content? Fail. Decoration must be motivated: a cursor inside a typed command (signals "you'd type next"), a numeral that names an issue / year / version / chapter, a gradient that responds to interaction (HP3 cursor-spotlight), a stamp that names an authorship or date. Random ornaments — a "42" in the corner with no edition meaning, a cursor floating beside a hero, a Pantone chip with no colour rationale — are slop.
diff --git a/skills/hallmark/references/typography.md b/skills/hallmark/references/typography.md
index a67a8ca..80d4165 100644
--- a/skills/hallmark/references/typography.md
+++ b/skills/hallmark/references/typography.md
@@ -184,6 +184,7 @@ Pick a ratio. The default for Hallmark work is **1.25** (major third). Build the
--text-3xl: 3.0518rem;
--text-4xl: 3.8147rem;
--text-display: clamp(2.75rem, 5vw + 1rem, 5.25rem);
+ --text-display-s: clamp(2.2rem, 4vw + 0.75rem, 4.2rem); /* one 1.25 step below display at both ends; the step-down the headline brackets reference */
}
```