블로그 > Guides
How do I make my website not look AI-generated? Prompts you can paste
Paste-ready prompts and a rules block for Cursor, Claude, v0, Lovable, and Bolt so a site stops looking like the default AI landing page.
- 글쓴이
- Unslop UI
- 게시
- 2026년 11월 20일
- 수정
- 2026년 11월 20일
- 읽는 시간
- 5분 읽기
A website stops looking AI-generated when the prompt names a visual direction, a few design tokens, and the patterns to refuse, instead of asking for a modern landing page. The paste-ready prompts below do that for Cursor, Claude, v0, Lovable, and Bolt. The rules page is the full ruleset; this post is the short version you can drop into a chat.
This is the toolkit, not the explanation of why the sameness happens. For that, read "Why Do All v0, Lovable and Cursor Websites Look Exactly the Same? (And How to Make Yours Not)".
What should I put in a prompt so the page does not look generated?
A useful prompt has five lines, in this order.
- Direction. One of editorial, Swiss-inspired, industrial, or analog. Do not ask for all four.
- Tokens. Background, text, radius, and section spacing. Set the canvas to
#F7F5F0and the text to#252722. That pair is about 13.85:1, which is fine for body text. Do not use a warm accent such as#B46F4Dfor small text on that canvas (about 3.6:1). - Type. A display face for headings and a text face for body. Instrument Serif or Newsreader for headings, with DM Sans or Inter for body, is a pairing people reach for when they want to leave Inter-everywhere.
- Hero. Left-aligned headline, one action, and a real product screenshot. Not a centered headline, a badge pill, and a glow.
- Refuse list. The patterns in the checklist below.
If any line is missing, the tool fills it with the average SaaS page.
Which patterns should the prompt forbid?
Keep this list short. It is the part models skip when the rest of the prompt is vague.
- No purple-to-blue gradient and no colored glow behind the hero.
- No badge pill above the headline.
- No three identical cards with Lucide icons as the first proof of the product.
- No
py-24on every section. That utility is 6rem, 96px at a 16px root. Varypy-12,py-16, andpy-20. - No single
--radius: 0.5rem(8px) on buttons, cards, and images alike, unless that radius is a choice. - No Inter or Geist as the only typeface on the page.
- No headline that could sit on another company's site. Name the action: what the visitor pastes, and what they get back.
For the longer list of tells, see "What makes a website look AI-generated?". For font pairings and hex values, see "What Are the Best Fonts and Colors to Avoid the AI Look on a SaaS Landing Page?".
What prompt can I paste into Cursor, Claude, v0, Lovable, or Bolt?
Use this as the first message, then add two sentences about your real product. The same text works in those tools because it is a brief, not a proprietary file.
Build a marketing page in an editorial direction. Canvas
#F7F5F0, text#252722, display headings in Newsreader, body in Inter. Radius0rem. Hero is left-aligned: one specific headline, one short paragraph, one primary action, and a real product screenshot on the right. Section padding alternatespy-12,py-16, andpy-20. Do not use a purple or blue gradient, a glow, a badge pill, three matching icon cards, or Inter as the only font. Write the headline so it names what the visitor does and what they receive. Do not invent features, testimonials, or prices.
Then a second message for a page that already exists:
Restyle the current page to the tokens above. Change the hero composition first. Keep the real product name, the real features, and the real screenshot. Do not add sections. Do not add a gradient to make it feel more finished.
v0 and Lovable often start from components. Say "implement these tokens in the existing Tailwind or shadcn setup" so the tool edits variables instead of pasting a second theme on top. Bolt and Claude Code follow the same brief if you paste it before the first file is written.
What should a rules file say?
A rules file is the same brief, kept where the tool reads it on every edit. In Cursor that is often .cursorrules or a project rule. Other tools have their own rules slot. The point is identical: the avoid list survives the next "make it nicer" message.
Visual direction: editorial. One direction only.
Canvas #F7F5F0. Text #252722. Radius 0.
Headings: Newsreader. Body: Inter.
Hero: left aligned, one action, real product screenshot. No badge pill.
Refuse: purple-blue gradients, glows, py-24 on every section,
three identical Lucide cards, Inter or Geist as the only typeface,
headlines that could fit another product.
Do not invent customers, quotes, or prices.
That block is a starter. The full ruleset, including how the checks are grouped, is on the rules page. If your product is a dense developer tool, swap the editorial line for industrial and keep the refuse list.
Satoshi is sometimes suggested as a body face. It is not a Google Font; it is distributed by Fontshare. Do not tell the tool it is on Google Fonts.
How do I check that the prompt actually stuck?
Compare the built page to the refuse list, one row at a time.
| If you still see this | The prompt did not stick |
|---|---|
| Centered headline plus a pill | The hero line was ignored |
| Purple or blue glow | The refuse list was ignored |
| Three equal icon cards | The product proof is still a template |
| One sans on every line | The type pairing was dropped |
The same py-24 on every band | Spacing was left as the default |
A free scan on Unslop UI takes a URL or an uploaded screenshot, then lists the tells it finds, with a score and what to fix first. Three checks a day need no sign-up. It does not prove a model built the site. For how that check differs from text detectors and landing-page graders, see "Is There a Tool to Check If My Website Looks AI Generated?".
Paste the next prompt only after that list is shorter than the last one.
FAQ
What prompt makes a website not look AI?
Tell the tool the visual direction, the background and text colors, the display and body fonts, the hero layout, and a short list of patterns to refuse. A prompt that only says modern or professional leaves those choices to the usual defaults.
Can I paste the same rules into Cursor, v0, Lovable, and Bolt?
Yes. The rules are design constraints, not a file format that belongs to one product. Put them in the prompt, in a project rules file, or in both, then check that the generated page actually followed them.
What should a .cursorrules file say about the AI look?
It should name tokens, fonts, and layouts to keep, and name the patterns to refuse, such as a purple glow, a badge pill over a centered headline, and three identical icon cards. The full ruleset for this site lives on the rules page.
How do I know the prompt worked?
Compare the built page to the refuse list, one row at a time. If the glow, the pill, or the three equal cards are still there, the prompt did not stick. A free check of the URL or an uploaded screenshot lists the patterns that remain.