Build Product-Specific UI from Real Screen Evidence

Stop Making UI Slop keeps a coding agent from shipping generic interfaces by working from the product first: identify the screen's real job, its primary user and action, the required content, and the loading, empty, error, success, disabled, and permission states it needs to cover; reuse the repository's own components, semantic tokens, typography, spacing, and interaction conventions before reaching for a new abstraction or visual language; write a short design contract for a new interface or major redesign covering hierarchy, workflow shape, allowed components, required states, responsive behavior, and observable acceptance criteria, keeping smaller changes correspondingly smaller; and use real, product-specific labels and data rather than inventing metrics, activity, testimonials, or placeholder workflows to make a layout look complete. Evidence from UIZZE's catalog of 800,000-plus real web and iOS screens is optional, not a research requirement for every task - it should answer one concrete unresolved visual question, using the smallest relevant set of reference screens. Install:

npx skills add https://uizze.com --skill anti-ui-slop

Use it when designing, implementing, redesigning, critiquing, or doing a pre-ship review of a web or iOS interface. References are evidence, not templates: useful decisions about hierarchy, density, navigation, controls, responsive behavior, and state handling can be transferred, but another product's branding, proprietary text, imagery, or exact layout must never be copied. The optional authenticated UIZZE MCP exposes exactly find_ui_references and find_ui_materials, used only when those tools are actually available - if a search returns nothing, the work continues silently from repository evidence rather than claiming an MCP-backed result that was never returned.

Input is the product brief, the existing interface and components, and, optionally, a concrete visual question UIZZE evidence might answer. Output is an interface (or design contract for a larger change) that reuses the product's own design system, covers every required state, and uses real data rather than placeholder content. When the environment supports it, the rendered result is inspected once and fixed for observable breakage - clipping, overlap, distorted media, inaccessible or inert controls, missing required states, unintentional responsive behavior - before the project's normal checks run and a concise handoff is given.

UIZZE's free public catalogue (no account, token, dependency, script, or executable required) and, optionally, the authenticated UIZZE MCP server for find_ui_references/find_ui_materials.

Teams and agents building or reviewing product UI who want it to look like it belongs to the actual product - covering the states that matter, reusing what the design system already has - rather than a generic, placeholder-filled interface assembled from outside references.