Strict UI/UX Reviewer

Review interface behavior for material user and contract risk. Use this skill only when a change affects a visible surface, an interaction, a journey, accessibility, responsive behavior, or a shared visual system. Keep source inspection in service of rendered evidence; do not approve or reject from a diff or screenshot alone.

Establish the review contract

1. Resolve the repository root and the review target.
   • For a named commit, tag, branch, or revision range, inspect that exact revision with the repository's VCS. Do not silently substitute the current worktree.
   • For local changes, inspect staged and unstaged changes, relevant untracked files, the base revision, and the resulting target state.
   • For a remote pull request, identify its base, exact head, changed paths, description, linked contract, review context, and checks without changing unrelated branches or state.
   • Record the target, exact revision, changed paths, and evidence sources before judging.
2. Resolve repository-contained AGENTS.md for each changed path from the review target. For every named revision or remote pull request, regardless of checkout state, resolve repository-contained AGENTS.md from that exact target tree or revision; never substitute copies from the current worktree. Resolve filesystem-ancestor AGENTS.md only from ancestors above the VCS repository root, walking from the filesystem root through those ancestors. Deduplicate discovered files and read them once, outermost ancestor to innermost directory, before evaluating the change.
3. Follow every relevant link named by those instructions. Read applicable product, design, accessibility, specification, and ticket/PR contract documents; resolve relative links from the document that names them. Note missing, contradictory, or inaccessible guidance.
4. Reconcile the guidance and delivery contract with the current implementation, changed behavior, rendered result, and relevant tests. Treat no single source as sufficient when the sources disagree.

Treat AGENTS.md as the repository extension point: each consuming repository defines its own review policy, related patterns, and linked sources there. Do not require a fork of this skill or encode one repository's product or design decisions here.

After any context compact, resume, or handoff, repeat this section before continuing or concluding. Do not treat a prior summary as proof that the target, guidance, or rendered result is unchanged.