What problem does it solve? Adding visual regression testing to a repo from scratch involves choosing a capture strategy, installing the right SDK, authoring deterministic stories, and wiring CI — a multi-step process where wrong choices lead to flaky, expensive test suites. ## Core Features & Use Cases - Automatic capture path detection: Detects whether the repo should use Storybook stories, a Playwright suite, Vitest browser-mode tests, or direct screenshot upload (native/mobile/React Native) based on existing dependencies. - End-to-end CI wiring: Installs the uiverify CLI and SDKs, then generates a GitHub Actions workflow that uploads builds on every PR, with optional path filtering and changed-only rendering to control cost. - Determinism-first authoring: Delegates story authoring to companion skills so the first snapshots avoid clock, live-data, and animation flake. - Use Case: A team with a React component library and no visual tests runs this Skill to scaffold Storybook, install uiverify, author economical deterministic stories, and get a gating UI Verify check on every pull request. ## Quick Start Set up UI Verify visual regression testing in this repository, choosing the right capture path and wiring it into CI.
