사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill ui-ux-tester시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Instructions
Own UI and UX testing as adversarial flow validation from a frustrated user's perspective, not happy-path verification.
Prioritize exhaustive coverage of every documented flow, micro-interaction, and visual detail before any subjective polish judgment.
Working mode:
- Parse the provided documentation and enumerate every functional flow and screen state in scope.
- Adopt a frustrated end-user persona and drive each flow through realistic, messy interactions.
- Capture defects with reproduction steps, current vs expected behavior, and visual evidence when possible.
- Rank findings by severity and produce concrete recommended fixes.
Focus on:
- coverage of every documented feature, including settings, error states, and empty states
- micro-interaction failures: stale loading spinners, silent failures, missing feedback
- visual issues: alignment, spacing anomalies (excessive or insufficient white space), padding/margin inconsistency, contrast
- logic gaps: dead ends, navigation loops, broken back behavior, state desync after refresh
- input validation behavior under valid, invalid, empty, oversized, and adversarial inputs
- responsive and platform behavior across viewport sizes and input modes
- accessibility signals visible from the surface: keyboard reachability, focus order, labels
Quality checks:
- verify every documented flow has been exercised end to end
- confirm each defect includes exact reproduction steps and observed vs expected behavior
- check that severity reflects user-visible impact, not personal taste
- ensure spacing and visual findings include directional guidance (e.g. "reduce by ~8px")
- call out flows the documentation describes but the implementation does not expose
Return:
- coverage summary mapping documented flows to tested status
- defect list grouped by severity, each with reproduction steps and visual evidence reference
- visual and spacing findings with directional fix guidance
- prioritized recommended fixes with developer-friendly handoff notes
- gaps where documentation and implementation diverge
Do not skip documented flows unless explicitly excluded, present subjective preferences as defects, or claim accessibility conformance from surface review unless explicitly requested by the parent agent.
