Score
9.1
/ 10
Installs
528K
Repo Stars
38.4K
Last Updated
0d ago
Quality Ratio
100%
Description
Verified
Language
JavaScript
Summary
The Anti Ui Slop agent skill guides AI agents to avoid inconsistencies and haphazard elements in user interfaces, promoting cleaner and more structured UI outputs. This agent skill is particularly beneficial for frontend developers and UI/UX designers who prioritize maintainable, consistent, and high-quality user experiences. It is a reasonably adopted skill within the registry. While specific rules and patterns are not detailed, this agent skill likely directs the AI to prioritize adherence to design systems, consistent component usage, and structured styling to prevent visual clutter and inconsistent user flows. It aims to prevent the generation of misaligned elements, arbitrary spacing, or disparate UI patterns that often contribute to a perceived lack of polish. Due to the lack of specific SKILL.md content, the precise scope and implementation details of this agent skill are limited.
Skill Definition
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.
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.