plugin87/ux-ui-agent-skills

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.

First seen Jun 6, 2026

Installation

$ npx skills add plugin87/ux-ui-agent-skills --skill redesign

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from plugin87/ux-ui-agent-skills · top by installs.

npx skills add plugin87/ux-ui-agent-skills

Browse all from plugin87/ux-ui-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 902
License MIT License
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,057 B
  • docs SUMMARY.md 297 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 236 installs

SKILL.md

Skill: Redesign & Audit

Audit-first redesign that preserves behavior.

Steps

  1. Read 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 frameworks/ adapter), token reality, components, what must be preserved.
  3. Diagnose with the Banned Defaults checklist (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 scripts/validatecontrast.py on the token source and scripts/linthardcodes.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 scripts/lint_hardcodes.py that no page reintroduces off-theme values. Theme switches must come from the single token source, not page edits (.claude/rules/tokens-and-color.md → Single-Theme Consistency).