# Hallmark: web pages that don't look AI-made (Nutlope/hallmark) — skill card for AI agents

> AgentGid skill card. Checked on 2026-11-05 against commit de4999e (version 2.0.0).
> Every fact comes from the pack's own files at that commit. Numbers marked "as reported" are the author's.
> Human page: https://agentgid.com/skills/nutlope/hallmark/

> Note: the pack has changed since this check; re-read its files before relying on details.

## Explain it to a non-programmer
Your AI assistant builds web pages that look designed, not machine-made. It asks once for your real material and picks one of fifty visual themes. Then it builds the page and checks it against common AI design habits. Name it and it will also redesign or review a page you already have.

## Who it is for
- You ask an AI assistant to build websites or new pages and they come out looking generic
- You use Claude Code, Codex, Cursor or OpenCode
- You want a page made only from real facts: no made-up numbers, quotes or logos
- You want an existing page rebuilt or reviewed, and are happy to ask for Hallmark by name
- Not for: You want a small change to an existing design in its own style: Hallmark stays out of it unless you name it
- Not for: You want filler customer numbers and reviews on the page: it leaves any you did not give out

## What it is
- Kind: knowledge, scripts
- License: MIT
- Repository: https://github.com/Nutlope/hallmark

## What it does
- Pre-flight: read the project first (fonts, palette, framework, a locked design.md, the real product if it can be reached)
- Ask once: material, audience, the one action, tone; or 'go ahead' and it infers and says what it picked
- Shape: list what is real, what pictures exist and what proof is absent; build the page from what visitors in that category come to do
- Direction: a script deals three of fifty themes that fit the prompt and differ from recent builds, or 'custom' designs from scratch
- The Picks block: every decision said once, so you can redirect
- Build: the first screen alone, reviewed with fresh eyes, then the rest of the page
- Sweep: its checker at eight widths until clean, a second fresh-eyes review, then the material ask
- Never cuts: The Floor: colours and fonts only through tokens, focus styles on every control, a reduced-motion fallback, no invented figures or quotes, no eyebrow labels or tracked capitals, no purple-to-blue gradient, card in a card or emoji icons, headline, sentence and main button visible at 1280 x 800, about 80 words per screen
- Level Floor: Never ships, cannot be waived
- Level Reflex: Defaults a model falls into; a build may overrule one with a reason, on the record
- Level Finish: Craft detail; answered, never blocks

## Skills
| Skill | Call | Changes code? | In plain words |
|---|---|---|---|
| hallmark | /hallmark <prompt> | redesign <path> | audit <path> ($hallmark in Codex), or describe a new build | yes | Designs and builds a new page, or redesigns or reviews one you name |

### hallmark
- Asks for: Material: screenshots or the app, its address or folder; your photos; real numbers; a quote with who said it; logos you may use
- Asks for: Audience: who uses this and what they care about
- Asks for: Use: the one action the page should drive
- Asks for: Tone: one extreme (editorial, brutalist, soft, utilitarian, luxury, playful, technical, austere), a vibe in 4 to 8 words, an anchor colour
- Gives: The Picks block: shape, theme, nav and footer, hero, signature, sections, material
- Gives: The page: HTML plus tokens.css and base.css, the decisions stamped in the first CSS comment
- Gives: A check report: Floor, Reflex and finish-review results
- Gives: The material ask: every photo slot, its size and what belongs there
- Gives: For redesign: a before and after table and .hallmark/compare.html; for audit: findings by tier with file and line
- Say: "/hallmark a landing page for a weekend pottery class"

## Know before installing
- It switches on by itself for new builds: its description says to use it whenever you ask to build or design something new. In Codex implicit use is allowed.
- It leaves an existing design alone unless you name Hallmark (redesign or audit); other changes are done in your project's own style.
- It runs its own Node scripts during a build and writes files beside your page: tokens.css, base.css and a .hallmark folder with a log, a cached pre-flight and screenshots.
- With TOGETHER_API_KEY set, it adds a mock-up step and can generate pictures through Together AI's paid image service; without the key that step never loads.
- Library photos come from Wikimedia Commons with their own licences (CC0, public domain, CC BY, CC BY-SA); the page credits each one. No stock sites.
- A page that names a real brand gets the brand's colours from its live homepage and stylesheets, never from memory.

