Hallmark

Install

npx skills add nutlope/hallmark

This is third-party code. Review the repository files before installing.

What it does

The skill gives the agent strict visual design rules and forces it to vary page structure, not just colors. By default it picks a macrostructure and one of the built-in themes, and on an explicit creative request it builds a custom palette and font pairing. The audit verb scores existing code against anti-patterns without editing, redesign rebuilds the visual layer while keeping copy and structure, and study extracts structure, fonts and colors from a design you like. Before output the agent runs slop and mobile layout checks and does not invent metrics or testimonials.

Who it is for. For developers and designers building landing pages and interfaces with an agent.

Example request

hallmark audit src/app/page.tsx: score the home page and rank the fixes

Limitations

The skill is rules and references and does not generate images. Study in URL mode reads HTML and CSS and fails on auth-walled pages and empty SPA shells, falling back to a screenshot. In Cursor only the SKILL.md body is used, without the references.

How to disable. Delete the hallmark folder from the agent's skills directory or the .cursor/rules/hallmark.mdc file.

Security check

• The skill is rules and references, and file deletion requires confirmation

README in short

The README explains four modes: default build, audit, redesign and study. A gallery shows pages for different briefs built in different themes and structures, plus a Custom mode for briefs with clear creative intent. Install via npx skills or by copying SKILL.md and references into Claude Code, Cursor or Codex folders. Made by Together AI, MIT licensed.

SKILL.md

---
name: hallmark
description: "Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study."
version: 1.1.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 (Anthropic's frontend-design 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`](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.** |

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?"*

**Implementation safety rail.** Hallmark is a design skill, not a license to bulldoze a codebase. In any existing project:
- Never delete production files, route trees, component directories, or an old website unless the user explicitly asks for deletion or approves a file-level plan that lists the deletions.
- Default to in-place edits of the named files, or additive new components/tokens that are wired through the existing route. If the redesign would require removing multiple components, stop and ask for confirmation first.
- Treat PDFs, README files, `.md` briefs, docs, transcripts, and pitch decks as reference material. Do **not** copy them word-for-word into the page unless the user explicitly says to use that text verbatim.
- Before editing, state the exact files you expect to modify/create/delete. Deletions require explicit confirmation.

Related