name: "ui-check"
description: "Visually verify changed UI behavior, layout, and relevant responsive states."
createdAt: "2026-09-11T18:46:00.191400+00:00"
repoUrl: "https://skillz.supply/skills/did:plc:xbtmt2zjwlrfegqvch7fboei/skills.ui-check/SKILL.md"
# ui-check Inspect the changed interface in a browser or the target application before claiming visual verification. Use the available inspection tools; a particular MCP server is not required. A successful build or an element appearing is not visual evidence. Choose coverage based on what changed: - Responsive layouts: a narrow phone viewport (around 390px) and desktop (around 1280px). - Theme-sensitive styling: light and dark when supported. - State-dependent behavior: relevant empty, populated, loading, error, and auth states. - Hydration-sensitive changes: server first paint and client-rendered state. - Deployment-sensitive behavior: a preview or the environment users will reach. Look at spacing between neighboring elements, shared alignment and gutters, long content, missing assets, and clipping. Measure geometry when a screenshot cannot resolve a spacing claim. Inspect the surrounding page as well as the component. Interact with changed controls and check for new console errors. Fix defects exposed by the inspection and recheck the affected cases. Report the coverage, outcome, and material gaps concisely; do not generalize one checked state to an entire interface. A written checklist for every screenshot is unnecessary.