AI slop

AI slop entered the builder vocabulary as a reaction to the homogenization of AI output. When everyone uses the same models with similar prompts, the results start looking the same: web designs using Inter or Roboto fonts, landing pages with the same hero section structure, blog posts that hedge every claim identically. The output is technically correct but forgettable.

In coding, AI slop shows up as technically functional code that lacks project-specific conventions, repeats patterns instead of extracting shared logic, and prioritizes passing tests over readability. In UI, it is the default Tailwind aesthetic that ships from every vibe-coded MVP. Design-focused builders have started writing explicit instructions in CLAUDE.md or system prompts to avoid it: 'commit to a bold visual direction before writing a line of code.'

The term is also used in content contexts: AI-generated articles that summarize without adding perspective, social posts that use AI sentence structures, and product copy that sounds templated. The cure is more specific constraints, stronger examples in context, and explicit evaluation criteria. It is essentially a prompt engineering and context engineering problem disguised as a quality problem.