uizze-ui-researchlisted

Stop UI slop before it ships. Use 800,000+ real web and iOS screens to make Codex, Claude Code, Cursor, Copilot, and other coding agents build product-specific interfaces instead of disposable card-grid defaults. Apply a design contract and a hard finish gate when designing, implementing, restyling, or reviewing product UI.
uizze/uizze-mcp · ★ 1 · Web & Frontend · score 74

Install: claude install-skill uizze/uizze-mcp

> ***If your UI screams AI, your app is dead.*** # Stop Making UI Slop Build distinctive UI with 800,000+ real web and iOS screens via [UIZZE](https://uizze.com). ![Stop Making UI Slop with UIZZE](https://uizze.com/landing/anti-ui-slop-skill-banner.png) Kill the interchangeable card grid before it reaches users. Turn real interface evidence into a concrete design contract, build in the product's own visual language, then run a hard finish gate before shipping. Use this skill for free. Do not require a paid UIZZE account to apply the catalogue-driven workflow below. ## Free anti-slop workflow 1. Inspect the target repository, product intent, local design system, primary user job, primary action, and required UI states. 2. Browse or search the public catalogue at https://uizze.com for relevant screens, flows, and elements. If browsing is unavailable, ask the user to share two or three UIZZE links or screenshots; the catalogue remains free to use. 3. Extract transferable decisions from the evidence: hierarchy, workflow shape, density, navigation, controls, state behavior, and responsive treatment. 4. Write a short design contract naming the screen job, content hierarchy, allowed components, required states, product-specific decisions, forbidden generic patterns, and verification criteria. 5. Build with the repository's existing components and tokens. Make the result belong to this product rather than to a generic SaaS template. 6. Run a finish gate on the rendered result.