How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill redesignBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
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
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/rules/tokens-and-color.md → Single-Theme Consistency).
