Component screenshot testing is now simpler. The old way of storing baseline images in the repository is gone. They are now managed by an external service.
When the CI runs, it automatically compares new screenshots to the baselines. If there are differences, a comment is posted on your pull request. This comment shows the before and after images.
You do not need to update the baselines yourself. After your pull request is merged to the main branch, the new screenshots become the new baselines automatically.
Global
mkdir -p ~/.claude/skills/update-screenshotsProject
mkdir -p .claude/skills/update-screenshotsSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step