Every AI coding agent โ€” Cursor, Codex, Claude Code, whatever you're running โ€” is trained on millions of websites. Most of those sites are average at best. So when you prompt 'build me a landing page,' the model doesn't think, it regurgitates the statistical mean: a centered hero section, a purple gradient background, and three equal columns for features. That's not design, that's slop.

The Problem With Average

The issue isn't just aesthetic boredom โ€” it's that this generic output is actively harmful to product differentiation. If every startup ships the same AI-generated landing page, users can't tell one tool from another. And developers waste time rewriting boilerplate instead of focusing on real UX decisions. The problem compounds because these models are trained on their own outputs over time, creating a feedback loop of mediocrity.

A Config File as a Counterweight

Developer Yu (DEV.to handle yu-369) built a skill.md file to break that cycle. It's essentially a set of instructions you drop into your project that tells the coding agent what not to do: no purple gradients, no stock hero layouts, no generic three-column feature grids. Instead, it nudges the model toward design-system-specific tokens and brand constraints โ€” or at least forces the human to define them before letting the AI run wild. The beauty of this approach is that it works across agents. Since skill.md is just a plain-text file in your repo, any tool that respects project context can pick it up. That means you're not locked into one vendor's prompt-hacking workaround โ€” you're encoding taste as infrastructure, which is exactly the kind of hack I respect.

Key Takeaways

  • AI coding agents default to average designs because they're trained on average sites; prompting alone won't fix that.
  • A skill.md file gives developers a portable way to inject design constraints into any agent's context window.
  • This is an early sign of the community building guardrails for vibe coding โ€” expect more config-file-driven control as agents get dumber with scale.

The Bottom Line

If you're letting an AI touch your UI, you need a skill.md or equivalent yesterday. Otherwise you're just shipping the same purple gradient everyone else is shipping โ€” and that's not innovation, it's conformity dressed up as automation.