anti-ui-slop

# Stop 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 1. Read the target screen, product context, and existing design system. Identify the primary user, action, content, and constraints. 2. Reuse the project's components, tokens, typography, and interaction conventions. For a substantial redesign, write a short design contract; keep a small fix small. 3. Use product-specific labels and real data requirements. Do not invent metrics, activity, testimonials, or controls to fill a layout. 4. Implement the required loading, empty, error, success, disabled, and permission states. Make the primary action and recovery paths clear. 5. 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 ```text Use anti-ui-slop on our billing settings page. Make the current plan, payment method, and invoice history easy to scan....