Cursor Website Prompts

Using a PromptSites prompt in Cursor

1. 1

   Paste the design brief into the project context

   Open Composer or chat on the route you will change. Paste the PromptSites prompt as the look you want, then name your stack — App Router, existing UI kit, current tokens.

2. 2

   Tell Cursor what files/components should change

   Point at the page, layout, or component in scope. If the rest of the app should stay put, say so. Explicit paths beat “rebuild the marketing site.”

3. 3

   Refine implementation without losing the chosen composition

   Once hierarchy matches the preview, wire data, routing, and tokens. Do not ask for a new visual direction in the same turn you connect real content.

What can you build with these Cursor prompts?

Jump to an existing PromptSites collection or a live example. No extra doorway pages.

Three designs that hold up as Cursor starting points

Why these previews are useful when the next step is code in a real project, not a blank chat site.

Anthropic Design System

Design System

Anthropic Design System

A full design-system still. Useful in Cursor when you need tokens, type, and component language mapped onto files you already have instead of a one-off landing.

View Anthropic Design System

AuraMail

SaaS

AuraMail

A SaaS marketing home with a clear header, hero, and product argument. A good Cursor start if you are replacing an existing Next.js route and want the layout locked.

View AuraMail

Bento Grid

Background

Bento Grid

One grid surface, not a whole site. Use it when you want Cursor to rewrite a section component without touching the rest of the app.

View Bento Grid

Other builders

Questions

Do these prompts work in Cursor?

Yes, as visual specs for code. Paste them into chat or Composer with the files you want changed. Cursor writes against your repo; it will not replay the PromptSites video frame-for-frame.

Can I customize the generated result?

That is the point. After the first pass matches the preview’s hierarchy, edit components, Tailwind classes, and data hooks yourself. Keep the PromptSites prompt as the look, not as a lock on every file.

Should I use the full prompt or one section at a time?

Inside an existing app, one page or one section is usually cleaner. Full-site prompts are fine in an empty marketing repo. This list mixes systems, SaaS homes, and isolated UI so you can match the job.

Can the same prompt work in other builders?

The PromptSites page is builder-agnostic. Cursor is the better stop when you already have a codebase. Lovable and Bolt are better for a first-pass site from a blank project. v0 is better for a single block.

What should I change after the first generation?

Match tokens, fonts, and spacing to the rest of the repo before adding features. Then hook real data. Mixing PromptSites colors with leftover theme defaults is what makes the page look generic.