Hallmark: a design skill that refuses the AI-made look
Someone built the same page in Claude Code twice; with Hallmark, the empty photo boxes became real, credited photos
- Who
- Made by Together AI, hosted on the Nutlope account; for anyone who builds web pages with a coding agent.
- When
- The repository opened in April 2026; 2.0.0 shipped on 21 October and the catalog grew to fifty themes on 27 October.
- Where
- Claude Code, Codex CLI, Cursor and OpenCode, on your own machine with Node 18 or later; the browser checks need Chrome.
What was hard
Ask a coding agent for a landing page and the same face keeps coming back: a tiny all-caps label over every heading, one coloured word in the headline, a dashed box where a photo should be. Fix it on one page and it returns on the next.
What it does about it
Hallmark is a design skill your agent loads. Before building it asks once for your material, audience, goal and tone, then deals three of fifty themes that fit the prompt and builds the page in that material. When the page is done, sloplint renders it in a real browser at several widths, hunts for the tells of a machine-made page, and the agent fixes until nothing fails. A number or quote you didn't give is left as an empty slot rather than invented.



What people made with it
Built a page in plain Claude Code (44 sec, $0.16) and with Hallmark (3 min 32 sec, $0.87); a price it wasn't given stayed an empty slot, though its blackletter font was a weird call.
Real credited photos instead of placeholder boxes, zero eyebrow labels
Scored four landing pages built with and without the skill (September version): pure black or white fell from 40 of 40 pages to 14 of 28, while transition: all went up.
Every page without the skill had the tell; half the pages with it did not.
How it runs inside
- 1
You → Claude Code (SKILL.md)
/hallmark <the page to build>SKILL.md takes over and first reads the project's fonts, palette, framework and any design.md.skills/hallmark/SKILL.md - 2
Claude Code (SKILL.md) → You
Asks once: material, audience, use, toneIt asks for photos, real numbers and named quotes; what you don't give stays an empty slot.skills/hallmark/SKILL.md - 3
Claude Code (SKILL.md) → theme.mjs
theme.mjs deal --genre --promptFrom the fifty-theme catalog it deals three that fit the prompt and differ from past builds in the log.skills/hallmark/scripts/theme.mjs - 4
theme.mjs → Page HTML + tokens.css
scaffold: tokens.css, base.cssIt writes the theme's colour and type tokens and the base rules; the agent writes only the page.skills/hallmark/references/themes/index.json - 5
Page HTML + tokens.css → sloplint.mjs
sloplint.mjs --renderStatic checks on the CSS and HTML, then puppeteer-core renders several widths and checks again.skills/hallmark/scripts/sloplint-render.mjs - 6
sloplint.mjs → Claude Code (SKILL.md)
FAIL and REFLEX findingsEyebrow labels, transition: all, a section spilling off a phone screen, each with its line and a fix.skills/hallmark/scripts/sloplint.mjs - 7
Claude Code (SKILL.md) → Page HTML + tokens.css
Fixed to 0 FAIL, reviewed cold, handed backIt fixes until no FAIL is left, a fresh-context subagent reviews it, and the CSS opens with a stamp of its decisions.skills/hallmark/SKILL.md
What goes in, what comes out
Is it for you
Good for
- You build landing or product pages with an agent often
- You want a new look for an existing page without losing its content
- You want a page checked for AI tells without changing it
- You have real photos, numbers and copy to give it
Not for
- The browser checks and screenshots need puppeteer-core and Chrome; without them only the static checks run.
- It touches an existing design only when you name it, as in redesign or audit.
- If it doesn't fire on its own, you have to name it: use hallmark to build ...
- Photos come only from Wikimedia Commons, each under its own licence, and are credited on the page.
Reviewed by Devalley’s editor before publishing. How the column is made