redesign
starsforks
How to install redesign?
educlopez/ui-craft/redesign
$npx -y skills add educlopez/ui-craft --skill redesignRedesign 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 sit
SKILL.md
| 1 | <!-- HARNESS MIRROR — do not edit here. Canonical source: commands/redesign.md. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. --> |
| 2 | |
| 3 | **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. |
| 4 | |
| 5 | Redesign `the target the user described`. 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. |
| 6 | |
| 7 | **Step 1 — Audit what exists (before any opinion):** |
| 8 | |
| 9 | - Run the detector on the current source (`npx ui-craft-detect <path>`) or live page (`npx ui-craft-detect <url>`) and note findings. |
| 10 | - 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. |
| 11 | - Read `.ui-craft/brief.md` if present — prior constraints still bind. |
| 12 | |
| 13 | **Step 2 — Classify what to preserve. Wrong-to-change unless the user explicitly asks:** |
| 14 | |
| 15 | - **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. |
| 16 | - **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. |
| 17 | - **Content + voice** — existing copy is data about the business. Restructure freely; rewrite voice only with permission. |
| 18 | - **Conversion paths** — every CTA and form that exists today exists for a reason. Relocate, restyle, but never silently drop one. |
| 19 | |
| 20 | **Step 3 — Pick the scope and say it out loud:** |
| 21 | |
| 22 | | Scope | What changes | When | |
| 23 | |---|---|---| |
| 24 | | **Refresh** | Tokens only: type scale, spacing rhythm, radii, shadows, color tuning | Site is structurally fine, looks dated | |
| 25 | | **Reskin** | Visual layer + component styling; layout skeleton and section order stay | Bones are good, skin is generic or old | |
| 26 | | **Rebuild** | Layout and composition too; content, IA, and brand carry over | Layout itself is the problem | |
| 27 | |
| 28 | Default to the smallest scope that fixes the stated complaint. For **rebuild**, print a short before/after section map and get a nod before writing code. |
| 29 | |
| 30 | **Step 4 — Declare the Craft Read** (surface kind, audience, theme, `DESIGN_VARIANCE`, signature bet) per `references/craft-intent.md`. Redesigns default to variance 4–5: the brand is already committed, so spend boldness on typography and composition, not on a new identity. |
| 31 | |
| 32 | **Step 5 — Modernize with levers, in this order:** typography (scale + pairing per `references/typography.md`) → spacing rhythm → color tokens (`references/color.md`) → imagery treatment → motion (entrance/hover only where focal). Fix every detector finding from Step 1 along the way. |
| 33 | |
| 34 | **Never:** invent a new brand palette over a committed one, drop routes or pages, flatten heading semantics for looks, rewrite copy voice unasked, or ship the redesign with more detector findings than the original had. |
| 35 | |
| 36 | **Output:** edit code directly (refresh/reskin) or section map first (rebuild). Print the Review Format table, the detector before/after counts, and end with the Craft Read line. |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
