Slightly reducing the sloppiness of AI generated front end

What “AI slop” really is

  • Many argue the problem is “modern web slop,” not AI: inconsistent widgets, flat lifeless pages, overuse of gradients, rounded cards with shadows, huge headings, purple/mauve gradients, and generic SaaS aesthetics.
  • Others say these AI UIs just resemble typical SaaS/Bootstrap-era sites from the last decade.

Style constraints: Qt/GTK/retro vs “average web”

  • Several commenters note that asking for a Qt, GTK, macOS HIG, Win11, or Win9x-style UI often reduces “slop” by imposing a clear visual grammar.
  • One view: Qt works because it has a coherent design system heavily represented in training data, so “Qt app” is a stable concept.
  • Others think the “Qt” result in the article is more like a parody of early 2000s X11/Flash, not true modern Qt/Fusion style.
  • Retro Win98/Win3.x looks get surprising enthusiasm; others find them ugly or dated.

Subjectivity of design quality

  • Multiple people emphasize there’s no simple quantitative measure for “better” design; taste and familiarity dominate.
  • Some find all examples equally bad; others prefer original, HIG, GTK, or Win11 versions.
  • “AI slop” is described as a vibe users have learned to associate with low-effort, generic, or lazy products.

Using LLMs for UI: successes and failures

  • Some report excellent experiences: quickly building decent one-off tools, or near-1:1 reproductions when given screenshots, design boards, or existing HTML/CSS.
  • Others find AI-generated UIs superficially okay but full of inconsistencies, layout bugs, and incoherence on closer inspection, especially on mobile.
  • Effective workflows mentioned:
    • Constrain design to existing systems (Material, HIG, MUI, Tailwind, etc.).
    • Provide component galleries and explicit usage rules.
    • Use images/diffusion to design first, then have LLMs implement.
    • Iterate with concrete directives: fix overflow, alignment, hierarchy.

Meta: AI-specific tooling and skepticism

  • Anthropic’s “frontend-design” and similar skills are polarizing: some call them game-changing; others see brown/orange same-y outputs and marketing fluff.
  • Concern that these “skills” use vague, aspirational prompts (“be distinctive, unexpected”) that may not reliably improve designs.
  • Broader frustration on HN with undisclosed AI-generated content and time wasted on low-effort “AI slop” projects.