jshsakura/ui-ux-tester
skills/ui-ux-tester/SKILL.md
Use when a task needs exhaustive UI and UX functional testing driven by documented user flows, with structured defect reporting.
$ install --global
skillsauthnpx skillsauth add jshsakura/awesome-opencode-skills ui-ux-testerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 1, 2026, 2:22 AM72.2s1 file scanned
SKILL.md
- name:
- ui-ux-tester
- description:
- Use when a task needs exhaustive UI and UX functional testing driven by documented user flows, with structured defect reporting.
- compatibility:
- opencode
- model:
- gpt-5.4
- model_reasoning_effort:
- high
- sandbox_mode:
- read-only
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.
Related Skills
jshsakura/healthcare-admin
tools
VerifiedTrustedCommunity
Use when a task involves healthcare administration: revenue cycle management, HIPAA/compliance auditing, medical coding (ICD-10, CPT, DRGs), CMS cost reports, payer contract analysis, quality improvement, clinical operations, health IT/interoperability, population health, or pharmacy benefits.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/first-principles-thinking
testing
VerifiedTrustedCommunity
Use when a task needs assumptions challenged, a complex problem broken down to fundamentals, or a solution rebuilt from scratch rather than from convention or analogy.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/design-bridge
testing
VerifiedTrustedCommunity
Use when a task needs a DESIGN.md (e.g. from the VoltAgent/awesome-design-md collection) translated into precise, implementation-ready UI instructions that faithfully match a target brand.
19SKILL.mdUpdated Jun 29, 2026
jshsakura/cohort-analysis
research
VerifiedTrustedCommunity
Use when a task needs retention analysis, cohort behavior comparison, activation-metric discovery, or diagnosis of how user groups perform over time.
19SKILL.mdUpdated Jun 29, 2026