anti-ui-slop — GitHub Copilot skill: UI and installation
This skill guides agents toward product-specific interfaces instead of generic UI. Use it for web or iOS design, implementation, redesign, and pre-ship review.
npx skills add github/awesome-copilot --skill anti-ui-slopWhat anti-ui-slop does
anti-ui-slop makes the agent inspect the product brief, existing UI, components, tokens, and constraints before changing an interface. It loads one playbook for the task: new work, product or dashboard work, polish, distillation, audit, or native iOS. For an unresolved visual question, the optional paid UIZZE MCP can provide focused references and materials from 800,000+ real web and iOS screens.
The skill checks required interface states and runs a finish pass for observable problems such as clipping, overlap, distorted media, inaccessible controls, and inert interactions. The free skill works without an account, token, MCP connection, dependency, script, or executable. You need a screen or component to build or review, plus the project's existing components and design tokens.
Install it when coding agents keep producing generic interfaces and you want a concrete review before shipping. For a project with no UI context, prepare a short product brief first.
What it helps with
- build a UI around a product's own workflow
- review a web screen before shipping
- cover required component states
- catch clipping and overlapping elements
- audit a native iOS interface
Example prompts for the agent
- Use anti-ui-slop to build the settings screen from the brief and existing components.
- stop UI slop: review this web screen and fix inaccessible controls.
- run the UI finish gate for the current iOS screen.
How to install anti-ui-slop
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill anti-ui-slop2GitHub CLI
gh skill install github/awesome-copilot anti-ui-slop3Manually: put the files in place
.github/skills/anti-ui-slop/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill anti-ui-slop -a claude-code2Manually: put the files in place
~/.claude/skills/anti-ui-slop/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/anti-ui-slop/
Manually: put the files in place
.agents/skills/anti-ui-slop/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/anti-ui-slop/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/anti-ui-slopManually: put the files in place
.devin/skills/anti-ui-slop/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →Similar
Questions about anti-ui-slop
How do I install anti-ui-slop in GitHub Copilot?
Run npx skills add github/awesome-copilot --skill anti-ui-slop or gh skill install github/awesome-copilot anti-ui-slop. The skill file is placed at .github/skills/anti-ui-slop/SKILL.md.
What does anti-ui-slop do?
It guides an agent through product context, existing components, design tokens, required states, and a final UI inspection. The review targets visible breakage and inactive interactions.
Do I need the UIZZE MCP to use this skill?
No. The free skill works without MCP, an account, a token, or dependencies. The paid UIZZE MCP adds focused visual references and hosted materials.
Source text
SKILL.md · MIT
--- name: anti-ui-slop description: '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 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".' license: MIT metadata: version: "1.2.13" author: "UIZZE <[email protected]>" compatibility: "Designed for Claude Code, Codex, Cursor, and GitHub Copilot; works in any agent that can read project files and fetch a URL." tags: "ui-design, design-system, design-review, frontend, web-ui, ios-ui" --- > **Stop AI coding agents from shipping generic UI.** # Stop Making UI Slop Build product-specific UI with 800,000+ real web and iOS screens via [UIZZE](https://uizze.com).  ## Overview Use the product brief, existing UI, components, and local design system to make intentional interfaces. Uizze supplies focused design guidance and, when useful, a small number of relevant visual references. ## Prerequisites - A screen or component to build, redesign, or review — a file path or a short description. - The product's existing components, design tokens, and visual language, so the build extends them instead of inventing a new system. - Optional access to the paid Uizze MCP for focused references and hosted materials. ## Authentication - The free skill and public catalogue work without an account, token, MCP connection, dependency, script, or executable. - The optional full UIZZE MCP may use the host's normal connection and authentication flow. Never claim it is connected without an actual host result. ## Work from the product Read the brief, existing UI, components, tokens, and constraints before designing. They always outrank this skill. Keep familiar interaction conventions and make the product's own objects, workflow, and priorities visually clear. Do not add novelty for its own sake. ## Load one playbook Choose at most one file for the current request: - New interface or major redesign: `reference/new-work.md` - Product or dashboard work: `reference/operate.md` - Refinement and polish: `reference/polish.md` - Simplification or distillation: `reference/distill.md` - Explicit audit: `reference/audit.md` - Native iOS work: `reference/ios.md` Do not load a second playbook. Apply judgment rather than treating its examples as a checklist. ## Optional Uizze evidence Read `references/uizze-reference-policy.md` before using the paid MCP. It exposes exactly `find_ui_references` and `find_ui_materials`. Use them only when a concrete unresolved visual or material question would benefit from evidence. If they return nothing, continue silently. ## Finish Complete the requested scope. When the environment supports it, render and inspect once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible controls, or inert interactions. Keep the handoff concise.
© UIZZE · MIT · github/awesome-copilot