skills/common/common-web-visual-testing/SKILL.md
Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
npx skillsauth add hoangnguyen0403/agent-skills-standard common-web-visual-testingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
[!IMPORTANT] Tier 2 (Methodology): Strategy web UI/UX audit. Tier 3 (Domain): Responsive, A11y (WCAG), Browser Engine quirk.
Visual test best as Comparative Audit loop:
snapshot --aria + screenshot prod/main.Responses must label the two captures as Before and After (or Baseline and Fixed) and include the diff and neighboring-element side-effect check.
| Change Type | Scenarios to Run | | :---------------- | :------------------------------------------------- | | CSS/Layout | Responsive Audit + Hover + CLS Check | | Forms/Input | Validation Msg + Focus State + Error Boundary | | Navigation | URL Sync + Sticky Header + Back-Button Persistence | | Assets/Fonts | Lazy Load + Icon Check + LCP Audit | | Accessibility | Tab Order + Aria-Snapshot + Color Contrast |
--mask or JS (opacity: 0). Avoid "False Regression".playwright-cli snapshot --aria verify state before done.testing
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
documentation
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
development
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
data-ai
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.