Build a website that does not look AI-made
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and build a website that does not look AI-made.
LLMPrompt
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.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/build-a-website-without-ai-design-cliches - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "build-a-website-without-ai-design-cliches",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}