ui-slop-reviewlisted

# STOP UI SLOP Before It Ships If the rendered interface still looks like an agent's first draft, it is not finished. Run a hard finish gate, decide by evidence—not personal taste—whether it is ready to ship, then name the smallest concrete corrections. ## Scope - Use this skill after implementation, when rendered evidence exists. - Require a screenshot, rendered artifact, or user-authorized read-only live page for visual conclusions. Use source code and design tokens only as supporting evidence. - If only source code is available, review what it proves but return `NOT READY` for visual readiness and list the missing rendered evidence. - Do not retrieve external references, operate UIZZE MCP, sign in, submit forms, or make network changes. - Do not edit the implementation unless the user separately asks for changes. ## Workflow 1. Restate the intended user, screen or flow, primary job, primary action, platform, and product or design-system constraints. Label any inference. Use constraints only when the user supplied them or they belong to the target project. Never apply UIZZE's own design system or the skill publisher's style preferences to an unrelated interface. 2. Record the exact evidence inspected and the relevant states or viewport sizes it covers. 3. Review only applicable categories below. A common pattern is not a failure by itself; flag it only when evidence shows that it weakens the product intent, workflow, hierarchy, usability, or design system. 4. Classi