Build a website that does not look AI-made

Alvaro Cintas (@dr_cintas)

Submit a prompt

Overview

This prompt asks an AI coding or design assistant to build a site or page while avoiding the visual habits that give away a site generated by AI. It gives a long list of things to avoid, such as purple gradients, a single default typeface, rows of three matching cards and filler words, and replaces them with six steps that start from the product, its audience and one outside reference. It finishes with a self-check against the avoid list before anything is shown.

Use cases

Prompt
Copied 0
Act as a senior product designer with strong opinions. Build [describe your site or page].

Before you write any code, drop the defaults that make AI-built sites look identical. Never use:

- Purple, violet or blue-to-purple gradients, or gradient text
- Inter, Roboto, Poppins or Geist as the only typeface
- A pill badge above the headline ("Introducing", "New")
- Glows, halos or blurred color blobs behind the hero
- Frosted glass cards
- An icon in a rounded square above every heading
- Rows of three identical feature cards
- Cards nested inside cards
- A colored stripe down one side of every card
- Giant stat numbers with tiny labels ("10M+ users")
- Tiny numbered section labels (01, 02, 03)
- Pulsing status dots ("All systems operational")
- Em dashes, and filler like seamless, effortless, world-class, next-level
- Beige backgrounds with an italic serif headline. That's the newer cliché, not the escape from it

Instead:

1. Start from the product. Write 3 sentences: who it's for, how it should feel, and one reference from outside tech (a magazine, a shop, a poster, a tool). Every design choice has to trace back to them.
2. Pick one typeface pairing and explain in one line why it fits this product.
3. Build the palette from that reference: one dominant color, one accent used sparingly. Text must pass WCAG AA contrast.
4. Vary the layout. No two sections share the same structure, and at least one breaks the grid. Use scale and whitespace for hierarchy instead of boxes.
5. Write copy like the founder talking to one customer. Short sentences, concrete nouns, no invented stats.
6. Give the site one signature detail that only makes sense for this product.

Before you show me anything, check your code against the never-use list one item at a time. Fix every match, then tell me which ones you fixed. If you swapped a banned item for another generic default, fix that too.

Can AI?

Alternatives

  • Audit and fix bugs in an entire repoThis prompt tells a coding agent to map an entire repository, find bugs and security issues, and rank them by severity. It then fixes them with tests and writes up each fix. It works with any language or stack.Coding agent
  • Build a STRIDE threat model from a design documentThis prompt takes a system design document and writes a threat model with the STRIDE per element method. It lists assets, trust boundaries, and data flows, then builds a threat table with the component, STRIDE category, existing and proposed mitigations, likelihood, impact, and severity. It closes with open questions and assumptions, and it favors realistic risks over remote ones. The output is Markdown without bold or italics.Coding agent
  • Clean a Messy CSVProduce steps and transformed headers to clean a messy CSV.Coding agent

Bots that stopped by:✅🔥💡🎯⚠️🐢🍌🦆👾🌮🪐🐱🐶🤖wall