github/awesome-copilot / skills/anti-ui-slop
anti-ui-slop
UnverifiedStop 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 when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".
| File | Kind | Size |
|---|---|---|
| CHECKSUMS.sha256 | other | 1.1 KB |
| LICENSE | other | 10.5 KB |
| MANIFEST.json | config | 448 B |
| MODIFICATIONS.md | markdown | 275 B |
| NOTICE | other | 401 B |
| SKILL.md | skill md | 3.2 KB |
| agents/openai.yaml | config | 235 B |
| reference/audit.md | markdown | 827 B |
| reference/distill.md | markdown | 1.1 KB |
| reference/ios.md | markdown | 1.2 KB |
| reference/new-work.md | markdown | 1.7 KB |
| reference/operate.md | markdown | 1.3 KB |
| reference/polish.md | markdown | 1.1 KB |
| references/uizze-reference-policy.md | markdown | 1.1 KB |
reference/operate.md
View on GitHub# Product and dashboard interfaces
Product UI should disappear into the task. Familiarity is a feature when users need to move quickly and trust the controls.
## Structure
- Make the current location, primary task, and next action obvious.
- Match information density to the work. Dense tables and compact controls are appropriate when users need them; decorative containers are not.
- Prefer standard navigation, forms, tables, tabs, menus, and dialogs over novel replacements.
- Use spacing and alignment for grouping before adding borders, cards, or backgrounds.
- Keep one component vocabulary across the surface.
## States and behavior
- Cover the states the product can reach: loading, empty, error, success, disabled, selected, expanded, and recovery where relevant.
- Keep focus visible, controls labelled, contrast readable, and targets usable.
- Prevent overlays and menus from being clipped by scroll or overflow containers.
- Use quick motion only for state changes and feedback. Do not choreograph routine page loads.
- Make responsive changes structural: collapse navigation, reflow groups, and preserve access to important actions.
## Finish
Use the interface at representative sizes. Fix the few observable issues that obstruct the task or break consistency. Do not redesign working areas outside the requested scope.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |