Zilmac Blog
← Back to Tech Practice

What Does Hallmark Do? Auto-Improve AI Web Pages in Claude Code—Install and Go

API & Agents ·~10 min read

Claude Code on Mac running Hallmark Skill to refine AI-generated landing page design

Ask Claude Code for a landing page and you often get the same AI look: six rounded cards, gradient buttons, one accent word in the headline, and an email capture at the bottom. It works, but it screams template. Hallmark (@nutlope, usehallmark.com) is a high-traffic 2026 Agent Skill that teaches Claude Code, Codex, and Cursor to design web pages by rules and self-check “AI slop” in a real browser with sloplint. This post covers what it does, one-line install and go, and how it fits a Claude Code workflow on a Zilmac cloud Mac. For other Skills, see our Claude Code Skills 2026 picks.

48+
Built-in themes (v2 surfaces 3 to choose)
3
Core flows: build · audit · redesign
0 FAIL
Target for sloplint --render multi-width checks

What Hallmark is (and what problem it solves)

Hallmark is not another component library. It is an Agent Skills workflow in SKILL.md: pick a theme and layout before HTML/CSS, then lint typical AI tells—low-contrast text on photos, twin solid CTAs, gradients where photos belong, tracked all-caps labels. The official site shows the same prompt with raw Opus vs Hallmark theme pages: issue counts drop toward zero on sloplint.

Unlike “please follow our design system” in chat, the steps are baked into the Skill: ask for assets once, deal themes, emit tokens.css, hero first, then browser render until clean.

What Hallmark does: three main paths

Build a landing page from scratch

Type /hallmark plus your product brief. The Skill reads the repo, asks once for real assets, deals three themes from 48+, then builds after you pick. It will not invent metrics—placeholders only.

/hallmark Build a landing page for [product]. The one action is [book a demo / download the app].
Use my screenshot URLs; only use numbers I provide.

Audit only — no file changes

/hallmark audit ./index.html

You get a sloplint FAIL/WARN report (40+ FAIL on a typical AI page is common) without edits.

Keep content, redo visuals

/hallmark redesign ./src/app

Preserves copy, links, forms, and wiring; rebuilds look and feel. Without redesign or audit, existing designs are not touched—safe to install globally.

Hallmark Skill in Claude Code running sloplint browser checks and theme selection for a landing page
v2 is “design then code”: theme tokens, layout, and sloplint browser verification are one loop—not a CSS patch at the end.

From one sentence to a shippable page

  1. Pre-flight: tokens, design.md, existing CSS variables.
  2. Material ask: photos, app shots, real stats—or placeholders, never fake KPIs.
  3. Theme deal: three candidates, or custom from your prompt under the same linter.
  4. Scaffold: tokens.css, base.css.
  5. Build: hero first; section order follows the page job—not the same six-card grid every time.
  6. Verify: sloplint --render across widths; fix to 0 FAIL, then a fresh-eyes pass.

Photos default to openly licensed Wikimedia Commons assets with credit; optional image API keys.

Install and use: Node, Skill, browser checks

node -v   # need 18+
npx skills add nutlope/hallmark -g
npm i -g puppeteer-core   # recommended; needs Chrome

Without puppeteer-core?

Static sloplint still runs, but multi-viewport render checks may miss mobile contrast, focus rings, and overlapping text.

No backend changes: Skill files live under ~/.claude/skills/hallmark or Codex’s ~/.agents/skills/hallmark. Re-run npx skills add to update.

Claude Code, Cursor, Codex invocation

ClientTypical pathInvoke
Claude Code~/.claude/skills/hallmark/hallmark …
Codex CLI~/.agents/skills/hallmark$hallmark …
Cursor / OpenCodereads installed copies/hallmark …

Use Hallmark for marketing HTML; keep repo Skills for release and tests—same governance as our Skills guide.

Safety: it won’t rewrite your site by accident

  • Acts on paths you name; normal chat won’t restyle the whole repo.
  • No fabricated facts—placeholders instead of fake “100k users”.
  • Can follow your design system via tokens and design.md.
  • Can capture app screenshots when your app runs locally.

Habits on Mac and cloud dev machines

  1. Persist ~/.claude/skills on cloud Mac home volumes.
  2. Pin team copies under .claude/skills in git with PR review.
  3. Deploy static frontend/ as usual—no server-side changes required.

FAQ

Does Hallmark need its own API key?

No for default photos. Page generation uses your existing Claude/Cursor model access.

Conflicts with Tailwind or shadcn?

Hallmark often outputs tokenized static HTML/CSS but can read your tokens. For React, scope redesign to the presentation layer.

Audit vs redesign?

Audit for a report; redesign to rescue visuals; fresh build when you want a new themed page.

/hallmark not recognized?

Verify install, restart the session, check SKILL.md exists; use a Skills-capable Cursor build.

Bottom line: Hallmark gives Claude Code design taste plus verifiable sloplint gates—one-line install, /hallmark to build, audit to inspect, redesign to rescue. Clearer than repeating “no AI slop” in every prompt.

Limited Offer

Zilmac

Cloud Mac, remote dev, and Mac VPS—Apple toolchain support for iOS and cross-platform teams.

Back to Home
Limited Offer View Plans