Individual skill
anti-ui-slop
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 for web or iOS UI design, implementation, redesign, critique, and pre-ship review in Codex, Claude Code, Cursor, Copilot, and other coding agents.
plugins/all-skills/skills/anti-ui-slop/SKILL.md
Source commit 82ce2112b080810c6b72939201d6a53876116e12
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,732
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-code Repository topic
- subagents Repository topic
- commands Repository topic
- claude-code-commands Repository topic
- cli-tool Repository topic
- mcp Repository topic
- mcp-server Repository topic
- mcp-tools Repository topic
- claude-skills Repository topic
- design Derived category
- engineering Derived category
- legal Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Stop Making UI Slop
Build product-specific interfaces with UIZZE's free anti-ui-slop workflow. Use the product brief, existing components, and design system to make the screen's hierarchy, content, controls, and states intentional.
## When to Use This Skill
Use it to design, implement, redesign, critique, or finish a web or iOS interface, especially when a first draft feels generic or omits important states.
## How to Use
1. Read the target screen, product context, and existing design system. Identify the primary user, action, content, and constraints.
2. Reuse the project's components, tokens, typography, and interaction conventions. For a substantial redesign, write a short design contract; keep a small fix small.
3. Use product-specific labels and real data requirements. Do not invent metrics, activity, testimonials, or controls to fill a layout.
4. Implement the required loading, empty, error, success, disabled, and permission states. Make the primary action and recovery paths clear.