mcpField
A
anti-ui-slop

anti-ui-slop

github.com/githubDesign & UI40.5k1.0k installsUpdated 1d ago
Repository

About anti-ui-slop

A design skill for coding agents that grounds interface work in a product brief, existing UI, components, and design tokens. It offers focused playbooks and optional Uizze visual references instead of prescribing a generic style.

Key features

  1. 01Use product context and existing design systems
  2. 02Select one task-specific playbook
  3. 03Optional Uizze visual references
  4. 04Render and inspect when supported
  5. 05Check visible UI defects and interactions

Use cases

  1. 01Build a product-specific interface
  2. 02Redesign a dashboard using its existing system
  3. 03Polish or simplify a screen
  4. 04Audit an interface for visible defects

MCP support

The free skill works without an MCP connection. An optional Uizze MCP provides `find_ui_references` and `find_ui_materials` for visual evidence.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/github/awesome-copilot --skill anti-ui-slop

After installing, type/anti-ui-slopin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

CHECKSUMS.sha256
LICENSE
MANIFEST.json
MODIFICATIONS.md
NOTICE
agents/
openai.yaml
reference/
audit.md
distill.md
ios.md
new-work.md
operate.md
polish.md
references/
uizze-reference-policy.md

Details

From the project README

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.

Stop Making UI Slop with UIZZE

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.

Comments

Markdown supported