사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill redesign시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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).
