antislop-ui

Audit the interface against a catalog of known AI-default patterns like blue-purple gradients, uniform feature cards, and glow effects. Replace defaults with choices derived from a written brand identity, and cap decorative treatments like glass, glow, and shadow to one or two elements.

Common tells include blue-to-purple gradients, glassmorphism on every surface, bento grid layouts, fake terminal windows, Lucide-style icons everywhere, emoji in headings, three-tier pricing with a highlighted middle card, and stat cards with invented numbers and deltas.

An empty state should explain why it is empty and give the one action that fills it, a loading state should say what is loading, and an error state should name the failure and next step. Generic 'No data available' messages with illustrations fail this standard.

Yes, when the choice serves a documented purpose. A gradient is acceptable as a hierarchy function with a written reason, and dark mode is valid when brand identity, product type, or audience justifies it. The problem is using them as defaults, not using them at all.

This Skill only covers UI and visual concerns, so it does not address backend logic, content writing, or non-visual code quality. It also requires the antislop core file for the governing rules and Delivery Gate, so it is not standalone.