Hallmark is a design skill for Claude Code, Codex, Cursor and OpenCode. When you ask for a new website or page, it reads the project, asks once for real material such as photos, screenshots and numbers, deals three themes from a catalog of fifty, and builds the page around the one job a visitor comes to do.
Every build holds a floor of fixed rules: colours and fonts through tokens, no invented metrics or testimonials, visible focus states, reduced-motion fallbacks and a hero that fits the first screen. A linter checks the finished page in a browser, and a fresh-context reviewer gives the last verdict. Naming it with redesign or audit works on an existing page.
What You Get
- A /hallmark command that builds a new website or page from a prompt, dealing three of fifty themes and building from the one you pick
- Redesign and audit verbs: /hallmark redesign <path> rebuilds a page and keeps its content and wiring, and audit <path> only reports
- A linter, sloplint, that checks the output against the floor and renders the page at several widths in a real browser
- A scaffold that writes tokens.css and base.css beside your stylesheet, with a stamp comment on the first CSS line recording the decisions taken
- A library of openly licensed photographs, picked per subject and credited in the page footer
Common Use Cases
- Building a landing page for a new product from a short prompt, with the action placed where that category of site puts it
- Redesigning an existing page while keeping its content, links, forms and handlers intact
- Auditing a finished page and getting a report of the tells that read as machine-made
- Capturing screenshots of a running app and building a page that shows the real product
What Makes It Unique
Hallmark pairs its design guidance with enforcement. It holds a floor of sixteen fixed rules that no build may waive, adds Reflex gates that can be overruled on the record with a reason, and adds Finish checks that never block. A render-based linter checks the page, and a reviewer started in fresh context gives a verdict the build must act on. A log of earlier builds feeds the theme draw, so two prompts in one theme produce different pages, and the skill never invents a metric, quote or logo.
Under The Hood
The skill is a SKILL.md that routes to reference files, loading only the ones a build needs, plus Node scripts the agent runs. theme.mjs deals themes, scaffolds token files and writes a build log into a .hallmark folder in the project. sloplint.mjs lints the output and, with —render, opens the page in headless Chrome through puppeteer-core, which you install separately. capture.mjs screenshots a URL, a local file or a running desktop app and writes PNGs into the project; to find a globally installed puppeteer it runs npm root -g in a shell. imagegen.mjs sends a prompt to the Together AI image API and saves the returned image, and only when a TOGETHER_API_KEY is set; without a key the build falls back to placeholders. install-hook.mjs is an optional step that adds an edit-time lint hook to Claude Code’s settings.json. Photographs come from a JSON list of Wikimedia Commons links, which the page credits. The folder also ships test files that write files and reference the API key variable, sample Vue, TSX and CSS fixtures for testing the linter, and emoji patterns in sloplint.mjs that contain zero-width joiner and variation selector characters. None of those is run when you use the skill.