hallmark

name	hallmark
description	Anti-AI-slop design skill — generate distinctive landing pages, audit existing UIs, redesign templated pages, or study an admired URL / screenshot to extract its DNA. Use one of the verbs `audit <target>`, `redesign <target>`, `study <URL or screenshot>`, or just ask Hallmark to build you a new page and it will fire. — Fires when ANY of these match — (1) the user names one of Hallmark's explicit verbs (`audit`, `redesign`, `study`, e.g. "audit this UI", "redesign this page", "study this screenshot", "study this URL"); (2) the user says a UI "feels AI-generated", "looks templated", "looks like every other AI page", or asks to "make it less AI-generated"; (3) the user attaches a screenshot OR pastes a URL of a design they admire and wants the DNA extracted (the `study` verb); (4) the user invokes the skill by name ("use Hallmark", "/hallmark"); OR (5) the user asks for a GREENFIELD full-page or full-site build with no existing styled UI to preserve — e.g. "build me a landing page for X", "make the marketing site for Y", "design the homepage for Z", "create a new product page from scratch", "build a portfolio site". DO NOT trigger on (i) component-scope requests ("design a button", "add a navbar", "fix this form", "build me a modal"); (ii) iteration on an existing styled page or codebase ("tweak the spacing", "update the hero copy on my page", "make the CTA bigger", "add a section to this layout") — anything where preserving the current aesthetic matters; (iii) any request inside a codebase that already has a design system or styled pages, unless the user explicitly invokes Hallmark by name. The decisive signal — is there existing styled UI here that the user wants preserved? If yes, stay silent and let frontend-design or other tools handle it. If no (true greenfield page/site), fire.
version	1.0.0

Hallmark

A design skill for AI coding assistants. Makes the UIs they generate look made, not generated.

