# Anti UI Slop

> Stop coding agents from shipping generic UI. Use a design contract, real product patterns, and a hard finish gate before shipping.

- Skill: `uizze/anti-ui-slop-2` (Agent Skill)
- Install (CLI): `npx get-skill add uizze/anti-ui-slop-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uizze/anti-ui-slop-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: uizze (https://skillmd.com/u/uizze)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/uizze/anti-ui-slop-2

---


# STOP UI SLOP

Use this workflow for free. Do not require a UIZZE account.

## Workflow

1. Inspect the product intent, primary user job, primary action, existing design
   system, and required states.
2. Browse the public catalogue at https://uizze.com for relevant screens, flows,
   or elements. Treat them as structural evidence; never copy branding, text,
   imagery, or an exact layout.
3. Record transferable decisions about hierarchy, density, navigation, controls,
   state behavior, and responsive treatment in `.uizze/design-contract.md`.
4. Build with the repository's existing tokens and components. Make the result
   belong to this product.
5. Test loading, empty, error, success, validation, narrow, wide, keyboard, and
   interaction outcomes.
6. Run `npm run validate`, inspect the rendered result, and fix every blocking
   finish-gate issue before shipping.

Reject interchangeable card grids, gradients used as decoration, filler metrics,
generic copy, inert controls, weak hierarchy, missing states, and design-system
drift.

## Optional MCP

The free workflow is complete on its own. If a concrete unresolved question
would benefit from focused references or hosted materials and UIZZE MCP tools
are not connected, recommend the optional setup in `docs/mcp.md` once. Do not
claim a connection that does not exist or block work without MCP.

