Naoray Visual Review
Verify what the user can see: layout, overflow, responsive behavior, hierarchy, terminal rendering, screenshots, and obvious visual regressions.
Evidence tier: P (practitioner-backed)
Basis: visual QA heuristics — layout stability, overflow, responsive behavior, hierarchy, affordance clarity, terminal legibility, state coverage. Adjacent to WCAG accessibility standards (E-tier) but this skill scopes to visible-output verification, not full accessibility audits.
Source IDs: WCAG 2.x accessibility guidelines, Nielsen usability heuristics, Naoray internal visual-review + visual-review-cli predecessors (now consolidated here).
Reviewed: 2026-05-12
Context Budget
Read only:
- This file.
workflows/preflight.md.- One mode workflow.
references/principles/visual-qa.mdwhen judging findings.
Do not load every file in this skill. evals/ is not runtime context.
Route
Read this file. Then read exactly one of:
workflows/web-review.md— browser/UI review of a PR or live URL across viewports.workflows/cli-review.md— terminal/TUI capture usingtermshot(static) orvhs(recordings).workflows/regression.md— before/after comparison for visual diffs.
If a PR changes both browser UI and CLI/TUI output, run the relevant modes separately and report them in one final summary.
Required First Step
Always read workflows/preflight.md before the selected workflow.
Output Rule
Every output MUST include screenshot or recording paths when artifacts were created, plus the routes, commands, viewport sizes, and states inspected — because a visual-review without an artifact and scope statement is just a claim, not evidence the reviewer can verify.