plugin87/ux-ui-agent-skills

prototype

Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill prototype

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Skill: Prototype & Research

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.

Guide work through the right fidelity level with validation.

Steps

  1. Read ${CLAUDE_SKILL_DIR}/../../../workflows/prototyping.md (5-level fidelity ladder, journey mapping template, usability-testing script, sample data).
  2. Identify the current need and pick the lowest fidelity that answers it — never skip levels:
  • Content-first (info needs) → Wireframe (layout/nav) → Low-fi (task completion) → High-fi (visual/a11y) → Code (feasibility/perf).
  1. For flows: produce a user-journey map with decision points, error paths, and edge cases.
  2. For validation: define the usability test (tasks, success criteria, 5-user rule) using the script.
  3. High-fi/code steps pull tokens (${CLAUDE_SKILL_DIR}/../../../tokens/*), components (${CLAUDE_SKILL_DIR}/../../../components/*), taste (${CLAUDE_SKILL_DIR}/../../../taste/*), and a11y (${CLAUDE_SKILL_DIR}/../../../accessibility/*).

Output

The artifact at the chosen fidelity + an explicit "what we validate next" plan.

Verification (before declaring done)

  • The fidelity matches the question being answered — no level skipped.
  • Flows include decision points, error paths, and edge cases (empty/loading/overflow), not just the happy path.
  • A concrete validation step is named (tasks + success criteria), not "test later".
  • High-fi/code artifacts pass the same token + a11y bar as design-code (no hardcoded values, contrast, states).

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
plugin87
커뮤니티

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

1시간 설치 수
1
GitHub Stars
3.2천
업데이트
11월 18일
plugin87
커뮤니티

design-qa

Set up or run design QA gates for token + hardcoded-value lint, automated a11y (axe), contrast, visual regression across variants/states/themes/RTL, and the manual a11y checklist. Use when the user wants CI quality gates, to prevent design regressions, or to QA a component/screen before shipping.

1시간 설치 수
2
GitHub Stars
3.2천
업데이트
11월 18일
plugin87
커뮤니티

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/codebase.

1시간 설치 수
2
GitHub Stars
3.2천
업데이트
11월 18일
plugin87
커뮤니티

data-dashboard

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data console, or any screen whose job is to show many numbers at once. Covers the layout sequence, the SVG geometry, the accessibility contract per chart type, and the contrast traps tha

1시간 설치 수
1
GitHub Stars
3.1천
업데이트
10월 27일