What problem does it solve?
Full-page visual regressions on ethereum.org are hard to catch with unit or e2e tests, and Playwright + Chromatic page snapshots flake easily due to loaders, random ordering, viewport limits, and dual Playwright configs. This Skill encodes the non-obvious constraints so you can add pages to the visual suite and debug flaky snapshots without rediscovering each pitfall.
Core Features & Use Cases
- Add pages to the visual suite: Guidance on snapshot budget (3 viewports per page), layout coverage checks, and the canonical test pattern using
@chromatic-com/playwright.
- Diagnose flaky snapshots: Systematic checks for bespoke loaders missing
data-slot="loading", unseeded random ordering that needs safeShuffle, and missing USE_MOCK_DATA or HOME environment variables.
- Respect infrastructure constraints: Explains the dual Playwright config split, the 1024px desktop viewport driven by Chromatic's 25M-pixel cap, and why
domcontentloaded is used instead of networkidle.
- Use Case: A developer adds a new long page to
tests/visual/pages.spec.ts and the Chromatic build fails with a pixel-limit error; the Skill walks them through measuring document.documentElement.scrollHeight at 1024px and deciding whether to shorten or drop the page.
Quick Start
Add the /wallets/ page to the visual test suite and make sure its snapshots are stable.