ui-review-and-polish

Review a UI artifact for design-system adherence by validating layout, visual hierarchy, and interaction states using evidence-first guardrails. The process checks responsiveness and accessibility basics, then emits a structured ui-polish-report that either approves handoff or blocks it with required fixes.

Validate interaction states and responsive layout in an existing prototype by reviewing the implemented screen against artifact-bound evidence. The review checks responsiveness across desktop and mobile views, applying fail-closed behavior that returns blocked or partial outcomes when required runtime proof is missing.

Anti-AI-Slop gate taxonomy evidence in a UI review is proof tied to specific gate IDs that validates visual claims and design decisions. It enforces fail-closed behavior, blocking handoff approval when critical proof, validator output, or owner approval is missing from the ui-polish-report.

A UI polish review can be used for mobile, desktop, and browser extension views. It applies to prototypes and implemented framework screens as part of the review phase before handoff, ensuring copy fit and accessibility basics are validated across all specified platforms.

A UI review blocks handoff approval when runtime proof is missing because it enforces evidence-first, fail-closed guardrails. This mechanism prevents unvalidated visual claims from passing, returning partial outcomes until required receipts, validator output, and Anti-AI-Slop evidence are provided.

The best way to ensure accessibility basics and copy fit are checked before approving a UI mockup is to run an evidence-first review. This process validates the artifact against design-system rules and emits a ui-polish-report with confidence scoring and concrete required fixes.