Visual Parity Audit

Drive two running instances of the "same" UI through matching states, take screenshots at a controlled viewport, and ship a reviewable PDF. Used to catch regressions that code review misses — typography, spacing, color, animation-entry state, or labels that drifted during a port.

When to use

• Port audits — old framework vs new framework should render pixel-close. (e.g. Express + vanilla HTML → Nuxt)
• Staging vs production — before cutover, prove no drift.
• Before client sign-off — supplier-built UI has to match designer's reference.
• After a "small" refactor — prove nothing cosmetic changed unintentionally.

Not this skill: functional BDD testing, accessibility audits, performance profiling. This is a typography-and-layout eyeball check.

Prerequisites