anti-ui-slop

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

1. Identify the screen's real job, primary user and action, required content,

and important loading, empty, error, success, disabled, and permission states.

2. Reuse the repository's components, semantic tokens, typography, spacing, and

interaction conventions before adding a new abstraction or visual language.

3. 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.

4. 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 c