Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Redesign $ARGUMENTS. Load the ui-craft skill and read references/craft-intent.md. A redesign is not a greenfield build wearing the old content — most of its value is in what you deliberately keep.

Step 1 — Audit what exists (before any opinion):

Run the detector on the current source (npx ui-craft-detect <path>) or live page (npx ui-craft-detect <url>) and note findings.
Inventory: pages/routes, section order, heading hierarchy (h1–h3), nav structure, conversion paths (CTAs and where they lead), forms, imagery assets, fonts, color values actually in use.
Read .ui-craft/brief.md if present — prior constraints still bind.

Step 2 — Classify what to preserve. Wrong-to-change unless the user explicitly asks:

Brand equity — logo, name, an established palette the business already uses in the wild. Committed brand color stays; you may re-tune tints/shades into a proper token scale.
IA + SEO — URLs/routes, page set, heading semantics, title/meta, alt text, structured data. A redesign that tanks organic traffic is a failure regardless of how it looks.
Content + voice — existing copy is data about the business. Restructure freely; rewrite voice only with permission.
Conversion paths — every CTA and form that exists today exists for a reason. Relocate, restyle, but never silently drop one.