redesign
Upgrade an existing website or app to premium quality without breaking functionality — audit the current design, identify generic/AI tells, then apply taste and system rules surgically. Use when the user wants to improve, modernize, polish, or "make better" an existing UI/codebas
Install
npx skills add https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/redesign
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install plugin87-ux-ui-agent-skills@llmmart
git clone https://github.com/plugin87/ux-ui-agent-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole plugin87/ux-ui-agent-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Skill: Redesign & Audit
Step 0: is the kit here? This skill reads files from the kit. Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSINGonly the skill folders were installed, which is whatnpx skills adddoes. Say so plainly, point the user atnpx ux-ui-agent-skills initor the plugin install, and stop. Do not guess the contents of a file you could not open.
Audit-first redesign that preserves behavior.
Steps
- Read
${CLAUDE_SKILL_DIR}/../../../workflows/redesign-audit.md(the full Scan → Diagnose → Direct → Apply → Verify sequence + Output Completeness). - Scan the codebase: framework, styling method (→ route to the matching
${CLAUDE_SKILL_DIR}/../../../frameworks/adapter), token reality, components, what must be preserved. - Diagnose with the Banned Defaults checklist (
${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md) + the review rubric (design-reviewskill). Produce a prioritized findings table. - Direct: choose an archetype/system (
apply-aestheticskill) that fits the brand. - Apply in order (tokens first, then typography/spacing, then component states, then motion) without changing routes/data/markup semantics (except a11y fixes).
- Verify: re-run
design-review+a11y-audit; smoke-test every previously working flow; dark mode + responsive spot-check. Run${CLAUDE_SKILL_DIR}/../../../scripts/validate_contrast.pyon the token source and${CLAUDE_SKILL_DIR}/../../../scripts/lint_hardcodes.pyover the changed code.
Guardrails
Never sacrifice a working feature for aesthetics. Never ship a brand color that fails contrast. Never remove existing accessibility affordances. Deliver complete files, no placeholders.
Single-theme consistency (critical for multi-page apps)
Consolidate to ONE shared token theme and make every page consume it. A redesign that leaves different pages on different palettes has failed. Replace per-page/ad-hoc colors with semantic tokens; verify with ${CLAUDE_SKILL_DIR}/../../../scripts/lint_hardcodes.py that no page reintroduces off-theme values. Theme switches must come from the single token source, not page edits (${CLAUDE_SKILL_DIR}/../../../.claude/rules/tokens-and-color.md → Single-Theme Consistency).
Files (ux-ui-agent-skills)
-
SKILL.md 2.8 KB
--- name: redesign description: Upgrade an existing website or app to premium quality without breaking functionality. Audit the current design, identify generic/AI tells, then apply taste and system rules surgically. Use when the user wants to improve, modernize, polish, or "make better" an existing UI/codebase. # `invocation:` was not a field Claude Code reads - unknown frontmatter keys are # ignored without an error, so these six were auto-invocable the whole time they # were marked user-only. This is the field that actually does it. disable-model-invocation: true --- # Skill: Redesign & Audit > **Step 0: is the kit here?** This skill reads files from the kit. Check once: > `ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING` > On `KIT_MISSING` only the skill folders were installed, which is what > `npx skills add` does. Say so plainly, point the user at > `npx ux-ui-agent-skills init` or the plugin install, and stop. Do not guess the > contents of a file you could not open. Audit-first redesign that preserves behavior. ## Steps 1. Read `${CLAUDE_SKILL_DIR}/../../../workflows/redesign-audit.md` (the full Scan → Diagnose → Direct → Apply → Verify sequence + Output Completeness). 2. **Scan** the codebase: framework, styling method (→ route to the matching `${CLAUDE_SKILL_DIR}/../../../frameworks/` adapter), token reality, components, what must be preserved. 3. **Diagnose** with the Banned Defaults checklist (`${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md`) + the review rubric (`design-review` skill). Produce a prioritized findings table. 4. **Direct**: choose an archetype/system (`apply-aesthetic` skill) that fits the brand. 5. **Apply** in order (tokens first, then typography/spacing, then component states, then motion) without changing routes/data/markup semantics (except a11y fixes). 6. **Verify**: re-run `design-review` + `a11y-audit`; smoke-test every previously working flow; dark mode + responsive spot-check. Run `${CLAUDE_SKILL_DIR}/../../../scripts/validate_contrast.py` on the token source and `${CLAUDE_SKILL_DIR}/../../../scripts/lint_hardcodes.py` over the changed code. ## Guardrails Never sacrifice a working feature for aesthetics. Never ship a brand color that fails contrast. Never remove existing accessibility affordances. Deliver complete files, no placeholders. ## Single-theme consistency (critical for multi-page apps) Consolidate to ONE shared token theme and make **every page** consume it. A redesign that leaves different pages on different palettes has failed. Replace per-page/ad-hoc colors with semantic tokens; verify with `${CLAUDE_SKILL_DIR}/../../../scripts/lint_hardcodes.py` that no page reintroduces off-theme values. Theme switches must come from the single token source, not page edits (`${CLAUDE_SKILL_DIR}/../../../.claude/rules/tokens-and-color.md` → Single-Theme Consistency).
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.