Visual Regression Guardian (Playwright)
Do not use when
- •The request is unrelated to this domain or requires a different specialized skill.
- •The user asks only for high-level discussion without applying this workflow.
- •Another skill has a tighter, more specific trigger for the same request.
Example user requests
- •"Apply visual regression guardian to improve this feature."
- •"Use visual regression guardian and give me the concrete deliverables."
- •"Can you run a full visual regression guardian pass on this repo?"
- •"I need step-by-step execution using visual regression guardian."
Goal
Prevent visual drift and catch subtle regressions in high-impact UIs.
When to use
- •PRODUCTION+.
- •After tokens and signature patterns exist.
- •Before client handoff.
Minimal inputs (ask only if missing)
- •Routes to baseline.
- •Viewports.
- •Light/dark variants.
Procedure (MUST)
- •Add and configure Playwright.
- •Create
docs/visual_regression.mdfrom template. - •Implement visual tests for key routes and critical states.
- •Define snapshot update policy.
- •Integrate into CI.
Outputs (MUST produce)
- •
docs/visual_regression.md. - •
tests/visual/*.spec.*. - •Playwright config + report artifacts.
Notes
Snapshots are reviewed artifacts, not auto-updated noise.