What problem does it solve? Per-snapshot visual testing tools bill and diff per rendered story, so writing one story per variant, state, or theme multiplies both cost and noise. A component with 5 sizes × 3 states × 2 themes becomes 30 snapshots the naive way, inflating the visual-testing bill and the flake surface. ## Core Features & Use Cases - Gallery stories: Render the entire size/variant/theme matrix in a single grid story so one snapshot covers every combination. - Data-driven states: Drive loading, empty, error, and loaded states from fixed fixtures or mocked responses in one story instead of one story per fetch state. - Granularity tradeoff guidance: Explains when to merge variants (shared component matrices) versus when to keep independent pages and flows separate to avoid coupling unrelated diffs. - Use Case: A Button component with 3 sizes × 3 variants collapses from 9 stories into one gallery story, cutting billed snapshots by roughly 90% while keeping full visual coverage. ## Quick Start Ask the agent to refactor my Button stories so all size and variant combinations render in a single gallery story instead of one story per combination.
