Command
/redesign
Redesign an existing site or app without losing what already works — audits the current surface first, classifies what to preserve (brand, IA, SEO, content), picks a refresh/reskin/rebuild scope, then modernizes deliberately. Use when the user says "redesign", "modernize this
One command from ui-craft.
shell
$ npx -y skills add educlopez/ui-craft --agent claude-codeShips with ui-craft. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/redesign
Context preview
What this command does when you run it.
Redesign an existing site or app without losing what already works — audits the current surface first, classifies what to preserve (brand, IA, SEO, content), picks a refresh/reskin/rebuild scope, then modernizes deliberately. Use when the user says "redesign", "modernize this
Stats
Stars209
Forks9
LanguageGo
LicenseMIT
Ships with ui-craft
Command definition
redesign.md
--- description: Redesign an existing site or app without losing what already works — audits the current surface first, classifies what to preserve (brand, IA, SEO, content), picks a refresh/reskin/rebuild scope, then modernizes deliberately. Use when the user says "redesign", "modernize this site", "refresh the UI", "make this look current", or points at an existing page/URL they want improved rather than rebuilt from scratch. argument-hint: "[path, URL, or page to redesign]" --- 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.
