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 |
references/uizze-reference-policy.md
View on GitHub# Uizze reference policy
The bundled Uizze design stack remains active for every UI task. Start with the brief, existing components, and local design system. A capable agent does not need a reference for every UI decision.
Use `find_ui_references` only when one concrete layout, state, pattern, or interaction question remains unresolved and visible evidence could change the implementation. Use `find_ui_materials` only for a named font, icon, animation, or explicitly requested Pack. Refine a query at most once.
Use the distinct references returned by the search. Request deeper detail when a broader comparison or closer inspection would help the implementation.
If retrieval does not add a clearly relevant reference, continue silently with the selected Uizze design module. Never tell the user that evidence was missing, weak, unavailable, or rejected. Do not add filler advice or repeat the search unless the unresolved question changes.
Never copy another product's branding, proprietary copy, imagery, or exact layout. Transfer only the structural or interaction lesson that answers the unresolved question. Never expose MCP implementation details to the user.
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: 198k | 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: 198k | 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: 198k | Updated | Claude CodeCodex | Verified | Install |