Editorial
Longform posts, essays, a personal magazine voice.
A landing-page skill that refuses to look AI-generated, and a linter that proves it.
A design skill for Claude Code, Codex, Cursor and OpenCode that refuses to look AI-generated. Made by Together AI. Use it for new marketing and landing pages, not app screens.
A new landing, launch or product page where the first screen has to sell.
One self-contained HTML/CSS page, stamped with its decisions, linted at eight widths and reviewed by a fresh-context subagent.
Hallmark holds a hard floor and then gets out of the way.
the eyebrow above every heading, tracked-capital labels, one coloured word in a headline, a page of empty frames or nothing but photographs, a hero that misses its screen, an email sign-up at the end of every page, a form that says thanks without sending anything.
A fresh-context reviewer gets the last word.
npx skills add nutlope/hallmark -g # every harness, every project npx skills add nutlope/hallmark -g --agent claude-code # one harness (codex, cursor, opencode, github-copilot) npm i -g puppeteer-core # + Chrome: needed for sloplint --render and screenshots
| Harness | Lands in | Invoke |
|---|---|---|
| Claude Code | ~/.claude/skills/hallmark | /hallmark <prompt> |
| Codex CLI | ~/.agents/skills/hallmark | $hallmark <prompt> |
| Cursor, OpenCode | finds the copies above | /hallmark <prompt> |
-g installs for every project; leave it off to install into the current one.
Needs Node 18 or later. Without puppeteer the static checks still run.
Name it: use hallmark to build .... Its description stops it from touching existing designs unless named.
/hallmark a landing page for a dotfiles CLI # build (deals 3 themes) /hallmark Terminal: a landing page for burrow # build in a named theme /hallmark custom: ... # no theme, Floor still holds /hallmark redesign ./src/app # keeps content + wiring, new system + layout /hallmark audit ./index.html # report only, no edits
Never use it on an existing design unless the user names Hallmark, as in /hallmark redesign <path>.
sloplint --before records every link, field, handler and heading first, sloplint --kept fails the redesign if one went missing.
Say keep the layout for a restyle or polish for only the tells.
No study verb ships in v2. SKILL.md lists only redesign <target> (a full redesign keeping content and wiring) and audit <target> (a report). "study" only shows up as an eval brief (eval/, b6) that expects the skill to decline.
The eight steps from SKILL.md, short.
0 Pre-flight. Reads fonts, palette, framework and any DESIGN.md, which overrides everything.
1 Ask once. Material, audience, use, tone. Or say go ahead. Facts are never inferred.
2 Shape. Names the visitor's job, then theme.mjs draw deals the page anatomy.
3 Direction. theme.mjs deal offers three themes; the agent picks one and says why.
4 to 5 Load and Picks. Loads one theme file, then posts a Picks block: your one chance to redirect.
6 Build. Hero first, linted with --stage hero and reviewed cold, then the rest.
7 Sweep. sloplint --render until clean, gates walked, fresh reviewer, then the material ask.
Picked for Anand's sites (indrayam.com, Daily Diff, Cribsheets) and CLI-tool landings. Pictures are the repo's own theme renders.
Longform posts, essays, a personal magazine voice.
Daily Diff style: dated issues, columns, a newspaper feel.
CLI tools, dotfiles, homelab, anything you install from a shell.
Typography-led pages; a single essay or manifesto.
Indexes, directories, systems; Swiss and modular.
Plain black notice; the quietest option.
A theme is a material, not a plan: it never says what a page contains or in what order, so two prompts in one theme make two different pages.
usehallmark.com shows all 48. The repo folder holds 48 theme files plus a README.
node ~/.claude/skills/hallmark/scripts/sloplint.mjs page.html # static checks node .../sloplint.mjs page.html --render # + eight widths in Chrome node .../sloplint.mjs src/ --url http://localhost:3000/ --scope page --json node .../sloplint.mjs ./src/app --before # snapshot links, fields, handlers before a redesign node .../sloplint.mjs ./src/app --kept # fail if any went missing # exit 1 on any FAIL
Run on the box against a deliberately sloppy one-screen test page (output trimmed) (24 Oct 2026):
FAIL 2a purple-to-blue gradient on .h FAIL 10a transition: all on body FAIL 20 no Hallmark stamp on the first non-empty line of any CSS FAIL 34 no overflow-x: clip on html and body FAIL 38i <em>/<i> inside <h1> FAIL 48 font-family literal "Inter" on body FAIL 48 colour literal #7c3aed outside tokens (x2) WARN 46a metric "Trusted by 10,000+": verify the user supplied this number WARN F23 the document lacks lang on <html>, a <title>, a meta description sloplint: 8 FAIL, 2 WARN across 1 file(s). # exit 1
Floor never ships. Reflex can be waived on the record. Finish never blocks.
.html and .css, plus .jsx, .tsx, .vue, .svelte, .astro (Tailwind class strings, cn/clsx/cva).
node skills/hallmark/scripts/install-hook.mjs adds a Floor check on edits, Claude Code only.
From reading 7ec8682 and running sloplint on the box.
linear-gradient(purple,blue) passed both 2a (purple-to-blue gradient) and 48 (colour literal). The same gradient written as hex (#7c3aed,#2563eb) failed both. Floor rule 11 says never a purple-to-blue gradient, so the linter misses named colours.
The brief listed build / redesign / audit / study. Only redesign and audit ship as verbs; build is the default.
package.json and SKILL.md say 2.0.0; the commit that brought in v2 is titled "Hallmark v2.2".
README says forty-eight; references/themes/ has 48 theme .md files plus README.md (49 .md files).
About 80 words per screen and no eyebrows or tracked caps. Great for landings, wrong for docs or dashboards. Use Impeccable there.
Snapshotting every link and handler before a rewrite and failing if any disappear is worth stealing for any refactor.
This rule sits on all three Design Skills sheets.
Never load Impeccable, Hallmark and Taste Skill together on one project. Pick one builder.
Each ships its own floor, bans and stamp. Impeccable writes PRODUCT.md, DESIGN.md and .impeccable/. Hallmark writes .hallmark/ and a CSS stamp. Two builders on one page argue: one deals a theme, the other rolls a visual world, and the agent splits the difference.
App, dashboard, settings, existing product UI: Impeccable. New landing or marketing page: Hallmark. Need a palette, font pair or UX rule: UI/UX Pro Max. It is a lookup, so it can sit next to either builder.
Hallmark is the builder for landing and marketing pages. Choose it, and leave Impeccable and Taste Skill unloaded on that project.