audit-ai-design-slop

Provide the artifact such as a screenshot, rendered page, or source code, and the audit inspects decorative stacking, template repetition, typography clutter, motion theater, and fake proof. Each finding cites concrete evidence and is prioritized P0 through P3 with a removal or correction recommendation.

An anti-slop design review identifies repeated generated defaults, decorative layers with no useful role, and unverifiable proof elements in an interface. It recommends the smallest removals or corrections that improve clarity while preserving the product's existing visual direction.

No. The audit explicitly avoids prescribing new fonts, palettes, layouts, or art direction unless the user explicitly asks. It defaults to subtraction and only suggests replacements that inherit the product's existing visual language.

Yes. Established UI failures flagged include low contrast, unreadable content, missing keyboard focus, and motion that ignores reduced-motion preferences. References include WCAG 2.2 quick reference and contrast minimum guidelines.

The audit does not guess whether AI made the design, assign numeric slop scores, or reject techniques like gradients or dark themes in isolation. Anything outside the visible or provided evidence is marked as unknown rather than speculated upon.