--- name: visual-verification description: "Verify visual UI changes vs mockups/identity; check screenshots across themes/scales/containers." --- # Visual verification Treat accepted visual references as acceptance criteria, not inspiration. ## Anchor - Inspect the canonical identity asset before inventing or changing visual language. - Identify the accepted reference and preserve identity, proportions, grouping, visible action count, and interaction hierarchy. - Inspect neighboring UI and the actual host container before choosing dimensions or styling. - Reuse native components, renderers, and theme roles where possible instead of replacing working behavior. ## Inspect rendered behavior - Preview in isolation when live changes could disrupt boot or the hosting session; verify renderer or loader version parity. - Inspect a representative screenshot or actual rendering in the target container, scale, and theme. - Compare frame dimensions, spacing, row structure, wrapping, and visible actions against the accepted reference. - Adapt to real host scale without changing the accepted visual hierarchy or blindly shrinking the whole container. - Check text and control contrast, selected states, destructive actions, and consistency with neighboring UI. - Keep ordinary UI domain-specific; summarize diagnostics and hide raw paths, source references, and provenance outside explicit diagnostic views. - After corrections, inspect a fresh rendering rather than assuming the source change fixed the appearance. ## Evidence and completion - Preserve evaluation-run artifacts unchanged; fix the tool, implementation, or guidance and rerun instead of polishing evidence. - Keep disposable screenshots, profiles, logs, and derived previews in approved OS-temp locations, not the repository. - Report the inspected rendering, runtime conditions, remaining mismatches, and unverified states. - Report visual verification as unrun when no representative rendering was inspected; passing structural checks alone does not establish visual fidelity.