Skip to content

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

CSS

The deal is picked by eye, and reviewers judge against the picture

Youssefca6e5841219c
diff --git a/README.md b/README.md
index 54473ba..427e85d 100644
--- a/README.md
+++ b/README.md
@@ -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 deals three themes from a catalog of forty-nine materials, and a script applies the rotation so consecutive builds cannot converge. When the user asks for **custom** it derives a world made to measure, with an outside draw picking among grounded directions so the model cannot repeat its favourite. It keeps every page to one idea per screen. Then it lints the result against the tells that read as machine-made in 2026: the eyebrow above every heading, the small label in tracked capitals, the one coloured word in a headline, middle-dot meta strings, arrows glued to link text, mono labels as a technical costume, cream paper with a high-contrast serif and a clay accent, and content that ships invisible when a script fails.
+Hallmark holds a hard floor and then gets out of the way. It deals three themes from a catalog of forty-nine materials, and a script applies the rotation so consecutive builds cannot converge. When the user asks for **custom** it derives a world made to measure, with an outside draw picking among grounded directions so the model cannot repeat its favourite. It keeps every page to one idea per screen. Then it lints the result against the tells that read as machine-made in 2026: the eyebrow above every heading, the small label in tracked capitals, the one coloured word in a headline, middle-dot meta strings, arrows glued to link text, mono labels as a technical costume, cream paper with a high-contrast serif and a clay accent, a page of empty picture frames, one price said four times, a form that says thanks without sending anything, and content that ships invisible when a script fails.
The gates come in tiers. The **Floor** never ships: contrast, focus, reduced motion, invented metrics, layout that breaks on a phone, the fold at three widths, the eyebrow. **Reflex** gates are the defaults a language model falls into rather than laws, and a build with an argument may overrule one on the record, with the reason in the CSS stamp and the guard re-derived by the checker. **Finish** checks are craft detail that never blocks a ship. A fresh-context reviewer with no memory of the build gets the last word.
@@ -21,11 +21,12 @@ Two pages by Hallmark for two different briefs feel like different sites, not co
## What a build looks like
1. Pre-flight reads the project (fonts, palette, framework, a locked `design.md`).
-2. One message asks for audience, use, tone, material and vibe; "go ahead" infers them.
-3. The page is designed, then named; `scripts/theme.mjs deal` prints three themes that fit the brief and clear the log.
-4. The build loads one craft file, one genre file, one theme file and the gate table. Nothing else unless it is needed. `scripts/theme.mjs scaffold` writes the tokens and prints the base rules, so the page is the only thing left to write.
-5. A Picks block states every decision once; then the page, a `tokens.css`, a stamp and a log entry.
-6. `scripts/sloplint.mjs --render` runs the mechanical gates at 320 to 1920 wide, the model walks the judged ones, and a subagent reviews the page cold.
+2. One message asks for the material first (screenshots, photos, real numbers, a quote with a name), then audience, use and tone. Material is never invented: what was not given becomes a designed slot or stays absent.
+3. The page is designed from that inventory, then named; the signature move comes from the strongest real thing. `scripts/theme.mjs deal` prints three themes that fit the brief and clear the log.
+4. The build loads one craft file, one genre file, one theme file with its picture (a finished page in that theme, for scale and density, never composition) and the gate table. `scripts/theme.mjs scaffold` writes the tokens and prints the base rules.
+5. A Picks block states every decision once. One exemplar page for the genre is read for craft.
+6. The nav and hero are built alone first, rendered at four sizes and reviewed cold before the rest of the page exists.
+7. `scripts/sloplint.mjs --render` runs the mechanical gates at 320 to 1920 wide, the model walks the judged ones, and a subagent reviews the finished page cold.
Each page is self-contained HTML and CSS, stamped in its first CSS comment with the shape, theme, chrome, hero and signature move it took.
@@ -66,7 +67,7 @@ Browse the full set at [usehallmark.com](https://www.usehallmark.com) or under [
## Themes
-A theme is a material, not a plan: paper, ink, faces, rule weight, radius, shadow stance, texture budget, motion character, voice. It never says what a page contains or in what order, so two pages in one theme do not share a section sequence. Every theme is one file of four to seven kilobytes in [`references/themes/`](skills/hallmark/references/themes/) with a header block that `theme.mjs index` compiles into `index.json`; the deal reads the index and a build reads exactly one theme file. Forty-nine themes cost a build what twenty-three did.
+A theme is a material, not a plan: paper, ink, faces, rule weight, radius, shadow stance, texture budget, motion character, voice. It never says what a page contains or in what order, so two pages in one theme do not share a section sequence. Every theme is one file of four to seven kilobytes in [`references/themes/`](skills/hallmark/references/themes/) with a header block that `theme.mjs index` compiles into `index.json`, and a picture beside it: two screens of a finished page built in that theme, so a build sees the material at full size before it writes a line. The deal reads the index and a build reads exactly one theme file. Forty-nine themes cost a build what twenty-three did.
## Custom
@@ -82,7 +83,7 @@ The same SKILL.md, references, gates and scripts run in **Claude Code**, **Codex
node skills/hallmark/scripts/sloplint.mjs <file-or-dir> --genre <genre> --render
```
-One command installs a lean copy (skill, references, scripts, never the marketing site) everywhere it belongs. On the way it rebuilds the theme index and runs `scripts/refcheck.mjs`, which reads every reference file for dead links, missing sections, retired gate numbers, unknown tokens, stale stamps and sample copy that breaks a gate; the install stops if it finds one:
+One command installs a lean copy (skill, references, scripts, never the marketing site) everywhere it belongs. On the way it rebuilds the theme index and runs `scripts/refcheck.mjs`, which reads every reference file for dead links, missing sections, retired gate numbers, unknown tokens, stale stamps and sample copy that breaks a gate, and lints the four exemplar pages, which must pass every gate they teach; the install stops if it finds one:
```bash
node skills/hallmark/scripts/install.mjs
diff --git a/skills/hallmark/SKILL.md b/skills/hallmark/SKILL.md
index 5c91fe4..6ed6dea 100644
--- a/skills/hallmark/SKILL.md
+++ b/skills/hallmark/SKILL.md
@@ -88,7 +88,7 @@ Check in order; the first match wins.
node <skill-dir>/scripts/theme.mjs deal --genre <genre> --brief "<the brief>" [--log .hallmark/log.json]
```
-The script reads the catalog index and the log, applies Rotation (two consecutive systems differ on paper band, display class or accent band; siblings in the log count as occupied) and deals three candidates that fit the brief's words, one line each, with a reproducible seed. Pick one of the three, say which and why in one clause, and load only `references/themes/<slug>.md`. Re-deal only when the user asks (`--reroll 1`). No Node: read `references/themes/index.json`, apply the same rule by hand, and stamp `deal: manual`.
+The script reads the catalog index and the log, applies Rotation (two consecutive systems differ on paper band, display class or accent band; siblings in the log count as occupied) and deals three candidates that fit the brief's words, one line each, with a reproducible seed. Look at the three pictures, pick one, say which and why in one clause, and load only `references/themes/<slug>.md`. Re-deal only when the user asks (`--reroll 1`). No Node: read `references/themes/index.json`, apply the same rule by hand, and stamp `deal: manual`.
A catalog theme is a material, not a plan: it says what the page is made of, never what the page contains or in what order. Two pages in one theme should not share a section sequence.
diff --git a/skills/hallmark/references/gates.md b/skills/hallmark/references/gates.md
index 773ffff..3cf1a5a 100644
--- a/skills/hallmark/references/gates.md
+++ b/skills/hallmark/references/gates.md
@@ -205,17 +205,17 @@ The gates above that a script cannot settle, with enough to judge them well.
## 6. The finish review, in fresh context
-The thread that built the page is its weakest reviewer. Spawn a reviewer with no inherited transcript (a subagent in Claude Code) and give it only: the artifact paths, the screenshots the render tier wrote (the folds at 1280 x 800, 1440 x 900 and 1920 x 1080, and the full page at 1440 and at 375), the direction contract or theme line from the stamp, and § 4 of this file. Its brief:
+The thread that built the page is its weakest reviewer. Spawn a reviewer with no inherited transcript (a subagent in Claude Code) and give it only: the artifact paths, the screenshots the render tier wrote (the folds at 1280 x 800, 1440 x 900 and 1920 x 1080, and the full page at 1440 and at 375), the direction contract or theme line from the stamp, on a theme build the theme's picture (`references/themes/<slug>.jpg`, a page in the same theme that shipped), and § 4 of this file. Its brief:
> Review a built page against a fixed list. You did not build it and will not be told why anything is the way it is. Read the page, not the intent. Reading is an allowance: the inputs above and nothing else, batched, and by the tenth turn stop reading and write.
>
> First line: one of `recapture` (a screenshot is missing, blank or shows the wrong thing; list what to recapture and stop), `rebuild` (the first viewport fails the contract or the theme wholesale), `fix` (material findings follow), `ship` (nothing owed).
>
-> Then: findings ranked by cost to the page, each one line with the gate or the plain defect, where it is, what you would do. At most eight. A direction you would not have chosen is not a finding. Then one answer to the question no gate can: does the stamp's contract or theme describe the page in front of you? Name the largest gap or say there is none. Close with one line naming what must not be diluted while fixing. Do not fix anything.
+> Then: findings ranked by cost to the page, each one line with the gate or the plain defect, where it is, what you would do. At most eight. A direction you would not have chosen is not a finding. The theme's picture, if given, is the bar for finish and never a model: is this page as finished as that one, in its own composition? Then one answer to the question no gate can: does the stamp's contract or theme describe the page in front of you? Name the largest gap or say there is none. Close with one line naming what must not be diluted while fixing. Do not fix anything.
-**The hero review** runs the same way, once, at Step 6, before any section below the fold exists. Give the reviewer the four `hero-*` screenshots that `sloplint --render --stage hero` wrote, the stamp's first two lines, and the Picks block's Material and Signature rows. Its brief:
+**The hero review** runs the same way, once, at Step 6, before any section below the fold exists. Give the reviewer the four `hero-*` screenshots that `sloplint --render --stage hero` wrote, the stamp's first two lines, the Picks block's Material and Signature rows, and on a theme build the theme's picture. Its brief:
-> Review the first screen of a page that is still being built. You did not build it. First line: `ship` or `fix`. Then at most five findings, one line each, worst first: does the headline say something only this product could say, in seven words or fewer; is the visual beside the text, real or a labelled slot, and does it hold its half of the screen; does anything read as a template (a centred stack, a pill or label above the headline, a gradient blob, a drawn dashboard, two filled buttons side by side; a primary with a quiet text link beside it is fine); is the signature move on this screen; does the type carry the theme at this size. Do not fix anything.
+> Review the first screen of a page that is still being built. You did not build it. First line: `ship` or `fix`. Then at most five findings, one line each, worst first: does the headline say something only this product could say, in seven words or fewer; is the visual beside the text, real or a labelled slot, and does it hold its half of the screen; does anything read as a template (a centred stack, a pill or label above the headline, a gradient blob, a drawn dashboard, two filled buttons side by side; a primary with a quiet text link beside it is fine); is the signature move on this screen; does the type carry the theme at this size; if you have the theme's picture, is this first screen as finished as its first screen, in a composition of its own. Do not fix anything.
Fix, recapture with `--stage hero`, and build the sections once the answer is `ship`. Record `hero-review: ship after 1 fix` in the stamp's finish-review field.
diff --git a/skills/hallmark/scripts/refcheck.mjs b/skills/hallmark/scripts/refcheck.mjs
index 945d4f8..0a86364 100644
--- a/skills/hallmark/scripts/refcheck.mjs
+++ b/skills/hallmark/scripts/refcheck.mjs
@@ -2,6 +2,7 @@
import { readFileSync, readdirSync, statSync, existsSync } from 'node:fs';
import { join, dirname, relative, basename, resolve } from 'node:path';
import { fileURLToPath } from 'node:url';
+import { spawnSync } from 'node:child_process';
const ROOT = resolve(dirname(fileURLToPath(import.meta.url)), '..');
const args = process.argv.slice(2);
@@ -258,6 +259,17 @@ for (const f of MD) if (!reach.has(f) && basename(f) !== 'README.md') add('warn'
const skillBytes = Buffer.byteLength(read(SKILL));
if (skillBytes > 20480) add('warn', SKILL, 1, 'size', `SKILL.md is ${skillBytes} bytes; keep it under 20 KB`);
+const exemplarDir = join(ROOT, 'references', 'exemplars');
+const clean = [...(existsSync(exemplarDir) ? readdirSync(exemplarDir).filter((n) => n.endsWith('.html')).map((n) => join(exemplarDir, n)) : []),
+ ...['eyebrow-pass', 'tailwind-pass'].map((n) => join(ROOT, 'scripts', 'fixtures', n)).filter(existsSync)];
+for (const target of clean) {
+ const run = spawnSync(process.execPath, [join(ROOT, 'scripts', 'sloplint.mjs'), target, '--json'], { encoding: 'utf8' });
+ let s = null;
+ try { s = JSON.parse(run.stdout).summary; } catch {}
+ if (!s) add('error', target, 1, 'lint', 'sloplint did not run on this file');
+ else if (s.fails || s.reflex || s.warns) add('error', target, 1, 'lint', `must lint clean, has ${s.fails} FAIL, ${s.reflex} REFLEX, ${s.warns} WARN`);
+}
+
const shown = ONLY_ERRORS ? findings.filter((x) => x.level === 'error') : findings;
const errors = findings.filter((x) => x.level === 'error').length;
const warns = findings.length - errors;
diff --git a/skills/hallmark/scripts/theme.mjs b/skills/hallmark/scripts/theme.mjs
index 037cf58..d77a0b9 100644
--- a/skills/hallmark/scripts/theme.mjs
+++ b/skills/hallmark/scripts/theme.mjs
@@ -140,7 +140,7 @@ function deal() {
});
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: 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, then node <skill-dir>/scripts/theme.mjs scaffold <slug> to write tokens.css and print the base rules`);
}
const PAPER_BANDS = new Set(['light', 'mid', 'dark']);