About anti-ui-slop
anti-ui-slop is a workflow skill for designing, implementing, reviewing, or refining web and iOS interfaces. It uses product context and existing design systems to guide specific layouts and interface states; MCP references are optional.
Key features
- 01Uses product context and design systems
- 02Plans interface hierarchy and controls
- 03Covers loading and other UI states
- 04Renders and checks output when supported
Use cases
- 01Refining a generic first draft
- 02Redesigning a web or iOS screen
- 03Reviewing responsive layouts and interactions
MCP support
The workflow does not require MCP. An optional separate UIZZE MCP provides tools to search screen references and visual materials when an authenticated connection is available.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/anti-ui-slopin Claude Code to confirm it loaded.
Details
From the project READMEStop Making UI Slop
Build product-specific interfaces with UIZZE's free anti-ui-slop workflow. Use the product brief, existing components, and design system to make the screen's hierarchy, content, controls, and states intentional.
When to Use This Skill
Use it to design, implement, redesign, critique, or finish a web or iOS interface, especially when a first draft feels generic or omits important states.
How to Use
- Read the target screen, product context, and existing design system. Identify the primary user, action, content, and constraints.
- Reuse the project's components, tokens, typography, and interaction conventions. For a substantial redesign, write a short design contract; keep a small fix small.
- Use product-specific labels and real data requirements. Do not invent metrics, activity, testimonials, or controls to fill a layout.
- Implement the required loading, empty, error, success, disabled, and permission states. Make the primary action and recovery paths clear.
- When the environment supports it, render the result and fix observable clipping, overlap, inert interactions, and responsive problems. Run the project's relevant checks and summarize what changed.
The workflow works without an account, token, script, or MCP connection. Continue from repository evidence when external references are unavailable.
Example
Use anti-ui-slop on our billing settings page. Make the current plan,
payment method, and invoice history easy to scan. Reuse our components
and tokens. Cover no invoices, payment failure, and read-only access.
Inspect desktop and mobile output and fix visible breakage.
For a focused review, identify the three most useful changes first and implement them within the requested scope.
Optional UIZZE References
The separate paid UIZZE MCP offers focused reference search across 800,000+ real web and iOS screens. It exposes exactly two tools:
find_ui_referencesfinds or inspects up to three full-screen references.find_ui_materialsfinds up to three hosted fonts, icons, animated icons, or explicitly requested packs.
Use those tools only when the host provides an authenticated connection and a concrete visual question would benefit from evidence. If retrieval returns nothing, continue from the project. Never claim a tool result that the host did not return.
Adapt useful decisions about hierarchy, density, controls, and states to the product's own design system. Preserve its identity and content.
Canonical Package and More Examples
This catalog entry is a standalone workflow. Install the complete current skill, including its focused playbooks, with:
npx skills add https://uizze.com --skill anti-ui-slop