wellmate-visual-regression

Validate UI visual changes through baseline capture, rendering comparison, and accessibility checks.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill wellmate-visual-regression-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wellmate-visual-regression
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/wellmate/visual-regression
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill wellmate-visual-regression-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Uncontrolled visual rewrites can silently break layout, contrast, focus states, and emergency-critical UI. This Skill enforces a repeatable loop of baseline capture, controlled change, rendering, comparison, and repair so every visual iteration is intentional, measurable, and reversible. ## Core Features & Use Cases - Baseline Management: Capture representative states across routes, viewports (360px mobile through desktop), appearance modes, and accessibility settings before making changes. - Regression Comparison: Systematically check layout geometry, spacing, typography, contrast, translucency, z-index layering, safe-area behavior, and animation states against the baseline. - Accessibility & Emergency Gates: Verify focus-visible, keyboard order, target size, reduced motion, high contrast, and that emergency CTAs remain solid, readable, and instantly actionable. - Use Case: When restyling a health app's dashboard with glassmorphism effects, use this Skill to capture baselines first, apply one material change at a time, and confirm no per-row blur or contrast regression was introduced. ## Quick Start Use the visual regression skill to establish baselines for the dashboard and habits screens, then verify my Liquid Glass navigation change against them.

Frequently Asked Questions about wellmate-visual-regression

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent visual regressions when redesigning a UI?▼

Capture baseline screenshots of representative routes and states before changing anything, then apply one design concern per iteration. After each change, render the same baseline set and compare layout, spacing, contrast, and interaction states against it.

What viewports should I use for visual regression testing?▼

Use 360x800, 390x844, and 430x932 for mobile, tablet portrait and landscape, plus 1366x768 and 1440x900 for desktop. Include supported appearance modes and accessibility variants like high contrast and reduced motion.

How do I test glassmorphism UI without hurting performance?▼

Keep the visible glass-container count reasonable, never apply per-row backdrop blur, avoid nested filters, and do not continuously animate blur or shadows. Verify scrolling stays smooth on mobile-class devices and provide opaque fallbacks.

What accessibility checks belong in every visual change?▼

Verify focus-visible indicators, keyboard order, target size, contrast, high contrast mode, reduced motion, reduced transparency, large text and zoom behavior, and screen-reader labels. These checks apply to every visual iteration, not just final releases.

Why does my glass effect disappear behind scrolling content?▼

This usually indicates a stacking or containment problem rather than a z-index shortage. Inspect the stacking context and overflow containment of parent containers before increasing z-index values.

When should a visual difference be treated as a regression?▼

Treat cumulative spacing drift, changed text wrapping, clipping, lost focus rings, changed target sizes, and contrast loss as regressions. Ignore anti-aliasing noise unless it reflects a real layout or contrast shift, and document intentional differences explicitly.