Skip to content

Anti-AI-slop design skill for Claude Code, Cursor, and Codex.

CSS

Hallmark never starts on an existing design unless named: a restyle, new colours or a redesign asked of the agent alone is done the ordinary way, and /hallmark redesign is a full redesign by default

Youssef5c79e1642388
diff --git a/README.md b/README.md
index c96669d..ab93b3f 100644
--- a/README.md
+++ b/README.md
@@ -92,9 +92,9 @@ node skills/hallmark/scripts/install.mjs
| Harness | Install location | Invoke |
| --- | --- | --- |
-| Claude Code | `~/.claude/skills/hallmark` | `/hallmark <brief>`, `/hallmark redesign <path>`, or just describe the build |
-| Codex CLI | `~/.agents/skills/hallmark` | `$hallmark <brief>`, `$hallmark redesign <path>`, or implicit |
-| OpenCode | auto-discovers the copies above | `/hallmark <brief>`, `/hallmark redesign <path>`, or implicit |
+| Claude Code | `~/.claude/skills/hallmark` | `/hallmark <brief>`, `/hallmark redesign <path>`, or describe a new build |
+| Codex CLI | `~/.agents/skills/hallmark` | `$hallmark <brief>`, `$hallmark redesign <path>`, or describe a new build |
+| OpenCode | auto-discovers the copies above | `/hallmark <brief>`, `/hallmark redesign <path>`, or describe a new build |
On Claude Code, `node skills/hallmark/scripts/install-hook.mjs` wires the Floor gates into a PostToolUse hook so a failing artifact is reported the moment it is written; the taste gates wait for the end-of-build sweep, so the hook never nags. `--global`, `--print` and `--remove` do what they say.
@@ -102,20 +102,20 @@ On Claude Code, `node skills/hallmark/scripts/install-hook.mjs` wires the Floor
## Redesign
-Hallmark runs by itself when you ask for something new. For a page, a site or an app that already exists, say the verb:
+Hallmark runs by itself when you ask for something new. It never starts on a page, a site or an app that already exists: ask your agent for new colours, a restyle or a redesign without naming Hallmark and it does the job the ordinary way. For a full redesign by Hallmark, say the verb:
```
/hallmark redesign ./src/app
/hallmark audit ./index.html
```
-A redesign keeps what the page says and does and changes how it looks, at the depth you ask for:
+A redesign keeps what the page says and does and changes how it looks and how it is laid out. Two lighter depths run only when you ask for them in the same request:
-| Depth | Stays | Changes |
-| --- | --- | --- |
-| **polish** | the system and the layout | only what reads as generated: the tells, contrast, states, motion |
-| **restyle** | the layout | colour, type, radius, shadow, motion, the controls |
-| **full** | the content and the wiring | the system and the composition |
+| Depth | Stays | Changes | Say |
+| --- | --- | --- | --- |
+| **full** | the content and the wiring | the system and the composition | the verb alone |
+| **restyle** | the layout | colour, type, radius, shadow, motion, the controls | *keep the layout* |
+| **polish** | the system and the layout | only what reads as generated: the tells, contrast, states, motion | *polish* |
Before it touches anything, `sloplint --before` lints the page and records every link, form field, handler, test hook, heading and figure. After the build, `sloplint --kept` fails the redesign if any of them went missing, a fresh-context reviewer compares the new screens with the old ones, and the project's own build and tests have to pass. The handoff is a before and after: findings, what was kept, what changed, anything dropped with the reason on the record, and `.hallmark/compare.html`, the old and new screens side by side. `audit` stops after the report and edits nothing.
diff --git a/skills/hallmark/SKILL.md b/skills/hallmark/SKILL.md
index 1c041e4..0d4b8e9 100644
--- a/skills/hallmark/SKILL.md
+++ b/skills/hallmark/SKILL.md
@@ -1,6 +1,6 @@
---
name: hallmark
-description: "Design skill for pages, sites, app screens and components that look made, not generated. Builds new UI from a dealt theme or a derived world on a hard floor, then lints and reviews it; `redesign <path>` does the same to an existing page, site or app and keeps its content and wiring. Use when the user asks to build or design new UI, asks to redesign or restyle a whole page, site or app, says one looks generic or AI-generated, or invokes Hallmark by name. Not for small edits to an existing design."
+description: "Design skill for new pages, sites, app screens and components that look made, not generated: deals a theme or derives a world, builds on a hard floor, lints and reviews. Use when the user asks to build or design something new, or names Hallmark. Never use it to change an existing design (a restyle, new colours or theme, a polish, a redesign, a small edit) unless the user names Hallmark: `/hallmark redesign <path>` is the explicit full redesign, keeping content and wiring; `/hallmark audit <path>` only reports."
argument-hint: "<brief> | redesign <path> | audit <path>"
version: 2.7.0
---
@@ -45,7 +45,7 @@ Above the Floor, a **Reflex** gate is a default a model falls into, which a buil
6. Build: the hero first, then the page; stamp, `tokens.css`, log.
7. Sweep: `sloplint --render` until clean, the judged gates, the finish review, the material ask.
-**Verbs.** `redesign <target>`, `audit <target>`, or a plain ask to redesign, restyle or polish an existing page, site or app: read [`references/redesign.md`](references/redesign.md) first; it sets what the run keeps and adds a before and an after. A small edit to an existing design is not a Hallmark run.
+**Verbs,** only when the user names Hallmark: `redesign <target>` (a full redesign keeping content and wiring) and `audit <target>` (a report); read [`references/redesign.md`](references/redesign.md) first. Any other change to an existing design is not a Hallmark run: do it as asked, in the project's own system, with no deal, scaffold, stamp or sweep.
Codex CLI and OpenCode read [`references/flow.md`](references/flow.md) § Harnesses first; other harnesses run this file as written.
@@ -77,7 +77,7 @@ Decide the page's shape, how it opens, which composition each section takes, wha
**Signature.** Every page has one thing a visitor would remember, and it is the brief's strongest real thing shown at its best: the photograph that is the place, the product doing its one job, a price or a date set huge because it is the offer, a control that lets the visitor try it. Decide it here, make it in the dealt theme's material, show it on the first screen, and put it in the Picks block and the stamp; the reviewer checks it. A number drawn as marks (one dot a bottle, a dial of the year) is a device, not a signature (82).
-Decide all of this and hold it; it is said once, at Step 5.
+Hold all of it; it is said once, at Step 5.
### 3. Direction
diff --git a/skills/hallmark/references/redesign.md b/skills/hallmark/references/redesign.md
index 49fab27..4f4aa14 100644
--- a/skills/hallmark/references/redesign.md
+++ b/skills/hallmark/references/redesign.md
@@ -1,6 +1,6 @@
# Redesign
-Loaded when the request opens with `redesign` or `audit`, or asks to redesign, restyle or polish an existing page, site or app. A redesign is a build whose material is the page that exists: SKILL.md still binds, and this file says what the run keeps, what replaces the Step 1 ask and what the sweep adds. The target is the user's own code (a file, a folder, a route on a dev server); a live URL with no source behind it can only be audited, through `--url`. A small edit (a tweak, one fix, new copy) is neither a redesign nor a Hallmark run.
+Loaded only when the user names Hallmark with `redesign` or `audit` (`/hallmark redesign <target>`, *redesign the site with Hallmark*). A request that changes an existing design without naming Hallmark (a restyle, new colours or a new theme, a polish, a redesign, a small edit) never loads this file: it is done as asked, in the project's own system. A redesign is a build whose material is the page that exists: SKILL.md still binds, and this file says what the run keeps, what replaces the Step 1 ask and what the sweep adds. The target is the user's own code (a file, a folder, a route on a dev server); a live URL with no source behind it can only be audited, through `--url`.
## What a redesign keeps
@@ -12,13 +12,15 @@ Loaded when the request opens with `redesign` or `audit`, or asks to redesign, r
## Depth
-How far the run goes. The user's words pick it, on an app as on a page; where they name no depth the project does, and the Picks block says which. Where the words fit two depths, take the lighter: a redesign that kept too much is one message from going further, and one that replaced too much has to be undone. The depths do not blend: a polish that finds the concept wrong says so and recommends the deeper run, it never smuggles one in.
+The verb is a **full** redesign: the content and the wiring stay, the system and the composition change. A lighter depth runs only when the same request asks for it in so many words, and the Picks block names the depth:
-| Depth | Stays | Changes | Picked by |
+| Depth | Stays | Changes | Only when the request says |
| --- | --- | --- | --- |
-| **polish** | the system and the layout | only what a gate names: the tells, contrast, states, motion, tokens | *polish*, *clean up*, *fix the design*; *keep our look*; a `design.md` |
-| **restyle** | the layout | the system: colour, type, radius, shadow, motion, the controls | *restyle*, *reskin*, *a new look*; the bare verb (*redesign* with no reason or depth beside it) on an app screen, or on a page with a brand |
-| **full** | the content and the wiring | the system and the composition: shape, hero, section objects, chrome | *redesign it fully*, *looks generic*, *looks generated*; the bare verb on a marketing page with no brand |
+| **full** | the content and the wiring | the system and the composition: shape, hero, section objects, chrome | nothing else: it is the verb |
+| **restyle** | the layout | the system: colour, type, radius, shadow, motion, the controls | *keep the layout*, *restyle*, *reskin*, *only the colours and type* |
+| **polish** | the system and the layout | only what a gate names: the tells, contrast, states, motion, tokens | *polish*, *keep our look*, *only fix what looks generated* |
+
+The depths do not blend: a polish that finds the concept wrong says so and recommends the full run, it never smuggles one in.
**Full depth on an app screen** recomposes each screen inside the shell it has: what leads, and how the figures, tables and forms are arranged (`flow.md` § App screens). Routes, destinations and each component's logic stay; there is no hero stage and no hero review.
@@ -43,14 +45,14 @@ It prints the findings grouped by gate and writes them to `.hallmark/before.txt`
One message replaces the Step 1 ask; skip it when the request already answers it or no one can answer:
-> *Before I redesign, three things. 1. **What stays**: the look (I fix only what reads as generated), the layout (new colour and type on the same structure), or only the content (a new design)? And anything I must not touch. 2. **What is wrong with it**, in your words, and the feeling you want instead. 3. **Anything new to show**: screenshots, photos, numbers, a quote. Or say **go ahead** and I will pick the depth from the project and say which.*
+> *Before I redesign, three things. 1. **What must stay**: the brand, a section, a page? Say *keep the layout* and I only restyle. 2. **What is wrong with it**, in your words, and the feeling you want instead. 3. **Anything new to show**: screenshots, photos, numbers, a quote. Or say **go ahead** and I will redesign it in full.*
## The plan
The Picks block opens with four rows of its own, and nothing is deleted until the user has seen the Files row:
```markdown
-- **Redesign** · restyle · 3 pages (/, /pricing, /docs)
+- **Redesign** · full · 3 pages (/, /pricing, /docs)
- **Before** · Floor 14 FAIL · Reflex 9 · a centred template in a stock indigo; the pricing table is clear and stays
- **Keeps** · every link, field and handler · the green and the brand face · the pricing table
- **Files** · edit: app/page.tsx, app/pricing/page.tsx, app/globals.css · create: app/tokens.css, app/base.css · delete: none
@@ -72,17 +74,15 @@ Then the build rows the depth reaches: Theme at restyle and full (dealt, `brand`
2. The project's own checks, where it has them: the type check, the build, the tests. A redesign that breaks one is not finished.
3. The finish review also takes the `before` screenshots and answers what the old page did better (`review-finish.md`). A polish hands it only the full pages at 1440, before and after, and takes at most five findings. A finding that is a plain defect (a misalignment, a broken glyph, a label that lies) is fixed at any depth; one that asks for a new composition joins the layout findings; one that asks for content the page never had goes to the owner in the handoff.
4. The log entry carries `mode: redesign`, `depth` and `scope` (page, site or app), plus the build's fields at full depth.
-5. The handoff, ahead of the material ask; the Layout and Next rows exist only where the layout stayed:
+5. The handoff, ahead of the material ask; where the layout stayed it adds a Layout row (the findings only a full redesign would settle):
```
-Redesign · restyle · 3 pages
+Redesign · full · 3 pages
Before Floor 14 FAIL · Reflex 9
After Floor 0 · Reflex 1 waived (47b)
-Kept 14/14 links · 5/5 fields · 9/9 handlers · 11/11 headings · every figure · the layout
-Changed the system: colour, type, radius, motion, the controls
+Kept 14/14 links · 5/5 fields · 9/9 handlers · 11/11 headings · every figure
+Changed the system and the composition: shape, hero, sections, chrome
Dropped none
-Layout 2 findings a full redesign would settle (8, 42), listed below
-Next say *redesign it fully* to recompose the pages
Yours 2 claims kept as found ("50,000+ teams", the Acme quote) · 4 lines reworded, listed below
Compare .hallmark/compare.html
```