Copy-paste Cursor prompts for landing pages, dashboards, pricing, login, onboarding and AI apps, written for Cursor Agent with @ file references, plus a prompt that writes your Cursor design rules.
A full landing page for a SaaS product: hero, logos, features, how it works, pricing, FAQ and a closing call to action.
Template: Pixel SaaS landing page
“Build a landing page for [product name], a SaaS product that helps [audience] [main outcome]…”
A hero section that explains the product in one line and gets the click, with a product visual and social proof.
Template: Dark gradient hero
“Build the hero section for [product name], which helps [audience] [main outcome]…”
A pricing page with three plans, a monthly and yearly toggle, a comparison table and a pricing FAQ.
Template: Three tier pricing section
“Build a pricing page for [product name]…”
An app dashboard with sidebar navigation, key metrics, a chart, a recent activity table and empty states.
Template: SaaS analytics dashboard
“Build the main dashboard for [product name], used by [user type] to [main job]…”
Sign in, sign up and forgot password screens with social login, clear errors and a branded side panel.
Template: Login page
“Build the sign in, sign up and forgot password pages for [product name]…”
A short onboarding flow: welcome, role, goals and a first-step checklist that gets new users to value fast.
Template: Onboarding role selection
“Build the onboarding flow new users see after sign up for [product name]…”
A ChatGPT-style AI chat app: conversation list, streaming answers, suggested prompts and a clean message box.
Template: AI chat interface
“Build an AI chat app called [product name] that helps [audience] with [topic]…”
A landing page for a mobile app with phone mockups, feature screens, reviews and App Store and Google Play buttons.
Template: Mobile app landing page
“Build a landing page for [app name], a mobile app that helps [audience] [main outcome]…”
A personal portfolio site with selected work, case study pages, an about section and a contact form.
Template: Designer portfolio website
“Build a portfolio website for [name], a [role] who wants [type of client or job]…”
Account, billing, team and notification settings pages with a settings sidebar and clear save states.
Template: Account settings page
“Build the settings area for [product name]…”
A pre-launch waitlist page that collects emails, shows the product and gives people a reason to share.
Template: Waitlist landing page
“Build a pre-launch waitlist page for [product name], launching [launch date]…”
A short launch video built in code: hook, product name, three feature scenes and a closing line, exported as MP4.
Template: App launch video
“Adapt the launch video template for [product name], which helps [audience] [main outcome]…”
Redesign an existing vibe-coded site or app to match a professional template, without breaking content or routes.
Template: AI chatbot landing page
“Redesign this [site or app] so it looks professional, using the template as the new design…”
A .cursor/rules file that makes Cursor follow your design template, colours and spacing in every chat and Agent run.
“Create the design rules file at .cursor/rules/design.mdc for this project, so every future change follows the same design…”
Every Cursor prompt above shows its opening line for free. The full prompts, and the templates they are written for, come with a BrowserMoon licence.
Get a licenceCursor writes good code, but its UI drifts unless you pin it to a design. These Cursor prompts reference a BrowserMoon template with @, list every section, and come with a Cursor rules file for design, so Agent builds pages that match instead of inventing new styles each time.
Choose the Cursor prompt for the page you are building, from a SaaS landing page to a login screen or an AI chat app.
Each prompt is written to go with the template shown on its card. Copy that template, or any template from the Cursor templates page.
Follow the design in @design/template.html. Match its fonts, spacing, colours, corner radius and components exactly, and reuse existing components before creating new ones.
Replace the parts in brackets, like [product name] and [audience], with your own details. The prompt ends with: “Work in Agent mode. Make the changes, then list every file you touched.”
Start with the Cursor rules prompt so Agent always follows your design, then use the landing page or dashboard prompt with the template referenced by @. With rules in place, every prompt on this page produces pages that look like one product.
Cursor Agent writes and edits code across your project very well, but it picks styles the way any model does: from whatever is in context. In a new project that means defaults; in an old one it copies the inconsistencies already there.
These prompts give Agent a design to work from. They reference the template file with @, list the sections in order and tell Agent to reuse your components, so Cursor builds UI that matches a real design instead of guessing.
Each prompt on this page is built from the same five parts. The page-specific part changes per prompt; the rest is written for how Cursor works.
Save the template in your project and mention it with @ in the prompt. Cursor then reads the real file instead of guessing.
Put your design rules in .cursor/rules so Cursor applies them to every chat and Agent run in the project.
Tell Cursor to reuse your existing buttons, cards and inputs. Otherwise it creates new versions that look slightly different.
Read the diff before you accept. Reject any change to files you did not ask about.
Without .cursor/rules, each Agent chat starts with no idea of your design. Write the rules once.
Give Agent the template and the files it must change. Extra context makes the result worse, not better.
Ask mode explains; Agent mode edits. Use Agent for these prompts.
Review diffs before accepting. A small style change can touch shared components.
Cursor is the editor of choice for many developers who build with AI every day. These Cursor prompts are for developers who use Agent to build features and want the UI to look as good as the code, without opening Figma.
A prompt says what to build; a template shows Cursor what it should look like. These templates also fit the prompts above.
One that references a design file with @, lists the sections to build, and tells Cursor to reuse existing components. Add a design rules file so the style holds across every chat.
Instructions saved in your project, in .cursor/rules, that Cursor applies to every request. A design rule keeps colours, spacing and components consistent.
Yes. They are written for Agent mode, which can create and edit several files at once.
Yes. Reference the template with @ and ask Cursor to split it into components in your framework. The redesign prompt does this for a whole page.
Yes. They are written for Agent mode, which replaced Composer, and work in any Cursor chat that can edit files.
Save it in your project, for example design/template.html, and type @ followed by the file name in your prompt.
Prompts for other AI coding tools
