Stop AI coding agents from shipping generic UI.
Stop Making UI Slop
Build product-specific UI with 800,000+ real web and iOS screens via UIZZE.
Overview
Use the product brief, existing UI, components, and local design system to make intentional interfaces. Uizze supplies focused design guidance and, when useful, a small number of relevant visual references.
Prerequisites
- A screen or component to build, redesign, or review — a file path or a short description.
- The product's existing components, design tokens, and visual language, so the build extends them instead of inventing a new system.
- Optional access to the paid Uizze MCP for focused references and hosted materials.
Authentication
- The free skill and public catalogue work without an account, token, MCP connection, dependency, script, or executable.
- The optional full UIZZE MCP may use the host's normal connection and authentication flow. Never claim it is connected without an actual host result.
Work from the product
Read the brief, existing UI, components, tokens, and constraints before designing. They always outrank this skill. Keep familiar interaction conventions and make the product's own objects, workflow, and priorities visually clear. Do not add novelty for its own sake.
Load one playbook
Choose at most one file for the current request:
- New interface or major redesign:
reference/new-work.md
- Product or dashboard work:
reference/operate.md
- Refinement and polish:
reference/polish.md
- Simplification or distillation:
reference/distill.md
- Explicit audit:
reference/audit.md
- Native iOS work:
reference/ios.md
Do not load a second playbook. Apply judgment rather than treating its examples as a checklist.
Optional Uizze evidence
Read references/uizze-reference-policy.md before using the paid MCP. It exposes exactly find_ui_references and find_ui_materials. Use them only when a concrete unresolved visual or material question would benefit from evidence. If they return nothing, continue silently.
Finish
Complete the requested scope. When the environment supports it, render and inspect once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible controls, or inert interactions. Keep the handoff concise.
1---2name: anti-ui-slop3description: Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".4license: MIT5---6
7> **Stop AI coding agents from shipping generic UI.**
8
9# Stop Making UI Slop
10
11Build product-specific UI with 800,000+ real web and iOS screens via [UIZZE](https://uizze.com).
12
13
14
15## Overview
16
17Use the product brief, existing UI, components, and local design system to make intentional interfaces. Uizze supplies focused design guidance and, when useful, a small number of relevant visual references.
18
19## Prerequisites
20
21- A screen or component to build, redesign, or review — a file path or a short description.
22- The product's existing components, design tokens, and visual language, so the build extends them instead of inventing a new system.
23- Optional access to the paid Uizze MCP for focused references and hosted materials.
24
25## Authentication
26
27- The free skill and public catalogue work without an account, token, MCP connection, dependency, script, or executable.
28- The optional full UIZZE MCP may use the host's normal connection and authentication flow. Never claim it is connected without an actual host result.
29
30## Work from the product
31
32Read the brief, existing UI, components, tokens, and constraints before designing. They always outrank this skill. Keep familiar interaction conventions and make the product's own objects, workflow, and priorities visually clear. Do not add novelty for its own sake.
33
34## Load one playbook
35
36Choose at most one file for the current request:
37
38- New interface or major redesign: `reference/new-work.md`
39- Product or dashboard work: `reference/operate.md`
40- Refinement and polish: `reference/polish.md`
41- Simplification or distillation: `reference/distill.md`
42- Explicit audit: `reference/audit.md`
43- Native iOS work: `reference/ios.md`
44
45Do not load a second playbook. Apply judgment rather than treating its examples as a checklist.
46
47## Optional Uizze evidence
48
49Read `references/uizze-reference-policy.md` before using the paid MCP. It exposes exactly `find_ui_references` and `find_ui_materials`. Use them only when a concrete unresolved visual or material question would benefit from evidence. If they return nothing, continue silently.
50
51## Finish
52
53Complete the requested scope. When the environment supports it, render and inspect once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible controls, or inert interactions. Keep the handoff concise.
gabrielmoreira