anti-ui-slop
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.
The Rule
The coding agent remains the designer. UIZZE supplies eyes before important layout and interaction choices are fixed, then runs one narrow source-level blocker check after the first render of substantial work. It is not a house style, layout generator, product strategist, or requirement engine.
Improve the requested UI relative to its product, task, platform, and existing system—not relative to an abstract demand for novelty. A familiar pattern is not slop when it is the clearest fit. Do not make a coherent interface stranger, louder, or more decorative merely to prove this skill was used.
Do not add copy, labels, metrics, controls, sections, routes, states, dependencies, or visual motifs to demonstrate UIZZE. Inside a hero or section, make the h1/h2 the first visible text unless a functional breadcrumb is required; omit decorative eyebrow, kicker, overline, pre-headline, category, and numbered labels above it. Do not use colored dots, emoji, or Unicode glyphs as interface decoration or icons; use readable status text and the project's coherent SVG icon system when an icon is necessary. On narrow screens, adapt navigation instead of clipping or pushing controls off-screen, and keep button labels and icons aligned unless wrapping is intentional.