# UI Verify

> Visual regression testing for agent-written UI, and an alternative to Chromatic and Percy. UI Verify captures your components on every pull request, diffs them against a baseline, and an AI judge tells an intended change from a real regression. Works with Storybook or Playwright, no Storybook required.

The full text of every page is inlined at [https://uiverify.ai/llms-full.txt](https://uiverify.ai/llms-full.txt).

## Getting started
- [Home](https://uiverify.ai/): What UI Verify is and how it works.
- [Storybook quickstart](https://uiverify.ai/docs/quickstart-storybook): Add visual testing to Storybook in minutes.
- [Playwright quickstart](https://uiverify.ai/docs/quickstart-playwright): Visual-test real pages with Playwright, no Storybook.
- [Pricing](https://uiverify.ai/#pricing): Plans and per-snapshot pricing.

## Docs
- [What is visual regression testing?](https://uiverify.ai/docs/what-is-visual-testing): Visual regression testing catches unintended UI changes by diffing a screenshot of your UI against a known-good baseline, pixel by pixel.
- [Storybook visual regression testing](https://uiverify.ai/docs/quickstart-storybook): Add visual regression testing to Storybook in minutes: install the uiverify CLI, build your stories, and get a screenshot diff check on every pull request.
- [Playwright visual regression testing](https://uiverify.ai/docs/quickstart-playwright): Turn your Playwright tests into visual regression tests: capture a deterministic archive of the real pages they visit and diff it on every pull request. No Storybook.
- [How visual regression testing works](https://uiverify.ai/docs/how-visual-testing-works): From CI upload to a green check: how UI Verify renders every component in a real browser, diffs it against its baseline, and has an AI judge triage each change.
- [Baselines and branches](https://uiverify.ai/docs/baselines): A baseline is the known-good screenshot every new capture is diffed against. It is chosen per branch and updates only when you accept a change.
- [Skip unchanged stories with --only-changed](https://uiverify.ai/docs/skip-unchanged): Render only the stories your pull request affects and carry the rest forward - the biggest lever on build time and per-snapshot cost on a large Storybook.
- [Automated visual review with an AI judge](https://uiverify.ai/docs/the-ai-judge): Not every visual change is a bug. UI Verify's AI judge tells an intended change from a real regression, so your review queue is only what actually needs a human.
- [UI Verify vs Chromatic](https://uiverify.ai/docs/uiverify-vs-chromatic): A Chromatic alternative built for agent-written UI: the same screenshot diffing, plus an AI judge that triages each change and MCP review from your coding agent.
- [Reduce visual test snapshots and cost](https://uiverify.ai/docs/economical-stories): Every visual testing tool bills per story. Two patterns cut a component's snapshot count up to 10x with the same coverage, on UI Verify, Chromatic, or Percy.
- [Fix flaky visual tests](https://uiverify.ai/docs/deterministic-captures): A visual test should only diff when the UI really changed. Every flaky diff traces to run-to-run variation you can eliminate at capture time.
- [Triage visual changes from your coding agent](https://uiverify.ai/docs/triage-with-your-agent): Review a UI Verify build without leaving your terminal. The UI Verify MCP lets Claude Code, Cursor, or any MCP client read a build's changes and accept baselines.
- [Troubleshooting UI Verify](https://uiverify.ai/docs/troubleshooting): Fixes for the common UI Verify setup problems: no check on your PR, an empty Playwright archive, phantom diffs after branching, and auth failures on upload.

## Agent skills
- [Factory](https://uiverify.ai/skills/factory): Say what you want. Get a merge-ready PR.
- [Review loop](https://uiverify.ai/skills/review-loop): Review and fix until the diff is actually clean.
- [Multi-model review](https://uiverify.ai/skills/review-multi-model): Two models review the same diff. You get one verified report.
- [E2E verify](https://uiverify.ai/skills/e2e-verify): Drive the real app, not just the tests.
- [Babysit a PR](https://uiverify.ai/skills/babysit-pr): Open it, watch CI, fix what's red, to green.
- [Add rule](https://uiverify.ai/skills/add-rule): Turn a correction into a rule and a lint guard.
- [Evaluate a run](https://uiverify.ai/skills/evaluate-run): Grade a finished run, cold and adversarially.
- [Set up visual testing](https://uiverify.ai/skills/setup-visual-testing): From no visual tests to a green check on every pull request.
- [Write economical stories](https://uiverify.ai/skills/economical-stories): Full visual coverage in the fewest billable snapshots.
- [Deterministic Storybook stories](https://uiverify.ai/skills/storybook-visual-testing): Stop story diffs that come back changed without a real change.
- [Deterministic Playwright captures](https://uiverify.ai/skills/playwright-visual-testing): Stop real-page diffs that flake without a real change.
- [Triage a build from your agent](https://uiverify.ai/skills/triage-visual-changes): Bucket real regressions vs noise and accept baselines, over MCP.

## Blog
- [Stop writing Storybook stories by hand](https://uiverify.ai/blog/stop-writing-storybook-stories-by-hand): You don't have to write Storybook stories or visual tests by hand. Add one CLAUDE.md rule and a lint guard, and your coding agent writes and maintains them.
- [How to not spend a fortune on visual testing](https://uiverify.ai/blog/cut-chromatic-bill-10x): Visual testing bills per snapshot, so story count is the cost. On Chromatic, Percy, Playwright, or UI Verify, two changes to how you write stories cut it up to 10x.