Skip to content

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

CSS

The redesign file says the same in fewer words

Youssefd775747ce000
diff --git a/skills/hallmark/references/redesign.md b/skills/hallmark/references/redesign.md
index 9ee7612..f545feb 100644
--- a/skills/hallmark/references/redesign.md
+++ b/skills/hallmark/references/redesign.md
@@ -1,12 +1,12 @@
# Redesign
-Loaded when the request opens with `redesign` or `audit`, or plainly asks to redesign, restyle or polish an existing page, site or app, or to make one look less generated. 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, or a route on a dev server. A live URL with no source behind it can be audited through `--url` and nothing more. A small edit to an existing design (a tweak, one fix, new copy) is neither a redesign nor a Hallmark run.
+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.
## What a redesign keeps
-- **The content.** Every fact, claim, name, price, date and quote the page states. Figures, quotes and logos already on the page are the user's material: carried over as found, never added to, and listed in the handoff for the user to verify; one a gate doubts (a trend nobody measured, 46a) stays and is named there. Nothing is added either: no action, section or visual the page did not have, beyond what the user hands over.
+- **The content.** Every fact, claim, name, price, date and quote the page states. Figures, quotes and logos already there are the user's material: carried over as found and listed in the handoff to verify, one a gate doubts (a trend nobody measured, 46a) included. Nothing is added: no action, section or visual the page did not have, beyond what the user hands over.
- **The wiring.** Every link, form, field, handler, route, id and test hook; every script, data call and analytics call. Edit markup inside the component that owns it. Never move logic, rename a prop, or drop a `name`, an `id`, a `key`, a `type`, an `href` or a `data-testid` that a script or a test reads. A prop the Floor empties (an emoji passed as an icon) may go with it, named in the handoff. A state the screen has no logic for (a failed load, an undo) is listed for the owner, never built.
-- **The files.** No file deleted, no route removed and no component tree replaced without a file-level plan the user approved, and no test edited to make the redesign pass. Documents in the repo (a README, a brief, a deck) explain the product; they are not page copy. In a git project, start from a clean tree, `.hallmark/` aside (ask the user to commit or stash; never do it for them), so the redesign is one diff they can read and revert. The stylesheet itself is the redesign's to edit: the append-only rule guards it from a build, not from its own redesign.
+- **The files.** No file deleted, no route removed and no component tree replaced without a file-level plan the user approved, and no test edited to make the redesign pass. Documents in the repo (a README, a brief, a deck) explain the product; they are not page copy. In a git project, start from a clean tree, `.hallmark/` aside (ask the user to commit or stash; never do it for them), so the redesign is one diff they can read and revert. The stylesheet is the redesign's to edit: the append-only rule guards it from a build, not from its own redesign.
- **The brand,** when there is one. A brand is chosen: a logo, a colour or a face the project names (a brand file, a logo asset, named tokens, a font file of its own) or the user states. It stays at every depth, its values read from the project's files, never from memory. A framework default or a look the gates name (the purple-to-blue gradient, Inter as the display, a stock swatch) is not a brand: restyle and full replace it, and the Picks block says so in case it was. A locked `design.md` is the system at every depth.
- **The words,** unless a gate names them. Wording that fails a copy gate (19, 54, 58, 63, 69) is tightened from the facts already on the page, and the handoff lists every changed line, before and after. An eyebrow is never just deleted: where its heading is figurative, the plain label becomes the heading (*Opening hours* over *When to find us* becomes *Opening hours*). Terms, disclaimers and consent text are never reworded. When the user says to keep every word, stamp `copy: verbatim`: 19, 58 and 69 then report as notes.
@@ -33,7 +33,7 @@ How far the run goes. The user's words pick it, on an app as on a page; where th
node <skill-dir>/scripts/sloplint.mjs <target> --genre <genre> --render --before [--url <route> ...] [--scope app]
```
-It prints the findings grouped by gate and writes every line to `.hallmark/before.txt`, the screenshots to `.hallmark/before/`, and the record to `.hallmark/before.json`: every link, form, field, inline handler, test hook, script tag, selector a script queries, heading and figure. The folder ignores its own screenshots and records in git.
+It prints the findings grouped by gate and writes them to `.hallmark/before.txt`, the screenshots to `.hallmark/before/` and the record to `.hallmark/before.json`: every link, form, field, inline handler, test hook, script tag, selector a script queries, heading and figure. Git ignores the folder's screenshots and records.
3. Look at the screenshots before you weigh the findings, so the linter does not write the verdict, then give the read in four lines: what the page is for (the audience, the one action); what works and stays (at least one thing); what reads as generated (the worst tells, by gate); what is broken.