AutoGineer
Generated banner for Anti UI Slop
Generated logo for Anti UI Slop

Anti UI Slop

GitHubOfficialCreated by UIZZEDistributed by GitHub

  • Skill
  • Review and audit
  • Software development
  • Apache-2.0
  • No issues found
Download ZIP

From the author

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".
— the description by UIZZE

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

anti-ui-slop is a design-focused skill designed to prevent AI coding agents from producing generic or low-quality interfaces. It forces the agent to prioritize the product's existing design system, components, and constraints over arbitrary novelty. By utilizing a structured set of playbooks and optional evidence-based references from a large library of real-world screens, the skill ensures that UI implementations are intentional, consistent, and polished. It includes a final inspection gate to catch common visual and functional defects before handoff.

What it does

  • Guides agents to build UI based on existing design tokens and components.
  • Provides specific playbooks for tasks like new interface design, dashboard work, and polish.
  • Integrates with a large library of real-world web and iOS screens for visual evidence.
  • Enforces a hard finish gate to identify and fix clipping, overlap, and accessibility issues.
  • Prevents the introduction of unnecessary design novelty that deviates from the product's visual language.

When to use it

  • When designing or implementing new web or iOS interfaces.
  • During major UI redesigns to ensure consistency with existing systems.
  • When refining or polishing existing components to improve visual quality.
  • When performing an explicit audit of an interface to identify and fix layout or interaction bugs.

Advantages

  • Reduces generic UI output by grounding decisions in real-world patterns.
  • Maintains design system integrity by prioritizing local constraints.
  • Improves final output quality through a structured pre-ship review process.
  • Supports diverse UI tasks via specialized, context-aware playbooks.

Usage examples

“anti-ui-slop: redesign this dashboard widget to match our current design system.”
The agent will analyze the existing components and tokens, select the operate.md playbook, and propose a design that aligns with the product's established visual language.
“run the UI finish gate on this new login screen.”
The agent will perform a final inspection of the rendered interface, checking for clipping, distorted media, and inaccessible controls before finalizing the code.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/github/anti-ui-slop/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip anti-ui-slop.zip -d .agents/skills

Documentation by UIZZE

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.

Image: 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.

Files

MANIFEST.json

{
  "name": "anti-ui-slop",
  "version": "quiet-expert-v12",
  "designStack": {
    "version": "4.1.1",
    "commit": "5a149f3fdb1b5793f10567233b1dcab98fc305fd",
    "license": "Apache-2.0"
  },
  "designAuthority": "uizze",
  "evidenceMode": "concrete-need-only",
  "included": [
    "reference/new-work.md",
    "reference/operate.md",
    "reference/polish.md",
    "reference/distill.md",
    "reference/audit.md",
    "reference/ios.md"
  ]
}

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
UIZZE
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/anti-ui-slop · commit 797337f
Licence
Apache License 2.0 (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by UIZZE or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download anti-ui-slop.zip