wip

SKILL.md

@@ -24,11 +24,17 @@ Hallmark has one default behaviour and three explicit verbs.
 | --- | --- |
 | *(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 redesign <target> [--mood <name>]` | Take the target's content and intent, then redesign the visual structure **inside the existing implementation boundaries unless the user explicitly confirms a full rebuild.** New section rhythm, new heading placement, new component voice. Preserve existing routes, component ownership, copy intent, brand, and information architecture; replace only the visual/interaction layer needed for the requested scope. |
 | `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`](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?"*
 
+**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.
+
 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`](references/custom-theme.md).
 
 ---
@@ -542,4 +548,4 @@ If `references/study.md` cannot be loaded for any reason, refuse the verb polite
 
 ## Output contract & scope
 
-Load [`references/contract.md`](references/contract.md) once, at handoff time, for the full output contract and scope-of-skill rules.
+Load [`references/contract.md`](references/contract.md) once, at handoff time, for the full output contract and scope-of-skill rules.

references/verbs/redesign.md

@@ -1,6 +1,16 @@
 # `hallmark redesign`
 
-The user wants a different page from the same content. They are not happy with the current structure — typically because it reads as templated, generic, or AI-shaped. Your job is to throw the structure out and build a new one.
+The user wants a different page from the same content. They are not happy with the current visual structure — typically because it reads as templated, generic, or AI-shaped. Your job is to redesign the page's structure, rhythm, and component voice while respecting the existing implementation boundaries unless the user explicitly confirms a full rebuild.
+
+## Non-destructive implementation rule
+
+Hallmark redesigns visual and interaction layers. It does not delete production files by default.
+
+- Never delete existing route files, component directories, page trees, or the 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 page/component files, or additive new components/tokens wired through the existing route.
+- If the redesign would require removing multiple components, replacing a route tree, or collapsing the app into a single new page, stop and ask for confirmation first.
+- Treat PDFs, README files, `.md` briefs, docs, transcripts, and pitch decks as source material for understanding the product. They are not page copy by default. Summarize and adapt them unless the user explicitly says to use their wording verbatim.
+- Before editing, state the files you expect to modify, create, and delete. Any deletion needs explicit confirmation.
 
 ## Step 0 · Detect scope first
 
@@ -224,10 +234,11 @@ If a page genuinely needs something `design.md` doesn't allow (e.g. a marketing
 (The classic redesign behaviour — unchanged.)
 
 **What to preserve:**
-- The copy (every word, ideally)
+- The copy intent, factual claims, product names, and primary message. Preserve exact wording only when it already lives in the target UI or the user explicitly asks for verbatim copy.
 - The information architecture (which sections exist, in roughly what order)
 - The brand (colours and fonts they've named, if any)
 - The primary action
+- The existing route/component ownership boundaries, unless the user has approved a full rebuild
 
 **What to replace:**
 - The structural fingerprint — pick a **different** combination from [`structure.md`](../structure.md) than the source had.
@@ -235,6 +246,11 @@ If a page genuinely needs something `design.md` doesn't allow (e.g. a marketing
 - The reveal pattern — if the original faded everything in on scroll, the new one might have no reveals at all.
 - The visual rhythm — different sections having different padding, different alignments, deliberate breaks.
 
+**What not to replace without confirmation:**
+- Route trees, production component directories, or the old website's file structure.
+- Working app logic, data fetching, auth, forms, analytics, or integration code.
+- Existing copy with pasted text from PDFs, docs, or markdown files unless the user requested verbatim copy.
+
 **Optional `--mood <name>` argument:**
 
 If the user specifies a mood (`hallmark redesign ./hero.tsx --mood luxury`), pick a tone aligned to that mood and let it drive the structural fingerprint. Mood names map to tones from [`typography.md`](../typography.md) and [`structure.md`](../structure.md). If no mood is given, ask the user what *feeling* they want — one word — and proceed.