Verify UI Changes

Verify UI changes across responsive states using a browser subagent.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/canyouseeus/thelostandunfounds --skill verify-ui-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Verify UI Changes
Source: https://github.com/canyouseeus/thelostandunfounds/tree/main/.agent/skills/verify_ui_changes
Command: npx skills add https://github.com/canyouseeus/thelostandunfounds --skill verify-ui-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable procedure to validate UI updates and bug fixes by driving a browser subagent to inspect visual correctness, stability, and alignment across components and viewports.

Core Features & Use Cases

  • Guided verification: captures target URL, key elements, interactions, and success criteria to standardize UI checks.
  • Browser-based validation: leverages a browser subagent to navigate, observe, and report visual deviations and console issues.
  • Regression reporting: generates a clear report with observed diffs, screenshots, and artifacts for issues across responsive states.

Quick Start

Launch the browser subagent and execute the predefined UI verification steps on the target page.

Frequently Asked Questions about Verify UI Changes

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

FAQPage Schema
How do I verify UI changes and prevent visual regressions after an update?

To verify UI changes, the Skill drives a browser subagent to inspect specific pages and components across responsive states, confirming visual stability and reporting any deviations with screenshots.

What is visual regression testing and how does a browser subagent execute it?

Visual regression testing checks for unintended UI changes. A browser subagent navigates defined targets, observes visual correctness across viewports, and reports deviations with context and artifacts.

How do I test frontend components across different responsive viewports?

You test frontend components across responsive viewports by defining target URLs and success criteria, then letting the browser subagent apply checks across various states to confirm no visual regressions.

Can I use this Skill to check specific page interactions and console issues?

Yes, this Skill can check specific page interactions and console issues. The browser subagent observes visual deviations and console problems during navigation, reporting them if they fail success criteria.

Do I need to provide target URLs and success criteria for frontend testing?

Yes, guided verification requires providing target URLs, key elements, interactions, and success criteria to standardize UI checks and accurately identify any visual deviations.

What is the best way to report UI deviations found during visual regression checks?

The best way to report UI deviations is generating a report with observed diffs, screenshots, and artifacts for issues across responsive states, ensuring results meet predefined success criteria.