Blog

Why agent design looks like slop

· Design Skills

Phone and laptop showing the same generic travel app — the sameness that makes agent design look like slop

Ask an agent for a logo and you usually get four recolors of one owl. Ask for a checkout and you get a happy path, a stock sans, and a primary button that says “Submit.” Ask for a deck and you get a thank-you slide.

That is not a model problem first. It is a brief problem.

The agent is not a designer. It is a very fast intern.

A good intern gets a brief: what to make, what not to invent, what files come back, what “done” means. A dumped prompt is the opposite. “Make it premium. Make it distinctive. Make it on brand.” Distinctive compared to what. On brand for whom. Premium in which century.

Without a contract the model does the statistically safe thing. Inter, a soft gradient, a geometric animal, three benefits, a fake metric. It looks generated because it is generated from the average of every other generated thing.

What slop actually is

Slop is not “AI made this.” Slop is output that cannot be kept:

  • A PNG of a UI instead of frames.
  • A moodboard instead of tokens.
  • Four logos that are one logo.
  • A “brand kit” that is a paragraph and a hex code.
  • A wireframe with no empty state and no error.

If you cannot name the files, you cannot review the work. If you cannot review the work, you cannot ship it. That is the whole loop.

Skills are contracts, not prompts

A design skill is a reviewed brief the agent is allowed to load — whether that host is Figma, Claude, Cursor, or ChatGPT. Inputs listed. Artifacts listed. Taste rules written down so the model does not get to invent a mystery pack and call it identity.

That is why this catalog stays short on purpose. A dump of 200 generic “agent skills” is how you get slop with better file names.

Browse the skills library. If a listing cannot say what comes back, it should not be on the shelf.