Website Prompts for Cursor, Claude Code & v0: One Brief, Three Workflows

The prompt that works best is usually the same brief in every tool. What changes is where you put it: a project instructions file in Cursor or Claude Code, or the first message in a browser builder such as v0, Lovable or Bolt.new. Decide the content and checks once, then adapt the delivery to the tool.

This page is about that adaptation. To write the brief itself, use the free website prompt template and brief builder, which includes a worked example run end to end. For adding depth and motion, see building a 3D animated website section by section.

What this is based on: each tool's own documentation, checked on 28 October 2026. We have not run a controlled comparison of these tools, so this page does not rank them.

What stays the same in every tool?

• The facts: who the page is for, the offer, the one action and its real destination.
• The content you can supply: approved copy, prices, contact details and images you have the rights to use.
• The rules: no invented testimonials or metrics, missing information marked as missing.
• The checks: layout at phone and desktop widths, links, keyboard access and forms.

If the brief is vague, no tool fixes that. If it is specific, each tool below can use it.

How do the three workflows differ?

Because Cursor and Claude Code both read AGENTS.md, one file can hold the standing decisions for a project you open in either tool.

Cursor and Claude Code: split the brief in two

Put decisions that apply to every page in the instructions file, and keep each request short. For the fictional pottery studio used in the template's worked example, the standing file could be:

# Project: Northside Clay Studio (fictional exercise)
- Audience: adults who have never used a pottery wheel.
- Colours: background #FAF6F0, text #222222, accent #B5532F.
- Type: serif headings, sans-serif body. No images unless supplied.
- Use semantic headings, labelled controls and visible focus. Respect reduced motion.
- Never invent testimonials, metrics, discounts or integrations. Mark missing facts as "Missing information".
- Every action needs a real destination. Ask before adding packages or a backend.

Then the request is only the task: “Build the enquiry section: one Email the studio button with a pre-filled subject and body. Then list what you changed and how to test it.”

Smaller requests are easier to review. Read the change before accepting it; an instructions file guides the tool, but it does not guarantee the tool follows every line.

v0, Lovable and Bolt.new: lead with the whole brief

Browser builders start from your first message and show a live preview. Paste the complete brief, including the missing-information rule and the checklist request, rather than a one-line idea you plan to fix later. Then change one thing per message: “increase the spacing between sections on small screens”, not “make it better”.

Check what the builder created beyond the page: hosting, a database, sign-in or paid add-ons. Each service has its own plans and terms; confirm them in its documentation before connecting anything real.

What should you check whichever tool you use?

1. Open the page at phone width and desktop width. Nothing should scroll sideways.
2. Follow every link and button to its destination.
3. Tab through the page with a keyboard and watch the focus outline.
4. Search the page for anything you did not supply: names, numbers, quotes or logos.
5. Run an automated audit such as Lighthouse, then do the manual checks it cannot do.

In the template's worked example, the automated audit scored 100 while a manual review still found an invented schedule and a form that would not work for many visitors. See that example.

Written by PromptPack, the seller of the website prompt pack. The free template and this guide can be used without buying anything.