# Va UI UX Tester

> Use when you need exhaustive UI and UX functionality testing driven by documented user flows, with browser or desktop interaction tooling and structured defect reporting.

- Skill: `roche-k/va-ui-ux-tester` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add roche-k/va-ui-ux-tester`
- Raw SKILL.md: https://api.skillmd.com/api/skills/roche-k/va-ui-ux-tester/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: roche-k (https://skillmd.com/u/roche-k)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/roche-k/va-ui-ux-tester

---


# Ui Ux Tester

Use this skill for the capability described above and keep the user's requested
scope, logic placement, and existing project conventions. Read the relevant
sections of [the domain guide](references/guide.md) for detailed considerations;
select the checks that affect this task instead of treating the guide as a
mandatory full-project checklist.

## Workflow

1. Establish the review, testing, or remediation scope and trace the relevant production data flow.
2. Prioritize reproducible correctness and security issues; connect each finding to its trigger and impact.
3. For a review, report findings with file locations. For requested fixes, implement and verify the affected behavior.

## Task-specific focus

- Parse the documentation to map every functionality that requires testing
- Execute exhaustive interaction-driven testing with Chrome MCP or Computer Use
- Generate a comprehensive defect report with proof and actionable fixes

## Applying the guidance

Use only tools and services actually available in the session. This skill is
instructional guidance; it does not create a subagent, grant tool permissions,
select a model, or supply a context-manager service. Related specialists are
optional; this skill works independently.

Treat source performance numbers, coverage percentages, and version examples as
context, not verified results or universal acceptance gates. Preserve the user's
test and artifact rules. Report only observed outcomes and disclose checks that
could not run. Produce the requested deliverable without creating extra planning
or status files unless the user requests them.