Stop Making UI Slop
Build product-specific UI with 800,000+ real web and iOS screens via
UIZZE.
Overview
Use the product brief, existing interface, components, and local design system
before reaching for outside references. UIZZE evidence is optional: it should
answer a concrete visual question, not turn every interface task into a research
project.
When to Use
Use this skill when designing, implementing, redesigning, critiquing, or doing a
pre-ship review of a web or iOS interface.
Work From the Product
- Identify the screen's real job, primary user and action, required content,
and important loading, empty, error, success, disabled, and permission states.
- Reuse the repository's components, semantic tokens, typography, spacing, and
interaction conventions before adding a new abstraction or visual language.
- For a new interface or major redesign, write a short design contract covering
hierarchy, workflow shape, allowed components, required states, responsive
behavior, and observable acceptance criteria. Keep smaller changes smaller.
- Use product-specific labels and data. Do not invent metrics, activity,
testimonials, users, or placeholder workflows to make a layout look complete.
Optional UIZZE Evidence
The free skill and public catalogue work without an account, token, dependency,
script, or executable. If a concrete unresolved visual question would benefit
from evidence, use the smallest relevant set of screens or materials.
The optional authenticated UIZZE MCP exposes exactly find_ui_references and
find_ui_materials. Use it only when those tools are actually available. If a
search returns nothing, continue silently from repository evidence. Never claim
an MCP-backed result that was not returned by the host.
Treat references as evidence, not templates. Transfer useful decisions about
hierarchy, density, navigation, controls, responsive behavior, and state
handling; never copy another product's branding, proprietary text, imagery, or
exact layout.
Install the current free skill directly from its canonical source:
npx skills add https://uizze.com --skill anti-ui-slop
Finish
When the environment supports it, render and inspect the result once. Fix
observable breakage such as clipping, overlap, distorted media, inaccessible or
inert controls, missing required states, and unintentional responsive behavior.
Run the project's normal checks and keep the handoff concise.
Limitations
- This workflow does not replace product validation, accessibility review,
security review, or project-specific tests.
- UIZZE evidence is optional and may legitimately return no useful result.
- A reference is not permission to copy another product's identity or assets.
1---2name: anti-ui-slop3description: "Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result."4category: frontend5risk: safe6source: https://github.com/uizze/uizze/tree/main/skills/anti-ui-slop7source_repo: uizze/uizze8source_type: official9date_added: "2026-08-16"10author: UIZZE11tags: [ui, ux, frontend, design, anti-ui-slop]12tools: [claude, codex, cursor, copilot]13license: MIT14license_source: https://github.com/uizze/uizze/blob/main/LICENSE15metadata:16 source: https://skillmd.com/skills/uizze/anti-ui-slop17---1819# Stop Making UI Slop2021Build product-specific UI with 800,000+ real web and iOS screens via22[UIZZE](https://uizze.com).2324## Overview2526Use the product brief, existing interface, components, and local design system27before reaching for outside references. UIZZE evidence is optional: it should28answer a concrete visual question, not turn every interface task into a research29project.3031## When to Use3233Use this skill when designing, implementing, redesigning, critiquing, or doing a34pre-ship review of a web or iOS interface.3536## Work From the Product37381. Identify the screen's real job, primary user and action, required content,39 and important loading, empty, error, success, disabled, and permission states.402. Reuse the repository's components, semantic tokens, typography, spacing, and41 interaction conventions before adding a new abstraction or visual language.423. For a new interface or major redesign, write a short design contract covering43 hierarchy, workflow shape, allowed components, required states, responsive44 behavior, and observable acceptance criteria. Keep smaller changes smaller.454. Use product-specific labels and data. Do not invent metrics, activity,46 testimonials, users, or placeholder workflows to make a layout look complete.4748## Optional UIZZE Evidence4950The free skill and public catalogue work without an account, token, dependency,51script, or executable. If a concrete unresolved visual question would benefit52from evidence, use the smallest relevant set of screens or materials.5354The optional authenticated UIZZE MCP exposes exactly `find_ui_references` and55`find_ui_materials`. Use it only when those tools are actually available. If a56search returns nothing, continue silently from repository evidence. Never claim57an MCP-backed result that was not returned by the host.5859Treat references as evidence, not templates. Transfer useful decisions about60hierarchy, density, navigation, controls, responsive behavior, and state61handling; never copy another product's branding, proprietary text, imagery, or62exact layout.6364Install the current free skill directly from its canonical source:6566```bash67npx skills add https://uizze.com --skill anti-ui-slop68```6970## Finish7172When the environment supports it, render and inspect the result once. Fix73observable breakage such as clipping, overlap, distorted media, inaccessible or74inert controls, missing required states, and unintentional responsive behavior.75Run the project's normal checks and keep the handoff concise.7677## Limitations7879- This workflow does not replace product validation, accessibility review,80 security review, or project-specific tests.81- UIZZE evidence is optional and may legitimately return no useful result.82- A reference is not permission to copy another product's identity or assets.