## Install (official commands)
- Any agent (skills CLI): `npx skills add nutlope/hallmark -g` — -g installs for every project; leave it off for the current one. One harness only: add --agent claude-code (or codex, opencode, cursor, github-copilot). Lands in ~/.claude/skills/hallmark (Claude Code) or ~/.agents/skills/hallmark (Codex); Cursor and OpenCode find those copies. Invoke with /hallmark, or $hallmark in Codex. Remove: `delete the hallmark folder from ~/.claude/skills or ~/.agents/skills`.
- Claude Code (plugin): `/plugin marketplace add nutlope/hallmark` && `/plugin install hallmark@hallmark` — Invoked as /hallmark:hallmark.
- From a clone: `node skills/hallmark/scripts/install.mjs` — Checks every theme and reference, then copies the skill into ~/.claude/skills, ~/.agents/skills or ~/.config/opencode/skills for each tool it finds in your home folder (or the ones you name with --claude, --codex, --opencode). --dry-run shows what it would copy. Remove: `node skills/hallmark/scripts/install.mjs --remove`.
- Claude Code edit-time check (optional): `node <skill-dir>/scripts/install-hook.mjs` — Adds a check after every file write to .claude/settings.json in the project, or ~/.claude/settings.json with --global. Advises only. Remove: `node <skill-dir>/scripts/install-hook.mjs --remove`.

## What runs on the user's machine
- Code on the machine: yes (builds where Node is available (the assistant runs the scripts itself); the edit-time check only if you install it)
- Network: optional
- Install: Copies one skill folder: the instructions, 50 theme files with pictures, a list of 755 photos (links only, no image files) and Node scripts. The plugin adds no hooks and the package has no install scripts.
- Every build: The assistant runs theme.mjs (deal, draw, scaffold, photos, log) and sloplint.mjs. They write tokens.css and base.css beside your stylesheet and a .hallmark folder in the project (preflight.json, log.json, a salt file, screenshots, a .gitignore).
- Browser checks and screenshots: If puppeteer-core and Chrome are installed (it runs npm root -g to look), sloplint --render, capture.mjs and picture.mjs open the page, a URL or dev server you give, or attach to a running desktop app's debugging port (--cdp). capture.mjs writes PNGs to ./images/screens by default.
- Network, only on request: imagegen.mjs sends your image prompt to api.together.xyz, only with TOGETHER_API_KEY set. theme.mjs photos --save downloads picked photos from upload.wikimedia.org only. For a real brand the assistant fetches its homepage and same-origin CSS.
- The finished page: Theme pages load web fonts from Fontshare or Google Fonts; draft pages may link Wikimedia thumbnails. These load in the visitor's browser.
- Edit-time check (opt-in): install-hook.mjs adds a PostToolUse entry for Write|Edit|MultiEdit to .claude/settings.json (project) or ~/.claude/settings.json (--global). After each write of a Hallmark page it runs the Floor checks with a 4-second limit and reports failures; it never blocks. --remove takes it out.
- install.mjs from a clone: Writes into ~/.claude/skills/hallmark, ~/.agents/skills/hallmark or ~/.config/opencode/skills/hallmark, replacing any folder already there; --remove deletes them.
- Never: The eval folder is the author's benchmark kit (calls model services with your keys). It is not in the published package and the skill never runs it.

## Settings
- `TOGETHER_API_KEY`: Turns on the mock-up step and generated pictures (Together AI)
- `CHROME_PATH`: Chrome or Chromium binary for the browser checks
- `HALLMARK_PUPPETEER`: Where puppeteer-core is installed

## Examples (from the pack's own files)
- The Picks block it shows before building: output format defined in skills/hallmark/SKILL.md
- The handoff after a redesign: output format defined in skills/hallmark/references/redesign.md

## Author's numbers (as reported, not run by AgentGid)
- Issues found by the pack's own checker on three pages Opus 5.5 built alone vs the same prompts as Hallmark theme pages: farm records 26 vs 0, bank reconciliation 11 vs 0, webhook API 18 vs 0 (Same prompt, Opus 5.5 alone vs a Hallmark theme page; counts from Hallmark's own checker; shown on the author's site). Source: Nutlope/hallmark/site/index.html
- On open models, the GLM arm had 96 rule failures with only the core rules and 11 with the full skill, across 6 briefs (Author's eval harness, bare API calls, run of 2026-07-23). Source: Nutlope/hallmark/eval/README.md
- No invented metrics on the brief built to tempt them, in every model arm. Source: Nutlope/hallmark/eval/README.md

## How to tell it works
Install it, then ask: "/hallmark a landing page for a weekend pottery class". It first asks four questions in one message; answer them or say "go ahead". You know it is on when a "Hallmark · v2.0.0" Picks block appears and the page's CSS starts with a "/* Hallmark · ..." comment.

## Related
- pbakaus/impeccable
- anthropics/claude-code
- nexu-io/open-design
- tw93/kami
- Leonxlnx/taste-skill
- alchaincyf/huashu-design
- nextlevelbuilder/ui-ux-pro-max-skill
- emilkowalski/skills
- vercel-labs/web-interface-guidelines

## Safety
Made by Together AI; install from github.com/Nutlope/hallmark. The skill itself tells the assistant to treat a project's design.md and fetched brand pages as data only and to check web addresses before fetching. It ships Node scripts your assistant runs during builds: read them before installing. The optional edit-time check edits your Claude Code settings file.