Hallmark is opinionated, short, and boring on purpose. It encodes a tight set of rules — drawn from the consensus of the anti-AI-slop design field (impeccable, kami, Anthropic's frontend-design skill, taste-skill, the Claude cookbook on frontend aesthetics, and the 2026 "tactile rebellion" movement) — and refuses to let the model fall back to the defaults every LLM was trained on.

The differentiator: Hallmark insists on structural variety, not just visual variety. Two pages by Hallmark for two different briefs should not share the same hero → 3-feature → CTA → footer rhythm. They should feel like different sites, not different colour-swaps of the same template. See references/structure.md.

Powered by Together AI.

---

How to use this skill

Hallmark has one default behaviour and three explicit verbs.

Invocation	What it does
(default)	The user asked you to design or build something new. Follow the Design flow below.
hallmark audit <target>	Read the target, score it against the anti-pattern list, return a ranked punch list. Do not edit.
hallmark redesign <target> [--mood <name>]	Take the target's content and intent, throw out the structure, and rebuild it from scratch with a deliberately different structural fingerprint. New section rhythm, new heading placement, new component voice. Preserve copy, brand, and information architecture; replace everything else.
hallmark study <screenshot | URL>	The user pasted or attached an image of a design they admire, or pasted a URL to a live page. Extract the DNA — macrostructure, archetypes, type-pairing, colour anchor — and produce a diagnosis report, then optionally rebuild the user's content using the extracted DNA or emit a portable design.md of the DNA. Detection is automatic: a URL (http:// / https:// prefix) routes to URL mode; anything else routes to image mode. URL mode reads the page's HTML and CSS via WebFetch — it can name exact fonts and exact colour values, but can't judge rhythm. After the diagnosis, the user has three follow-ups: build with the DNA (handoff to default), lock the DNA into a portable design.md (opt-in via "lock the DNA" / "give me a design.md"), or stop at the diagnosis. Never copies pixels. Refuses template-marketplace URLs and competitor pages. Tighter refusal layer for design.md emission than for the diagnosis itself — URL-mode emission requires attestation that the source is the user's own or a public reference for their own brand. Falls back to asking for a screenshot if the URL is auth-walled, a JS-only SPA shell, or otherwise un-readable. Load references/study.md before this verb runs.

If the user types anything that does not clearly map to audit, redesign, or study, treat it as default. If the user attaches an image or pastes a URL without a verb prefix, ask: "Should I study this (extract the DNA), or should I treat it as a reference for a fresh build?"

The default Design flow always picks a theme. By default it picks one of the 22 named themes — the catalog — and rotates among them per the diversification rule. There is also a quiet custom branch that constructs a one-off OKLCH palette + free-font pairing for the brief; the custom route fires only when the brief carries a creative-intent signal (the user names a brand colour, names a multi-attribute vibe the catalog can't carry, or explicitly asks for a custom theme). For vanilla briefs, the user never sees the words "catalog" or "custom" — the catalog runs silently. See Step 1 (signal detection) and Step 2.6 (dispatch); the protocol lives in references/custom-theme.md.

---

Disciplines that hold across every verb

These four disciplines are not verb-specific. They apply to default Design, audit, redesign, study, and component-scope alike. They sit alongside the slop test, not inside one branch of it.

1. Pre-emit self-critique. Before handing back any output, score it 1–5 on six axes — Philosophy, Hierarchy, Execution, Specificity, Restraint, Variety. Anything < 3 triggers a revision pass. Stamp the six scores at the top of the artifact (/* Hallmark · pre-emit critique: P5 H4 E5 S4 R5 V5 */). See references/slop-test.md § Pre-emit self-critique.

2. Honest copy — no fabricated content. If the user did not supply a metric, do not invent one. Stat-led layouts, comparison rows, and proof bars must use real numbers, a placeholder (— plus a labelled grey block, "metric to confirm"), or a different macrostructure. "+47 % conversion", "trusted by 50,000+ teams", and "10× faster" are slop the moment they're invented. Same rule for testimonials, logos, and case-study counts. See references/anti-patterns.md § Invented metrics and slop-test gate 56.

3. Locked tokens — no mid-render improvisation. Once a theme is selected at Step 2.6, every colour and every font-family declaration in the artifact must reference a named token (var(--color-accent), font-family: var(--font-display)). Inline OKLCH / hex / rgb() values, or a font-family: "Some Font" declaration that bypasses the token block, are not allowed. If a value is needed that doesn't exist as a token, lift it into the token block as a new named variable, then reference it. See references/anti-patterns.md § Mid-render token improvisation and slop-test gate 58.

4. Re-drawn chrome forbidden. Hallmark must not hand-build fake browser bars (URL pill + traffic-light dots), fake phone frames, fake code-block windows (mock title bar + dots wrapping a <pre>), or fake IDE chrome — the user's environment already supplies real chrome. Use real screenshots wrapped in a <figure> (with at most a hairline border), or omit the chrome and let the content stand on its own. See references/anti-patterns.md § Re-drawn UI chrome and slop-test gate 57.

5. Mobile responsiveness — every emit verified at 320 / 375 / 414 / 768 px. Hallmark's output must render flawlessly at all four widths. The non-negotiables: no horizontal scroll (gate 36), no two-line clickable text — buttons, primary nav links, footer links, breadcrumbs, CTAs (gate 59); image-bearing grid tracks use minmax(0, 1fr), never bare 1fr (gate 61); root has overflow-x: clip on both html and body — never hidden (gate 62); display headers wrap inside long words via overflow-wrap: anywhere; min-width: 0 (gate 63); section heads collapse to one column on mobile across every theme variant (gate 64); radio-tab patterns don't scroll-jump (gate 65). See references/responsive.md § Mobile — non-negotiable. This is a hard floor, not a wish list.

---

When the brief is a component, not a page

Before entering the full Design flow, check scope. If any of these fire, run the Component-scope flow instead — most day-to-day dev requests are component-shaped, not page-shaped, and the page-level apparatus (macrostructure, hero enrichment, footer archetype, project memory) is wrong for them.

Component-scope signals:

• The brief names a single UI element: a button · an input · a card · a modal · a dropdown · a tooltip · a select · a checkbox · a switch · a tab strip · a chip · a badge · a banner · a snackbar · a popover · a slider · a date picker · an avatar.
• The brief is short (≤ 30 words) and refers to one element.
• The target file is a single component (e.g., ./Button.tsx, ./components/Input.css, app/components/Card.vue).
• The user explicitly says "just the X", "only the Y", "this one element", "a single ___".

If two signals fire, route component. If only the page flow fires (multi-section brief, "build me a landing page"), stay in Design flow.

What Component-scope keeps from the page flow

• Step 0 · Pre-flight scan — same. Read existing tokens, fonts, framework, microinteraction stance. A button on a Geist-bodied Tailwind project must adopt those tokens, not invent new ones.
• Step 1 · Genre detection — same. Editorial / modern-minimal / atmospheric / playful. The component inherits its surroundings' genre (silent default to editorial when unknown).
• Step 2.6 · Theme route — same. If a tokens.css or design.md exists, the component uses those tokens. Otherwise it asks "is there a system to follow, or should I pick one?" — defaulting to catalog if the user is silent.
• 2+1 font discipline — same.
• State discipline — STRICTER. Every interactive component MUST ship code for all 8 states: default · hover · :focus-visible · :active · disabled · loading · error · success. The 8-state checklist in interaction-and-states.md is mandatory, not advisory.
• Slop test — universal-only subset. Run the visual / microinteraction / contrast (gates 46–50) / a11y / typography gates. Skip the diversification gates (no .hallmark/log.json entry — components don't rotate) and skip the layout-safety gates that assume a full page.

What Component-scope skips

• Step 2 · Macrostructure pick. Components don't have macrostructures. State this explicitly: "Component-scope: skipping macrostructure."
• Nav and footer archetype picks. N1–N9 and Ft1–Ft8 are page-scope only. A component is one element; it has no nav, no footer. Skip both.
• Hero polish patterns (HP1–HP4). Page-scope only. A button or card has no hero.
• Step 4 · Enrichment. No hero illustration, no demo video, no abstract background. The component IS the artifact.
• Step 5 · Multi-section preview. Replaced by the 8-state demo wrapper (below).
• Project-memory append. No .hallmark/log.json entry for component runs. The diversification rule doesn't apply.

What Component-scope emits

Two files, side by side:

1. The component artifact — a single self-contained file matching the project's conventions:

   • React / Vue / Svelte: Button.tsx / Button.vue / Button.svelte
   • Vanilla web: button.css + button.html
   • Tailwind: a .tsx with className chains AND a tokens.css if missing
   • The component consumes Hallmark tokens by name (var(--color-accent)), never inlines OKLCH values.

2. An 8-state demo wrapper — <ComponentName>.preview.html (or .preview.tsx). A small standalone page that renders the component in all 8 states stacked vertically, each labelled. The user opens it once, sees the component working, then deletes it. The wrapper is not part of production code. Format:

   ┌──── Button — 8 states ────────────────────────┐
   │                                                │
   │ default       [ Click me                  ]    │
   │ hover         [ Click me                  ]    │  ← .is-hover forces :hover styling
   │ focus         [ Click me                  ]    │  ← .is-focus forces :focus-visible
   │ active        [ Click me                  ]    │  ← .is-active forces :active
   │ disabled      [ Click me                  ]    │  ← disabled attr
   │ loading       [ ⌛ Working…                ]    │  ← data-state="loading"
   │ error         [ ⚠ Try again               ]    │  ← data-state="error"
   │ success       [ ✓ Saved                   ]    │  ← data-state="success"
   │                                                │
   └────────────────────────────────────────────────┘
   

   Each labelled row uses a class (e.g. .is-hover) that the component's CSS targets in addition to the real pseudo-class, so all 8 states render at once on the demo page. Example:

   .btn:hover, .btn.is-hover { background: var(--color-paper-3); }
   .btn:focus-visible, .btn.is-focus { outline: 2px solid var(--color-focus); }
   .btn:active, .btn.is-active { transform: translateY(1px); }
   

Stamp format for component output

Components stamp differently from pages:

/* Hallmark · component: <type> · genre: <genre> · theme: <theme>
 * states: default · hover · focus · active · disabled · loading · error · success
 * contrast: pass (46–50)
 */

The component: prefix tells future Hallmark runs this artifact is component-scoped and shouldn't trigger page-level diversification rules. The states: line is a checklist — every state listed must have actual styling in the file.

When in doubt — ask once

If the brief is ambiguous between component and page (e.g. "design a pricing section" — could be one card, could be a whole page), ask one short question: "One pricing card, or the whole pricing page?" Default to component if the user doesn't engage — single-artifact output is cheaper to redirect than a multi-section page.

---

Design flow (default)

0. Pre-flight scan

If the project already has code — a package.json, a tailwind.config.*, an index.html, any CSS — Hallmark should read it before asking the user anything. Stomping on an established palette or font stack is the difference between a skill the user keeps and a skill the user uninstalls.

Six signal sources, scanned in order:

0. design.md — at the project root (or DESIGN.md). If present, this is the locked design system for the project — written by a previous hallmark redesign run on the whole app, or by hand. Read it first; it overrides everything else. Subsequent picks (genre, theme, type, motion) defer to it. The diversification rule is inverted on design.md-managed projects: pages must share the system, not differ from each other. See verbs/redesign.md § Multi-page flow for how the file is produced and amended.
1. Font stack — package.json for next/font, @fontsource/*, expo-google-fonts, geist; any <link rel="stylesheet" href="...fonts.googleapis.com/..."> in HTML / layout files; tailwind.config.{js,ts} theme.extend.fontFamily; @import url("fonts.googleapis.com/...") in any stylesheet.
2. Palette — OKLCH / HSL / hex values inside :root blocks; tailwind.config theme.extend.colors; any tokens.json, design-tokens.{json,yaml}, or DTCG-shaped file.
3. Microinteraction stance — package.json dependencies for framer-motion, gsap, motion, lenis, lottie-react, @react-spring/*, auto-animate. Any one of those = "motion-on" project. None = "motion-cut" project.
4. Spacing scale — Tailwind theme.extend.spacing; CSS --space-* custom-property pattern; presence of a 4-pt or 8-pt scale.
5. Framework — Next.js (next in deps), Astro (astro), Vue (vue), Svelte / SvelteKit (svelte / @sveltejs/kit), Remix (@remix-run/*), or vanilla HTML.

Output format — emit this block once, before Step 1, with file:line citations so the user can verify what you found:

Pre-flight findings:
· Font stack: Geist + Geist Mono (next/font, package.json L23)
· Palette: OKLCH custom properties (app/globals.css :root)
· Motion: framer-motion 11 installed (package.json L41)
· Spacing: Tailwind extend.spacing (4-pt scale, tailwind.config.ts L18)
· Framework: Next.js 15 (app router)

Hallmark will preserve: font stack, palette, spacing scale.
Hallmark will introduce: macrostructure, microinteraction discipline,
slop-test gates, hero enrichment recipe.

If you want Hallmark to override any preserved item, say so.

Persistence. Write the findings to .hallmark/preflight.json once. On subsequent runs, re-use the cached findings unless either:

• the user says "refresh pre-flight" (or "scan again", "re-scan"), or
• package.json / tailwind.config.* mtimes are newer than preflight.json.

If the cache is re-used, emit a one-line note instead of the full block: "Pre-flight cached (last scan: 2026-04-30). Say 'refresh pre-flight' to re-scan."

Edge cases:

• design.md found → emit "design.md detected at project root — this is a system-managed project. Reading the locked design system; subsequent picks defer to it." Then read the file in full and use it as the source of truth for genre / theme / typography / spacing / motion / CTA voice. Skip Step 1's catalog/custom dispatch; the system is already chosen. Proceed to macrostructure pick (Step 2) within the family design.md allows for this page's type.
• No signals found (vanilla HTML project, empty repo, scratch directory) → silent. One line only: "No pre-flight signals — proceeding with full Hallmark stack."
• Conflicting signals (e.g. framer-motion installed but no motion.div usage anywhere; or Geist import in package.json but font-family: Inter hard-coded in CSS) → flag the conflict explicitly: "Conflict: Geist imported via next/font but a hard-coded font-family: Inter in app/globals.css L4. I'll preserve next/font Geist; please confirm or remove the Inter declaration."
• Empty project (no package.json, no index.html) → silent.
• The user said "ignore the existing project" → skip pre-flight entirely; emit "Pre-flight skipped at user request." and proceed to Step 1.

Two more sample outputs for the model to imitate:

Vanilla HTML project, motion-cut:

Pre-flight findings: vanilla HTML, no framework detected. No motion library, no Tailwind, no design tokens. Hallmark will introduce: full token system, macrostructure, microinteraction discipline, slop-test gates. Nothing to preserve.

Astro + Tailwind + DTCG tokens already present:

Pre-flight findings: Astro 5 (astro.config.mjs L1) · Tailwind v4 with @theme inline tokens (src/styles/global.css L3) · tokens.json at project root (DTCG format, 12 colour tokens, 6 font tokens). No motion library detected. Hallmark will preserve: Tailwind tokens, the tokens.json file (won't overwrite). Hallmark will introduce: macrostructure, microinteraction discipline, slop-test gates. Motion stance: motion-cut (no framer-motion / motion / gsap detected).

The pre-flight block is the user's accountability line: "here's what I noticed about your project before I touched anything." Skipping it is the fastest way to lose the user's trust.

1. Design-context gate

Hallmark works best when you know three things before writing code:

1. Audience. Who will use this? What do they already know?
2. Use case. What single job does this interface do? What is the one action the user should be able to take?
3. Tone. Pick an extreme — editorial, brutalist, soft, utilitarian, luxury, playful, technical, austere. "Clean and modern" is not a tone.

Always ask — answering is optional. Hallmark always asks before it designs. The bundled question is the first thing the user sees after the pre-flight block. Even on a five-word brief — "design a podcast site", "build a SaaS landing", "make me a portfolio" — ask. Especially on those briefs, since they're where the model is most tempted to invent.

The prompt format:

Before I build, I need three things:

1. Audience — Who will use this? What do they care about? 2. Use case — What's the one action the page should drive? (Sign up? Subscribe? Read? Buy?) 3. Tone — Pick an extreme: editorial · brutalist · soft · utilitarian · luxury · playful · technical · austere. "Clean and modern" isn't a tone.

Or say "go ahead" and I'll infer from the brief — I'll tell you what I picked.

Send the prompt once, in one message. Bold the three labels (Audience / Use case / Tone) so the user can scan them. Do not ladder follow-ups; if the user answers some fields and skips others, treat the skipped fields as opt-out and infer them. If the user says "go ahead", "you pick", "just build it", "don't ask", or doesn't engage after one prompt, the inference protocol below kicks in.

One exception where the gate is silent:

• The skill is invoked with audit, study, or redesign --mood — those verbs read context from the target, not the user.

There is no "the brief looks complete" exception. There is no "the user already named all three" exception. There is no length threshold below which asking is skipped. A long, detailed brief gets the same three-question prompt as a five-word one — the user can wave you through with "go ahead" in two seconds. Default is to ask. The cost of asking is one extra message; the cost of guessing wrong is a whole rebuild.

Genre — pick before themes. Before the theme route, settle on a genre. Hallmark ships four: editorial (default · the canonical anti-slop voice), modern-minimal (Stripe / Linear / ElevenLabs school), atmospheric (Suno / Runway / dark-AI-tool school), playful (post-Linear soft school). The genre scopes which themes can rotate, which slop-test gates apply, and which voice fixtures the LLM picks from. Detection is signal-based — silent default to editorial unless the brief fires one of these:

• AI tool, generative, music, video, voice, late-night, dark mode, atmospheric → atmospheric → load references/genres/atmospheric.md
• SaaS, enterprise, API, platform, developer tool, infra, B2B, dev experience → modern-minimal → load references/genres/modern-minimal.md
• fun, consumer, casual, friendly, onboarding, family, community → playful → load references/genres/playful.md

If two non-default signals fire (rare), ask one short follow-up: "This brief fits both modern-minimal and atmospheric — which feels closer? [modern-minimal · atmospheric]". Default with no signal: silent editorial → load references/genres/editorial.md. The chosen genre file is loaded eagerly (it scopes everything downstream); other genre files stay on disk.

State the genre out loud at Step 2.5 alongside the macrostructure and theme picks: "Genre: atmospheric. Macrostructure: Marquee Hero. Theme: Bloom (atmospheric cluster)."

Theme route — only surface when the brief signals it. Hallmark has two theme routes: catalog (the 22 named themes — Specimen, Atelier, Brutal, Salon, Newsprint, Linen, Studio, Manifesto, Terminal, Midnight, Almanac, Garden, Quiet, Riso, Sport, Bloom, Coral, Violet, Aurora, Halo, Plume, Editorial) and custom (an OKLCH palette + free-font pairing tuned to this one brief). Catalog is the default. The catalog rotation is scoped to the genre's theme cluster — atmospheric rotates Bloom/Midnight/Terminal, modern-minimal stays on Quiet, playful stays on Plume, editorial walks the remaining twelve. Do not offer the user a choice on every prompt — that's friction, not discipline. Surface the catalog/custom fork only when the brief carries one of these signals:

• The user explicitly says custom theme / tailored to our brand / make it ours / something unique / play with the colors and fonts.
• The user names a specific brand colour as the anchor (e.g., "use our terracotta", "the brand red is hex #c0392b", "anchor on sea-blue").
• The user describes a multi-attribute aesthetic that doesn't map to a single catalog theme — three or more vibe words pointing at a specific feel (e.g., "moss, lichen, soft pink, herbal" / "sun-drenched, market-day, carbon-black" / "late-night, neon, brutalist deli"). One adjective ("warm", "technical", "playful") is not a custom signal — that's a tone, and the catalog already carries it.
• The user attaches a brand-mood reference (a colour swatch, a moodboard, a Pantone chip) without asking to study a screenshot.

If any of those fires, ask one short follow-up before picking: "This brief reads like a custom palette would fit better than the catalog. Want me to construct a custom OKLCH palette + free-font pairing tuned to , or stay on the catalog for variety + speed?" Wait for the user to say custom (or catalog). Default is still catalog — silence routes to catalog, not custom.

If none of the signals fires, proceed with catalog silently. Do not mention the fork. Most briefs don't need a custom theme — the catalog's 22 themes plus the rotation rule already deliver structural variety. See Step 2.6 for the dispatch.

If the user opts out or skips fields (says "go ahead", "you pick", "skip", "just build it", "don't ask", answers some fields and leaves others blank, or simply doesn't engage with the question after one prompt):

• Infer audience, use case, and tone from the brief, the domain, and any visible context (filename, framework, surrounding code is fair game now — only because the user delegated).
• State the inferences in one sentence at the top of your reply — "Going with: audience = X · use = Y · tone = Z. If any of those is wrong, tell me and I'll redirect."
• Stamp them in the CSS comment alongside the macrostructure (Step 4 below). The stamp is now the durable record.
• Pick a non-default macrostructure — Specimen-fall-through is still banned, even on inferred briefs.

Do not skip the inference disclosure. The opt-out is a courtesy to lazy users, not an excuse for the skill to be opaque. If the user can't see what was inferred, they can't redirect when it's wrong.

Once the three are settled (asked or inferred), restate them in one sentence and proceed.

2. Pick a macrostructure FIRST

Before loading any visual ruleset, read the slim index at references/macrostructures.md and pick one of the twenty-one named macrostructures. The index is one-line-per-macro; pick a name, then load ONLY that one per-macro file from references/macrostructures/ (e.g. references/macrostructures/05-workbench.md). Do not load the whole catalogue — that's ~37 KB of dead weight for a single pick. Each macrostructure is a complete page-shape — heading placement, body composition, divider language, button voice, image treatment, reveal — bundled as a single named choice. Picking one named macrostructure is faster and more varied than choosing six independent axes from scratch.

Diversification rule (mandatory). Before you pick:

1. Look in the target codebase for an existing /* Hallmark · macrostructure: <name> · ... */ stamp at the top of any CSS file. If you find one, your pick must be a different macrostructure.
2. If you have produced any other Hallmark output for this user in this session, your pick must be a different macrostructure than the last one.
3. The Specimen macrostructure (numbered left-margin labels + huge serif + asymmetric spans + typographic CTA) is no longer a default. Reach for it only when the brief is explicitly editorial, foundry-adjacent, or the user has named it.

Theme-diversification rule (mandatory). Picking a different macrostructure isn't enough on its own — two consecutive Hallmark outputs can share a theme even if their structures differ, and the result reads as repetition. Two consecutive themes must differ on at least one of three axes:

• Paper band — dark (L < 30 %) / mid (30–85 %) / light (> 85 %), per the theme's --color-paper lightness
• Display style — italic-serif (Specimen, Studio, Atelier) / roman-serif (Newsprint, Salon, Linen) / geometric-sans (Plume, Manifesto) / mono (Terminal) / display-condensed-italic (Sport) / display-heavy (Brutal) / system-native (Quiet) / risograph-bold (Riso)
• Accent hue — warm (red / orange / amber: 10–60°) / cool (blue / indigo / cyan: 200–300°) / neutral (no chromatic accent: Quiet) / chromatic-other (green: Studio · sage: Garden · phosphor: Terminal)

If the previous output was Specimen (light · italic-serif · warm), the next can be Studio (light · italic-serif · chromatic-green) — the accent hue differs. But the next can't be Salon (light · roman-serif · warm) which only differs on display style and shares both paper band and accent — pick a more distant theme.

The per-theme axis values live as comments at the top of each theme's tokens block in site/css/tokens.css. When in doubt, name your candidate theme out loud and identify its three axis values; if two of three match the previous output, redirect.

State your pick. Before writing any code, say "Macrostructure: . Theme: . Differs from the last on: ." in plain text. This is a deliberate accountability step — picking on the page (not in your head) prevents the default-attractor sameness that kept the skill emitting Specimen output.

If the brief is genuinely vague (no theme, no tone), do not default. Offer the user three macrostructures from categorically different groups (e.g. one grid-led like Bento, one document-led like Long Document, one poster-led like Manifesto). Three concrete choices, not seven abstract tones.

The macrostructure picks five of the six structural axes for you; you only need to pick the reveal yourself. The deeper axis catalogue is still in references/structure.md when you need to deviate from the macrostructure's defaults.

Pick a nav archetype (N1–N10) and a footer archetype (Ft1–Ft8) at this step. They are not optional chrome; they are part of the page's structural fingerprint. Read the slim index at references/component-cookbook.md and the routing tables at its bottom — the genre's default plus the acceptable alternates. Then load ONLY the picked archetype files from references/components/ (e.g. components/n5-floating-pill.md + components/ft5-statement.md). A typical build loads 5–7 archetype files total (1 hero + 1 section head + 1–2 features + 1 CTA + 1 footer + 1 nav). Do not load the cookbook end-to-end — that's ~55 KB of archetypes you won't use. State both picks alongside the macrostructure: "Macrostructure: Marquee Hero. Nav: N5 Floating pill. Footer: Ft5 Statement. Theme: Bloom."

Default away from N1 and Ft3. N1 (wordmark + 4–5 inline links + button-right at full width) and Ft3 (4 columns of links + social row + tiny copyright) are the most-recognised AI fingerprints. Reach for N5–N9 and Ft1/Ft2/Ft4/Ft5/Ft6/Ft7/Ft8 by default; reach for N1 only when the page genuinely has 2 destinations and the genre allows it; reach for Ft3 only on a genuine docs root or hub.

Diversification extends to nav + footer. Across consecutive Hallmark runs in the same project session (per .hallmark/log.json), no two outputs should share the same nav archetype OR the same footer archetype. If the previous run used N5 + Ft5, the next picks N6/N7/N8/N9 + Ft1/Ft2/Ft4/Ft6/Ft7/Ft8 from the routing tables. The nav and footer picks are recorded in the macrostructure stamp at Step 6.

2.5. Check project memory

If the project has a .hallmark/log.json file (created by previous Hallmark runs), read it before picking the macrostructure or theme. The schema is a JSON array, newest entry first:

[
  { "date": "2026-04-30", "macrostructure": "Bento Grid",   "theme": "Linen",   "enrichment": "E1 clipped-edge",  "brief": "Tracejam · SaaS observability" },
  { "date": "2026-04-28", "macrostructure": "Long Document","theme": "Linen",   "enrichment": "E5 hand-built SVG", "brief": "Maple Street Bread · bakery" },
  { "date": "2026-04-25", "macrostructure": "Manifesto",    "theme": "Manifesto","enrichment": "none",            "brief": "Meridian · studio manifesto" }
]

Use the last 3–5 entries to inform diversification:

• Your macrostructure pick must not match any of the last three.
• Your theme pick must differ from the last on at least one axis (see the theme-diversification rule above).
• Your enrichment pick should not be the same enrichment archetype as the last (E1 clipped twice in a row reads as templated, even with different content).

If the file doesn't exist, this is the first Hallmark run for this project — no constraint, but you'll create the file in Step 6.

If the project has a CSS stamp but no log.json, infer one entry from the stamp and proceed.

State the rotation in plain text before picking. This is the user's accountability line for diversification — picking on the page (not in your head) is what keeps the skill from drifting back into Bento-Grid-by-default. The format:

"Last 5 builds: Bento Grid (Tracejam) · Bento Grid (Foundry) · Long Document (Maple) · Manifesto (Meridian) · Quote-Led (Tide). Bento Grid used 2 of 5 — picking from {Marquee Hero, Stat-Led, Workbench, Letter} this time. I'll go with Marquee Hero."

Then the theme rotation, on the next line:

"Last 3 themes: Linen · Plain · Salon. Picking from {Newsprint, Atelier, Studio, Garden} — Newsprint differs on display style and accent hue."

Three sample shapes to imitate:

• First-time (no log.json, fresh project): no rotation block at all — just the macrostructure pick. "This is the first Hallmark run for this project. Picking Long Document — fits the Coffeebox brief's editorial tone."
• Mature project (5+ entries in log.json): the format above — frequency count, exclusion list, pick.
• User overrode last run ("use Bento Grid again, I want the same shape"): "Last build was Bento Grid (you requested it). You've asked for it again — I'll pick different knob values. Knob deltas: tiles=8 (was 6), accent=full-bleed (was corner-only), spans=irregular (was even). Same archetype, different fingerprint."

The rotation block keeps the user inside the discipline without making them read the rules. Skip it and the user starts thinking the diversification is theatre.

2.6. Theme route — studied-DNA, catalog, or custom

By the time you reach this step, one of four things is true:

0. A study diagnosis was emitted earlier in this conversation and the user is asking to build from it (phrases: "build it", "make it", "use this DNA", "build with this" — immediately following the diagnosis) → theme route is studied-DNA. Skip catalog/custom dispatch entirely. The studied paper OKLCH, accent OKLCH, type roles (with named candidates), macrostructure, and nav/footer archetypes from the diagnosis become the locked system for this build. Diversification is suspended — you're following an external DNA, not rotating the catalog. The Step 6 stamp records theme: studied-DNA (source: <URL or image>) plus the actual OKLCH/font values inline. If the user later pivots with phrases like "use Linen instead" / "ignore the DNA" / "rotate to a different theme", route back to the normal dispatch below and resume diversification. Continue to Step 3.
1. The user named custom (because they said so, or because Step 1's signal detection fired and they confirmed) → load references/custom-theme.md, ask the one follow-up (vibe in 4–8 words + optional anchor colour), construct the OKLCH palette + free-font pairing, compute the three axis values (paper-band / display-style / accent-hue), then continue to Step 3.
2. The user named catalog (or implicitly accepted it by not naming custom) → pick one of the 22 named themes per the diversification rule above. Existing flow — continue to Step 3.
3. Neither was discussed (Step 1's signals didn't fire — vanilla brief) → default to catalog. Do not pause. Do not ask. Continue to Step 3.

Custom is a quiet branch, not a default question. Most briefs route to catalog and the user never sees the words "catalog" or "custom." The 22 named themes plus the rotation rule already deliver structural variety; the fork is reserved for when the brief specifically asks for a tuned look the catalog can't carry.

A custom theme is a complete OKLCH palette + font pairing tuned to the brief — not a one-off colour swap, not an excuse to bypass the rules. Every constraint in color.md, typography.md, and anti-patterns.md still applies. The 65 slop-test gates fire unchanged. The Step 5 preview block surfaces the palette + pairing in plain text before any code is emitted, so the user can redirect.

The diversification rule is theme-route-blind: a custom run that follows another custom (or a catalog) must differ on at least one of the three axes from the previous entry, same as catalog-vs-catalog. Custom entries record their three axes explicitly into .hallmark/log.json (see custom-theme.md § F).

3. Load the visual ruleset

The non-negotiables live in references/. Be precise about what to load when. Discipline matters — over-eager loading is the largest avoidable cost of running Hallmark.

Always-load (eager — 1 file):

• The genre file picked in Step 1 — genres/editorial.md, genres/modern-minimal.md, genres/atmospheric.md, or genres/playful.md. Scopes everything downstream.

Index-then-pick (read the slim index, then load only the picks):

• macrostructures.md — slim index of the 21 macros. Pick one name from the index, then load ONLY references/macrostructures/<NN-slug>.md for that pick. Never load the whole index plus more than one per-macro file in a single build. ~30 lines per per-macro file vs. 660 lines for the old monolith.
• component-cookbook.md — slim index of 46 component archetypes (9 heroes, 5 section heads, 6 features, 4 CTAs, 4 testimonials, 8 footers, 10 navs) + the nav + footer routing tables at the bottom. Pick your archetype codes (H#, S#, F#, C#, T#, Ft#, N#) from the index, then load ONLY the matching references/components/<code>-<slug>.md files. A typical build loads 5–7 archetype files. Loading the cookbook end-to-end or pre-loading more than one archetype per category is the single biggest token waste in the skill — don't.

Load-per-build (universal rules — load every build):

• typography.md — fonts, scale, pairing, weights, measure, hero headline sizing
• color.md — OKLCH, palette construction, accent discipline
• layout-and-space.md — 4 pt scale, grid-breaks, asymmetry, depth
• motion.md — durations, easings, what to animate, reduced-motion
• copy.md — verbs, labels, error structure, link text
• anti-patterns.md — the named tells you must not emit

Load-conditionally (only when the page actually needs it — be honest, do not pre-load "for safety"):

• microinteractions.md — load whenever the output has any interactive element (buttons, inputs, modals, tabs, dropdowns, toasts, drag handles, copy buttons). That is most pages.
• interaction-and-states.md — load when the page has stateful UI (forms, command palettes, optimistic updates).
• responsive.md — load when mobile is in scope.
• structure.md — load only when deviating from a named macrostructure.
• hero-enrichment.md — do NOT load at Step 4 unless the image-need check in the next paragraph returns YES. Most builds are typography-only and never touch this file. The decision is one quick read of the brief, not a defensive auto-load.
• custom-craft.md — load only when an enrichment archetype requires construction (CSS art, SVG, declarative animation, etc.).
• assets.md — load only when an enrichment archetype needs an external asset (icons, illustration, photography, Lottie).
• custom-theme.md — load only when Step 2.6 routes to custom. The full custom branch (palette construction, font pairing, axis computation) lives there; SKILL.md only carries the dispatch.
• design-md.md — load only when the user explicitly asks Hallmark to lock the system into a portable file (phrases: "lock the system", "give me a design.md", "make this portable", etc.). Opt-in; never fires on a vanilla build.
• preview-examples.md — load only if you need a worked example of the Step 5 preview block format. The bullet list in Step 5 itself is normally enough; reach for the file only when picking unusual macrostructures / custom themes.

Load-at-the-end (Step 7 only):

• slop-test.md — strictly Step 7, after Build. The 66 gates are a post-emit check, not a pre-emit reference. Pre-loading slop-test.md costs ~7K tokens for nothing — the gates inform fixes, not generation. If a gate fails at Step 7, fix and re-test; do not consult the file earlier "to know what to avoid" — that's what anti-patterns.md is for.
• contract.md — load at handoff time for output-contract + scope rules.
• export-formats.md — load at Step 6 only when the project warrants multi-format exports (i.e. has a design.md). Single-page builds emit tokens.css from the in-memory token state and don't need this file.

Verb-specific:

• verbs/audit.md, verbs/redesign.md — load only when that verb runs.
• study.md — load only when hallmark study runs.

Human-only (do NOT auto-load):

• ../docs/recipes.md — eight worked briefs for human readers.
• ../docs/study-examples.md — three worked DNA-extractions for human readers.

4. Decide on hero enrichment

Most pages don't need it. The strongest hero is often a typographic one. Reach for hero-enrichment.md only when the brief points there — a SaaS / dev-tool brief wants a demo video or mockup; a bakery / café / atelier brief wants a hand-built illustration; a manifesto wants nothing.

First — does the brief need imagery at all? Run the image-need table at hero-enrichment.md § Image-need detection. Default is typography-only. If the brief signals "needs photographic content" (e-commerce, team, food, travel) AND the user hasn't supplied real assets, use the placeholder strategy in assets.md § Placeholder strategy. If the brief allows non-photographic imagery (SaaS landing, manifesto, agency splash, editorial-led), prefer the imagery-kit.md over photo placeholders. Never ship invented stock photos as if they were the final design.

Eyeball the brief or ask one short question. State the decision in one sentence (e.g., "Enrichment: E1 Clipped-Edge Demo Video, Tier-A CSS-art mockup." or "Enrichment: none — typography only."). The decision goes into the macrostructure stamp at Step 6.

The enrichment hierarchy is non-negotiable. Reach for the highest tier you can ship: typography only → Tier A pure CSS art → Tier B hand-built SVG → Tier C generated still (Nanobanana / Recraft) → Tier D library + customisation → Tier E Lottie is last resort, only for complex character motion that hand-build can't reach. Reaching for Lottie when CSS would have built it is the new tell.

When an enrichment archetype requires construction, also load custom-craft.md. When it requires an external asset, load assets.md.

5. Preview

Before emitting any code, output a tight summary of what you're about to ship. This is the user's TL;DR — they should be able to scan it in five seconds and tell you to redirect before you write 500 lines of CSS that don't match their intent.

Format (Markdown bullets, not ASCII boxes — they render reliably across every chat client and terminal):

**Hallmark · v1.0.0**

- **Macrostructure** · Stat-Led
- **Theme** · Plain (#fff paper · cool greys · ink-blue accent)
- **Enrichment** · none (typography only)
- **Sections** · Hero · Logos · Stats · Features · Testimonials · Pricing · FAQ · CTA · Footer
- **Motion** · counter · pricing-lift · pulse-once
- **Slop test** · 69 / 69 ✓ (run after Build)
- **Diversification** · differs from Linen on display style + accent hue

Six required bullets, one optional, plus a CTA line:

1. Macrostructure — the named pick from macrostructures.md.
2. Theme — for catalog: name + one-line palette summary (paper colour band · accent hue · display style). For custom: custom (vibe: "<4–8 words>" · paper oklch(<L%> <C> <H>) · accent oklch(<L%> <C> <H>) <one-word hue label> · <display face> + <body face>).
3. Enrichment — the chosen archetype + tier, or none (typography only).
4. Sections — section names separated by ·, in DOM order.
5. Motion — microinteraction primitives separated by ·, or none — typography only. Always under three primitives per the microinteractions.md hard rules.
6. Slop test — 69 / 69 ✓ if all gates pass, or N / 69 — fails: <gate numbers> if any are open. Run the slop test BEFORE writing this row; the slop test is Step 7.
7. Diversification (optional, only when .hallmark/log.json has prior entries) — what axes differ vs the previous run.

Then one quiet CTA line, italicised, after the bullets:

System portable? Say lock the system to extract this build's tokens + voice into a design.md.

Skip the CTA line when (a) the build is component-scope, or (b) design.md already exists at the project root (the system is already locked). See design-md.md for the full opt-in flow.

Four worked sample preview blocks (Long Document, Bento Grid, Manifesto, Custom) live in references/preview-examples.md — load that file only if the bullet-list spec above isn't scaffolding enough on its own. Most builds don't need it.

If any slop-test gate fails when you reach Step 7, return to the relevant Build step, fix it, and re-emit the preview block with the corrected slop-test row. The preview is the durable summary; it's wrong to ship if it lies.

6. Build

Emit code that satisfies the tone and structural fingerprint. Match the complexity of the code to the ambition of the tone — a brutalist page needs raw, heavy CSS; an austere page needs restraint.

Always:

• Hero headline — match font-size to copy length. When you write the headline yourself (no user-supplied copy), aim for ≤ 7 words and ≤ 50 chars from the start. For longer headlines, apply the size-by-length brackets in typography.md § Hero headline sizing: 21–50 chars use --text-display; 51–90 chars cap at --text-display-s; > 90 chars rewrite shorter or cap at --text-4xl. Aggressive-display themes (Brutal, Riso, Manifesto) auto-step down one rung past 50 chars — their 6.5–9rem ceiling is for short statements only.
• Section tags / eyebrows — default OFF. Do NOT emit 01 · THE TOUR, 02 / FEATURES, Chapter Three, or any uppercase mono-cap section number / kicker / label unless either (a) the user explicitly asked for chapter / step / section numbering, OR (b) the macrostructure is Long Document, Manifesto, or Catalogue numbered AND the content is genuinely ordinal. Cap at 1–2 per page even then. When a tag IS used, always stack vertical — tag above, heading directly underneath in the same column. The tag-left / heading-right two-column pattern (a.k.a. hanging header, left-margin label) is banned outright — it is the single most reliable templated-editorial tell, and slop-test gate 66 auto-fails it.
• Use OKLCH for every colour. Declare tokens as CSS custom properties at :root.
• Use a 4pt spacing scale with semantic names (--space-sm, --space-md, …).
• Pick a distinctive display face and a refined body face. Pairings, not single-font pages — unless the single-font choice IS the design (a true terminal-aesthetic page is monospace-only on purpose; that's allowed).
• Design every interactive element for its full eight states (see interaction-and-states.md).
• Animate transform and opacity only — never layout properties.
• Use the three named easings (--ease-out, --ease-in, --ease-in-out) — never the browser default ease, never bounce/overshoot on UI state.
• Support prefers-reduced-motion: reduce. Spatial motion collapses to ≤150ms opacity crossfade.
• Include :focus-visible with a visible ring at ≥3:1 contrast. Never animate the ring's appearance — it must show instantly on focus.
• For each interaction in the output (button, input, modal, toast, drag, copy, etc.), apply the recipe in microinteractions.md. Pick silent success over celebratory toasts. Pick optimistic update + Undo over confirmation dialogs. Pick delay 800ms on hover tooltips and 0ms on focus tooltips.
• Cut motion before adding it. Most pages have too much, not too little. If removing an animation wouldn't lose the user information, remove it.
• Stamp the output. The first non-empty line of the produced CSS file (or the top of <style> if inline) MUST be a comment of the form: /* Hallmark · macrostructure: <name> · tone: <tone> · anchor hue: <hue> */. This stamp is the durable record of what you chose. The next time Hallmark runs in this project, it reads the stamp and picks a different macrostructure. For custom themes, the stamp also carries the vibe, paper + accent OKLCH values, the chosen display + body fonts, and the three diversification axes — the full multi-line format is in custom-theme.md § E. For studied-DNA builds (Step 2.6 Condition 0 routed here from a study diagnosis), the stamp's theme: field is studied-DNA (source: <URL or "image">) followed by the paper OKLCH, accent OKLCH, and display + body fonts pulled directly from the diagnosis — not a catalog theme name. Diversification stays suspended for the run; the log entry below records theme: studied-DNA so Step 2.5 on the next run knows not to rotate against it.
• Append to project memory. After you write the stamp, update (or create) .hallmark/log.json at the project root. Append a new entry at the front of the array: { "date": "<YYYY-MM-DD>", "macrostructure": "<name>", "theme": "<name>", "enrichment": "<E# name or 'none'>", "brief": "<one-line summary>" }. Custom entries also carry "theme": "custom" plus "theme_axes": "<paper-band> / <display-style> / <accent-hue>" and an optional "vibe": "<4–8 words>" — see custom-theme.md § F. Trim the file to the last 20 entries (rotate the oldest off). Create .hallmark/ and the file if they don't exist; respect any existing .gitignore (the user may or may not want this committed). This file is what Step 2.5 reads on the next run.
• Always emit tokens.css. After writing the page CSS, also write tokens.css at the project root containing every --color-*, --font-*, --space-*, --text-*, --ease-*, --dur-*, --rule-*, and --radius-* token used in the build. The page CSS imports tokens.css (or, on framework projects, the project's existing entry-point includes it) — the page CSS must reference tokens by name, never inline raw values. Even single-page builds get a tokens.css. This is what makes the design system portable to the next project. Load export-formats.md at this point only when the project warrants additional formats — see below.
• Multi-format exports on design.md projects. If a design.md exists at the project root (a system-managed project), append all four export formats — tokens.css, Tailwind v4 @theme, DTCG tokens.json, shadcn/ui CSS variables — into design.md's ## Exports section. Load export-formats.md for the canonical mapping from Hallmark tokens to each format. Single-page projects skip this step (they get only tokens.css).
• Opt-in design.md (lock-the-system flow). If the user explicitly asks Hallmark to lock the build's design system into a portable file (phrases: "lock the system", "give me a design.md", "make this portable", etc.), load design-md.md and follow it. Page-scope only; component-scope skips. The default verb does NOT auto-emit design.md — users iterate freely first, then ask for it once the system is settled. If design.md already exists, refresh its ## Exports section instead of overwriting. The Step 5 preview block carries a one-line CTA surfacing this option after every page-build.

7. The slop test

Before handing back, run the output through the 69-gate slop test in references/slop-test.md. Every answer must be no. Load that file at this step (not earlier — it isn't needed until handoff). The active genre matters: some gates are universal, some are genre-scoped (atmospheric loosens the radial-bloom gate; modern-minimal loosens the zero-chroma neutral gate; etc.). The full per-genre overrides are listed inline in slop-test.md.

Run the slop test BEFORE writing the Slop test row in the Step 5 preview block — that row reflects the actual outcome of this step.

If any gate fails, fix it. Do not ship slop.

---

hallmark audit

Load references/verbs/audit.md and follow it.

---

hallmark redesign

Load references/verbs/redesign.md and follow it.

---

hallmark study

The user has supplied a reference — either an attached screenshot or a URL to a live page — of a design they admire. They want to learn from it — its shape, its type, its rhythm — and apply that DNA to their own content. They do not want a pixel-faithful copy.

Critical position: study extracts structure, not pixels. It names the macrostructure, the archetypes, the type-pairing, the colour anchor, and (in image mode) the rhythm. It produces a diagnosis report before any code, then offers to rebuild the user's content using the extracted DNA. Pixel-cloning is not a feature.

Always read references/study.md before invoking this verb. That file contains the source-mode detection rules, the extraction protocol (vision-pass for image mode, HTML/CSS-pass for URL mode), the structured-fields schema, the refusal heuristics (both image-mode and URL-mode refuse lists), the junk-or-blocked detection for URLs, and the type-role vocabulary. Do not work from intuition.

Source-mode detection

If the user's input starts with http:// or https:// → URL mode. Otherwise → image mode. Same verb, same diagnosis output, different signal sources. The two modes share the schema and the diagnosis shape; they differ on what each extraction step can know — see study.md § Source mode.

Pipeline

1. Refuse-or-proceed check. Before extracting anything (and in URL mode, before WebFetch fires), run the refusal heuristics in study.md. Image mode checks the image's content; URL mode runs the URL refuse list (themeforest, framer.com/templates, webflow.com/templates, gumroad UI-kit listings, dribbble shots, behance galleries, disclosed competitors). Ambiguous sources get one short question: "Is this your own work, a public reference for inspiration, or someone else's live site?"

2. Extraction pass.

   • Image mode: vision-pass on the attached capture per study.md § Five-step protocol.
   • URL mode: WebFetch the URL, then parse the returned HTML and any linked stylesheets. If the response trips any junk-or-blocked signal (auth wall, SPA shell, non-2xx response, no styling signal, < 1 KB body), fall back — emit the screenshot-fallback message from study.md § Junk-or-blocked detection and stop. Do not silently degrade.

   Output the structured-fields schema in study.md § The structured fields. URL mode fills the mode-conditional fields (display_face, body_face, paper_value, accent_value, motion_library) with exact values; image mode leaves those null.

3. Diagnosis report. Return a one-page "this is what you're looking at" using the matching template (image-mode template or URL-mode template) from study.md § The diagnosis report. Names the macrostructure, names the archetypes, points at the type pairing (with exact font names in URL mode), identifies anti-patterns the user should not carry over. URL-mode diagnoses must also call out the rhythm blind spot.

4. Confirmation question. Ask: "Adopt this DNA wholesale, or change one axis? For example, I could keep the macrostructure but pick a theme that better matches your tone." The diagnosis report's last line also surfaces the design.md emission CTA — "Or — say lock the DNA if you want a portable design.md of this DNA." Wait for the user's answer before doing anything.

5. Branch on the user's response:

   • "Build with this DNA" → run the build step below. Pick the closest matching theme from the catalog. Stamp the comment with the inferred macrostructure + archetypes + theme + source mode. The user's content goes in; the source's content does not.
   • "Lock the DNA" (or any other emission trigger phrase per study.md § Trigger phrases) → emit a portable design.md of the DNA per study.md § Emitting a design.md from study. In URL mode, run the attestation step first — ask whether the source is (a) user's own, (b) public reference for the user's brand, or (c) something else. (c) refuses emission; (a) and (b) write the file with a ## Provenance block recording the answer. Image mode emits without asking — the user owns the screenshot. The emitted file becomes the project's locked system; subsequent runs defer to it.
   • "Just the diagnosis was enough" / silence → stop. The diagnosis is a complete deliverable.

Output contract for study

When study produces code, the macrostructure stamp must include a studied: yes flag, the theme picked, and the source mode. Image mode example:

/* Hallmark · macrostructure: Marquee Hero · H1 hero knobs: size=xxl, alignment=left-bias
 * theme: Studio · accent: forest-green ~3% · studied: yes · DNA-source: image (user reference)
 */

URL mode example — additionally records the URL and any exact-fonts / exact-colours that informed the build:

/* Hallmark · macrostructure: Marquee Hero · H1 hero knobs: size=xxl, alignment=left-bias
 * theme: Studio · accent: forest-green ~3% · studied: yes · DNA-source: url
 * source-url: https://example.com/  ·  observed-fonts: Inter Tight + Inter
 * observed-accent: oklch(58% 0.16 35)  ·  rhythm: unknown (URL mode)
 */

The stamp signals to future Hallmark runs that this page's structure was extracted, not invented. That matters for the audit verb: a studied: yes page is audited more leniently for "Specimen fall-through" (the user explicitly chose this DNA) but more strictly for "did you actually use the extracted DNA, or did you drift back to defaults?"

Limits to spell out to the user

When you return the diagnosis, name the limits explicitly:

• Fonts: in image mode, the skill names a role and proposes one or two real candidates from the canon — visual font ID is unreliable. In URL mode, the skill names the exact fonts the page loads (via @font-face, Google Fonts, next/font). The role still drives the rebuild — Hallmark may pick a different specific face for the user's content.
• Imagery: the skill never copies the source's photography. It generates structurally-equivalent placeholders or asks for the user's own assets.
• Theme drift is allowed. If the source is a Specimen and the user's content is a SaaS landing page, the skill picks a different theme. The DNA is the macrostructure + archetype + colour-anchor + type-pairing — not the dress.
• Rhythm is the URL-mode blind spot. HTML alone can't tell you whether the visual rhythm reads generous or templated. URL-mode diagnoses always state this and offer a screenshot fallback if it matters.

If references/study.md cannot be loaded for any reason, refuse the verb politely and direct the user to hallmark redesign with a written description of what they want from the source.

---

Output contract & scope

Load references/contract.md once, at handoff time, for the full output contract and scope-of-skill rules.