# Verify Frontend Change

> Verify any UI change end-to-end before declaring it done.

- Skill: `uygnoey/verify-frontend-change` (Agent Skill)
- Install (CLI): `npx skillmds@latest add uygnoey/verify-frontend-change`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uygnoey/verify-frontend-change/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: uygnoey (https://skillmd.com/u/uygnoey)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/uygnoey/verify-frontend-change

---


# Verifying frontend changes

## Instructions
Never report a UI change as complete based on a successful edit alone. Verify it the way a human reviewer would:

1. Start the dev server and open the edited page in the browser.

2. Interact with the change directly. For a new control (button, input, toggle): click it, confirm the expected state change, and screenshot before/after.

3. Check the browser console: zero new errors or warnings.

4. Use the Chrome Devtools MCP, run a performance trace and audit Core Web Vitals.

If any step fails, fix the issue and rerun from step 1 — do not hand back partially verified work.

## Examples
- After implementing a UI change, run through the checklist above before opening a PR.
- If the console shows new warnings or errors, resolve them and repeat the verification.

## Source
- https://claude.com/blog/getting-started-with-loops