visual-qa

Topics in the source

• Visual QA — see it, judge it, push it
• 1. Run the site and capture
• 2. Critique with the rubric
• 3. Turn the lowest scores into specific changes
• 4. Iterate
• 5. Report

Code that "should" look good often doesn't. Never report visual work as done without looking at it. Start the dev server (or use a built HTML file), then: First time only: pip install playwright pillow && python3 -m playwright install chromium. For a specific page or section, pass its URL (e.g. /#work). Add .visual-qa/ to .gitignore. Then Read these images and look carefully: full1440.png, full375.png — overall composition, rhythm, mobile layout introsheet.png — the first 1.6s: is there an intro moment? Is it choreographed or does everything fade at once? scrollsheet.png — do sections enter with intent? Anything empty, half-revealed, or jumping? reduced.png — content fully visible without motion? report.json — overflow offenders, broken/blurry images, console errors, CLS, fonts in use If the user can share a reference site they love, capture it the same way and compare side by side — the gap is usually obvious once both are on screen. Score each 1–5 and write one concrete observation per line. Be honest — a 2 is a 2. | Area | Basic (1–2) | Premium (4–5) | |---|---|---| | Typography | one size jump, default weights, system font, centered everything | dramatic scale contrast (display

This is an excerpt. Refer to the complete source and its current requirements.