# UI Regression

Should be used when the user asks to "verify UI changes", "audit UI quality", "test...

- Repository: https://github.com/fcakyon/claude-codex-settings (1195 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add fcakyon/claude-codex-settings --skill ui-regression -g -a claude-code -y`
Codex: `npx skills add fcakyon/claude-codex-settings --skill ui-regression -g -a codex -y`
Cursor: `npx skills add fcakyon/claude-codex-settings --skill ui-regression -g -a cursor -y`
Gemini CLI: `npx skills add fcakyon/claude-codex-settings --skill ui-regression -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add fcakyon/claude-codex-settings`

## Description

This skill should be used when the user asks to "verify UI changes", "audit UI quality", "test every screen and action", "run regression QA", "check a deployed UI", or "validate an extension release". Test known web and browser-extension workflows on localhost, staging, or production with action coverage, recovery, localization, accessibility, and real integration evidence. Use dogfood for open-ended bug discovery.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# UI Regression

Verify that the requested UI works from entry to outcome. Cover the changed surface and its dependencies, without expanding a small edit into an unrelated product audit.

Use the browser tools available and permitted in the current environment. When using the agent-browser CLI, read [its skill](../agent-browser/SKILL.md) first. This workflow does not require a particular browser driver or local source access.

## Scope and evidence

- Identify the target URL or extension build, environment, affected screens, actions, roles, locales, and dimensions. Inspect source and API contracts when available. For deployed-only QA, derive coverage from visible navigation and the requested workflows.
- Keep a compact coverage ledger in working notes or an existing artifact: screen/state, expected outcome, observed result and evidence. Track functional behavior, rendered quality and runtime health separately as pass/fail/unverified/not-applicable. Inventory before testing and update as results arrive; passing interactions cannot approve unchecked visuals.
- Confirm the effective URL after navigation, candidate revision or deployed version, browser, viewport, device pixel ratio, data source and build mode. Verify runner overrides take effect before exercising a local candidate. Mark unknown revisions explicitly. Compare baselines at matching content, state and dimensions.
- When asked to test every function, account for every inventoried action. Do not silently omit blocked checks or impose an arbitrary bug-count stopping point.

## Real behavior and safe boundaries

The rest: https://github.com/fcakyon/claude-codex-settings/blob/HEAD/plugins/agent-browser/skills/ui-regression/SKILL.md