SkillAgentSearch skills...

anti-ui-slop

Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.

Install / Use

npx skills add sickn33/agentic-awesome-skills --skill anti-ui-slop

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Category

Design

Supported Platforms

Claude Code
Cursor
GitHub Copilot
OpenAI Codex

Our assessment of anti-ui-slop

anti-ui-slop scores 90/100 on our quality scale, 83rd of 261 Design skills we index (top 32%).

Its SKILL.md is 3.3 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 49,671 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so anti-ui-slop is actively maintained.
  • Our last check on 2026-10-29 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

anti-ui-slop compared with similar skills

All 4 of these similar skills score higher than anti-ui-slop; compare them before choosing.

SkillScoreStarsUpdatedFormat
anti-ui-slop (this skill)by sickn339049.7k3d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md

Frequently asked questions

How do I install anti-ui-slop?
Run npx skills add sickn33/agentic-awesome-skills --skill anti-ui-slop. The install tabs above show the steps for each supported agent.
Which AI agents does anti-ui-slop work with?
It is written for Claude Code, Cursor, GitHub Copilot and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
Is anti-ui-slop safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is anti-ui-slop still maintained?
The repository was last updated 3 days ago, so anti-ui-slop is actively maintained.

name: anti-ui-slop description: "Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result." category: frontend risk: safe source: https://github.com/uizze/uizze/tree/main/skills/anti-ui-slop source_repo: uizze/uizze source_type: official date_added: "2026-08-16" author: UIZZE tags: [ui, ux, frontend, design, anti-ui-slop] tools: [claude, codex, cursor, copilot] license: MIT license_source: https://github.com/uizze/uizze/blob/main/LICENSE

Stop Making UI Slop

Build product-specific UI with 800,000+ real web and iOS screens via UIZZE.

Overview

Use the product brief, existing interface, components, and local design system before reaching for outside references. UIZZE evidence is optional: it should answer a concrete visual question, not turn every interface task into a research project.

When to Use

Use this skill when designing, implementing, redesigning, critiquing, or doing a pre-ship review of a web or iOS interface.

Work From the Product

  1. Identify the screen's real job, primary user and action, required content, and important loading, empty, error, success, disabled, and permission states.
  2. Reuse the repository's components, semantic tokens, typography, spacing, and interaction conventions before adding a new abstraction or visual language.
  3. For a new interface or major redesign, write a short design contract covering hierarchy, workflow shape, allowed components, required states, responsive behavior, and observable acceptance criteria. Keep smaller changes smaller.
  4. Use product-specific labels and data. Do not invent metrics, activity, testimonials, users, or placeholder workflows to make a layout look complete.

Optional UIZZE Evidence

The free skill and public catalogue work without an account, token, dependency, script, or executable. If a concrete unresolved visual question would benefit from evidence, use the smallest relevant set of screens or materials.

The optional authenticated UIZZE MCP exposes exactly find_ui_references and find_ui_materials. Use it only when those tools are actually available. If a search returns nothing, continue silently from repository evidence. Never claim an MCP-backed result that was not returned by the host.

Treat references as evidence, not templates. Transfer useful decisions about hierarchy, density, navigation, controls, responsive behavior, and state handling; never copy another product's branding, proprietary text, imagery, or exact layout.

Install the current free skill directly from its canonical source:

npx skills add https://uizze.com --skill anti-ui-slop

Finish

When the environment supports it, render and inspect the result once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible or inert controls, missing required states, and unintentional responsive behavior. Run the project's normal checks and keep the handoff concise.

Limitations

  • This workflow does not replace product validation, accessibility review, security review, or project-specific tests.
  • UIZZE evidence is optional and may legitimately return no useful result.
  • A reference is not permission to copy another product's identity or assets.

Related Skills

View on GitHub
GitHub Stars49.7k
CategoryDesign
Updated3d ago
Forks7.2k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions