One Prompt Website — Your Access Page

The whole thing. One prompt, one AI, one live website.

Whimzy Vibez · SKU WZ-DIGITAL-OPW-001 · v1.0

Pick your path

There are two ways to run this. Both end with a live website today.

The Fast Path — Steps 1–4 below. Answer six plain questions, paste one prompt, get a finished site. About 30 minutes. This is most people.

The Full Path — run The Page Prompt first (it's Part 2, at the bottom of this page), then come back here to Step 2. The Page Prompt does something different and harder: it picks your single best offer, defends the choice, and writes the entire page in your voice — your sentence rhythm, your story, your price logic. Then the prompt below turns that writing into a real hosted site. About 90 minutes, and the result is meaningfully better copy.

If you're not sure: do the Fast Path today, get something live, run the Full Path this weekend. A live imperfect site beats a perfect one you never shipped.

Before you start: read this part, it's 60 seconds

You need three things. All three are free. None of them require a credit card.

1. A Claude account — claude.ai. Free tier works.
2. A Netlify account — netlify.com. This is where your site will live. Free forever for a site this size.
3. A folder on your computer. Name it whatever your business is called. That's it. That's the whole setup.

You do not need: a developer, a domain (yet), a hosting company that calls you, WordPress, a template, a course, or a single line of code.

The economy restructured. You're about to have a website by dinner.

Step 1 — Fill in the six blanks

Below is the prompt. It has six blanks marked [LIKE THIS]. Fill them in with your own words — plain sentences, no marketing voice, no trying to sound professional. Claude translates. That's its job.

Don't overthink this part. Bad answers still produce a good website. Blank answers don't.

Step 2 — The Prompt

Copy everything between the lines. Paste it into Claude. Send it.

Full Path users: run this in the same conversation where you ran The Page Prompt. Then replace answers 1–6 with this single line:

Use the page manuscript and the color/font direction you just wrote for me as the content and design spec. Do not rewrite the copy — build it.

Everything from NOW BUILD IT down still applies exactly as written.

You are an expert web designer and front-end developer. I am not technical
and I do not write code. Your job is to build me a complete, finished
website that I can put online today.

HERE IS MY BUSINESS:

1. What I do, in my own words:
[WRITE 2-3 PLAIN SENTENCES. Example: "I'm a hairstylist in Tucson. I do
color corrections and lived-in blonde. Most of my clients come from
Instagram and I want somewhere to send them to book."]

2. Who my customer is:
[WHO ARE THEY, WHAT DO THEY WANT, WHAT ARE THEY WORRIED ABOUT. Example:
"Women 28-45 who've been burned by a bad dye job and are nervous about
trusting someone new."]

3. What I want someone to DO on the site:
[PICK ONE MAIN THING. Book a call, buy something, email me, join a list,
fill out a form, call me. One. Not five.]

4. My contact info and links:
[EMAIL, PHONE IF YOU WANT IT PUBLIC, INSTAGRAM, BOOKING LINK, ANY OTHER
LINK. Put "none" for anything you don't have.]

5. The feeling I want:
[3-5 WORDS. Example: "calm, expensive, not corporate" or "loud, fun,
a little chaotic" or "warm and trustworthy."]

6. My business name:
[NAME. If you don't have one yet, write "no name yet" and suggest three.]

NOW BUILD IT. FOLLOW THESE RULES EXACTLY:

STRUCTURE
- Produce ONE single file called index.html.
- Put the CSS in a <style> tag in the head and any JavaScript in a
  <script> tag before </body>. Do NOT create separate .css or .js files.
  Do NOT use a framework, a build step, npm, React, or Tailwind CDN.
  Plain HTML and CSS only. This must work by double-clicking the file.
- No external files of any kind except Google Fonts.

SECTIONS, IN THIS ORDER
1. A header with my business name and a single button for the ONE action
   from answer 3.
2. A hero: one headline under 10 words, one sentence under it, that same
   button again.
3. "What I do" — three short blocks. Icon-free. Text only.
4. A section that handles the worry from answer 2 head-on. Name the fear,
   answer it, move on.
5. Three testimonials. Write realistic placeholder ones and wrap each in
   an HTML comment that says <!-- REPLACE WITH A REAL REVIEW -->.
6. An FAQ with 5 questions my actual customer would ask. Write real
   answers based on what I told you.
7. A closing call to action with the button one more time.
8. A footer with my contact info and links from answer 4, and the current
   year.

DESIGN
- Interpret answer 5 into an actual palette. Pick 2 colors plus a neutral
  and use them consistently. No gradients unless the feeling calls for it.
  No stock-template look.
- Use one Google Font for headings and one for body. Load them properly
  with a <link> tag.
- Generous whitespace. Body text at least 17px. Line height at least 1.6.
  Max text width about 65 characters.
- Must look correct on a phone. Use a mobile-first approach with one
  media query at 768px. Test your own markup mentally at 375px wide.
- Buttons must be at least 44px tall and obviously tappable.
- Do not use lorem ipsum anywhere. Every word is real copy written for
  my business.

COPY
- Write all of it in a confident, human voice. Short sentences.
- No "welcome to our website." No "we are passionate about." No
  "in today's fast-paced world." No "solutions."
- Say the specific thing, not the general thing.

TECHNICAL MUSTS
- <title> and <meta name="description"> written for search, using my
  business name and what I actually do.
- Open Graph tags (og:title, og:description, og:type, og:url) so the link
  looks right when shared.
- <meta name="viewport" content="width=device-width, initial-scale=1">
- Semantic HTML: header, nav, main, section, footer. Alt text on any
  image element. Proper heading order, one h1 only.
- If I gave you a booking link or email, wire the buttons to it for real
  (https:// link or mailto:). If I gave you "none", make the button
  scroll to a simple contact form section instead.
- Add a favicon using an inline SVG data URI with my initials. No file.

OUTPUT
- Give me the complete file in ONE code block. Top to bottom, finished,
  nothing left for me to fill in except where you left the REPLACE
  comments.
- Do not explain the code. Do not give me options to choose from. Do not
  ask me follow-up questions. Build it.
- After the code block, give me exactly three bullets: what to change
  first, what to change second, what to ignore.

Step 3 — Save it

1. In Claude's reply, hover the code block and click Copy.
2. Open TextEdit (Mac) or Notepad (Windows).
   Mac only, this matters: TextEdit → Format menu → Make Plain Text. Skip this and the file breaks.
3. Paste.
4. Save it into your folder as exactly index.html
   Not index.html.txt. Not Index.html. Not website.html. index.html.
5. Double-click the file. Your website opens in your browser.

That's a website. It's on your computer. Now let's put it on the internet.

Step 4 — Live in 90 seconds

This is the part everyone told you was hard. It is not hard. There is no server, no cPanel, no FTP, nobody to call.

1. Go to app.netlify.com/drop
2. Drag your folder onto the page. The whole folder — not the file.
3. Wait about ten seconds.

You now have a live website at a URL like random-words-12345.netlify.app. It is real. It works on every phone in the world. Send it to someone right now.

Make the URL less ugly: Sign up (free), then Site configuration → Change site name. Now it's yourbusiness.netlify.app.

Want a real domain? Buy one at Namecheap or Porkbun — about $12/year. Then in Netlify: Domain management → Add a domain and follow the two steps it gives you. Netlify handles the security certificate automatically. You will never touch a nameserver by hand.

You can skip the domain entirely and launch today. .netlify.app takes payments and books clients exactly as well.

Step 5 — Changing things later

You do not edit code. You go back to the same Claude conversation and ask in English:

"Make the hero headline say [new thing]."

"The blue is too cold. Make it warmer and a little darker."

"Add a section between the FAQ and the footer about my new package. It's $400 and it includes three sessions."

"This looks cramped on my phone. Fix the spacing."

Claude gives you the full updated file. Copy, paste, save over index.html, drag the folder to Netlify Drop again. Live in ten seconds.

Keep that Claude conversation. It is your website's memory. Starting a new one means re-explaining everything.

When something goes wrong

The upgrade path, honestly

This gets you a genuinely good one-page site. That covers most businesses for a long time.

When you outgrow it, you'll want: a second page, a blog, or a real shopping cart. Ask Claude for a second file (about.html) and link them — same process, no new skills. Past that, you're looking at Shopify or a CMS, and by then you'll know exactly what you need and why, which is a much better place to hire from than where you started this morning.

You didn't learn to code today. You learned that you never needed to.

Your license

Yours to use for your own business and your clients' businesses. Build as many sites as you want. Don't resell or redistribute the prompt itself as a product.

Questions: hello@whimzyvibez.com

Calm isn't a feeling. It's a system. — Elle Purcell

Whimzy Vibez · whimzyvibez.com

Part 2 — The Page Prompt (the Full Path)

This is the second half of what you bought, and it is the harder, better one. It does not build anything. It decides what your page should say — it picks your single best offer, defends that choice back to you, and writes the whole page in your own voice.

How to run it: copy everything in the box below and paste it into a fresh Claude conversation, then answer the INTAKE questions when it asks. When it hands you the finished page manuscript, scroll back up to Step 2 and run the Build Prompt in that same conversation to turn the writing into a live site.

Already shipped something today on the Fast Path? Good. Do this one at the weekend and replace your copy. A live imperfect site beats a perfect one you never shipped.

## OPENING

You are my page-writer. I'm going to give you my voice, my offer, and who I serve. Your job is to return one complete, build-ready landing-page manuscript in my voice — strategically clear and plainly written. Study everything below, do all the silent thinking the instructions ask for, run STAGE 0 in the open, then deliver the page in one pass.

---

## TOP OF PROMPT

**This prompt builds ONE landing page for ONE offer: my single best offer.**

That means the highest-value, highest-commitment thing I sell to one specific buyer — not a menu, not my whole business, not two things that happen to both be mine. One offer. One buyer. One page.

If anywhere below I've given you more than one offer, your first job before writing a single word is to **pick my best one** and frame it — see STAGE 0. Every other offer is context only: it exists so you know what to leave out.

---

## STAGE 0 — SELECT MY BEST OFFER AND FRAME IT (visible, before the page)

Before the manuscript, do this in the open — this is the one thing you're allowed to output above the template, because its job is to make my offer strategically clear to **me**, not just to build the page.

**1. Lay out the field.** In one line each, list every offer you found across my intake and my corpus. For each, note its buyer and its rough price/commitment.

**2. Select one — and defend it in 2–3 sentences.** Pick my single best offer by these criteria, in order:

- **Buyer match:** does it serve the person in WHO I SERVE? An offer for a different buyer can't win, no matter how big.

- **Price & commitment:** highest-value, deepest-commitment offer wins. Sell the thing that changes my business, not the impulse buy.

- **Strategic leverage:** which offer, if it lands, makes the rest of my work inevitable? Which one is the door everything else walks through?

- **Legibility:** which one can I make a stranger understand in one sentence? If an offer can't be made clear, it isn't ready to be the page.

If two offers serve different buyers, they can never share a page — pick one, say so, set the other aside as context.

**3. Write THE OFFER BRIEF — the strategic frame.** Eight lines, plain language. This is the clarity artifact; the page is built from it.

- **The offer:** [name]

- **The buyer:** one real person — role, situation, what they already have, what's at stake

- **The expensive problem:** what it costs them, in real terms, to not solve this

- **The promise:** the transformation in one line — where they are after

- **The mechanism:** why this works and why it's mine — the unfair advantage, concretely

- **The price + its logic:** the number, and the one reason it's rational (anchor to the cost of the problem, not to my hours)

- **The position:** the single sentence that makes this offer inevitable — the line a buyer would repeat to someone else

- **Not for / not this:** who it's wrong for and what it is not — the boundary that makes the rest sharp

**4. Honesty rule.** Build the brief only from what I gave you. Where you're inferring rather than quoting my material, mark it **(inferred)**. If price or mechanism is genuinely absent, write **[NEEDS YOUR CONFIRM]** rather than inventing a number or a method.

**5. Then proceed.** If the brief holds together, write the full page to it immediately in the same reply. If — and only if — selection is blocked because two offers serve different buyers and I haven't said which, or there's no price anywhere to anchor to, present the brief as your recommended draft, name the one gap, and ask the single question (see QUESTIONS). Otherwise: brief, then manuscript, one reply.

---

## INTAKE

**[1] MY CORPUS**

(Paste the way I actually write: my MY VOICE ON THE PAGE section, real lines from my site and interviews, anything in my own register. This is what you study for rhythm, recurring words, archetype, and shadow. The more raw, the better.)

**[2] MY ONE OFFER — this page sells exactly one thing.**

- **Name of the offer:**

- **Who buys it** (one buyer — their role, their situation, what they already have, what's at stake for them):

- **Price** (a number or a range — required):

- **Mechanism** (what literally happens / how it works, step by step):

- **Outcome + by when** (what they walk away with, and the timeframe):

**[3] MY OTHER OFFERS — context only. DO NOT sell these on this page.**

(List them so you know my full landscape and keep them out. For each: who it's for and roughly what it costs, so you can see at a glance it serves a **different** buyer than [2].)

**[4] WHO I SERVE** (the buyer of the offer in [2], stated once — must match [2]'s buyer exactly):

---

## HOW TO WRITE IT (do all of this silently — none of it appears in your output, except STAGE 0)

Before writing, study my corpus for: my sentence rhythm and the words I lean on (write the whole page in that fingerprint, cleaned of static); my archetype AND the shadow I hide that actually makes people trust me (the shadow goes in MY STORY — that's where trust lives); and the one sentence my whole mission keeps almost saying (that becomes the HERO — if I've never quite said it, finish it for me). Derive my colors and fonts from the way I write, not from industry clichés: if my words are velvet, the page is velvet; if my words are lightning, the page is lightning.

**One offer. No blending. This is the rule the whole page hangs on.**

This page sells exactly the offer in [2] and nothing else. If my corpus or my other offers tempt you to add a second product, a store link, a tripwire, an upsell, or a "you can also…" — don't. An offer from [3] may be named **once, in passing,** only if it removes an objection. It never gets its own section, price, or button. Two offers on one page don't add up — they halve it.

**Resolve the offer before writing — do not average across mine.**

- If [2] is filled, sell that and only that.

- If [2] is blank but my corpus contains several offers, do not combine them and do not default to the cheapest or most recent — run STAGE 0 and pick by the criteria there.

- If two offers serve different buyers, they can never share a page.

- Name your choice in STAGE 0, then write.

**Match the buyer to the offer, out loud to yourself.** Before THE RECOGNITION, check: does the ache I'm about to name belong to the person who actually buys [2]? A CIO's ache and a solo founder's ache are not the same sentence. If WHO I SERVE and the offer's real buyer don't line up, trust the offer's real buyer and write to them.

**THE REGISTER — this governs every line you write:**

Write like a sharp operator who happens to have a soul — not a guru, not a tech bro. The spine of this page is business reality: who I help, what changes for them, how it works step by step, what it costs, what they walk away with, and by when. Concrete nouns carry the page: clients, revenue, hours, weeks, deliverables, calendar, results.

- **The 1-in-10 rule:** at most one line in ten may carry spiritual or soulful language, and only if my own corpus speaks that way. The soul is seasoning. It is never the spine.

- **Banned, guru side** (unless these exact words recur in my corpus — then once, maximum): vibration, alignment, abundance, divine timing, sacred container, soul-led, calling it in, the universe, energetics, activation, frequency, expansion, holding space.

- **Banned, tech-bro side, no exceptions:** crush it, 10x, scale to the moon, disrupt, unlock, game-changer, level up, no-brainer, skyrocket, secret weapon, value bombs, and any manufactured scarcity or countdown urgency.

- **The eye-roll test:** every sentence must survive a smart, busy woman with a real budget reading it. If she'd roll her eyes — too mystical or too hype — cut it and state the plain fact underneath it instead.

Writing standards, applied silently to every line:

- Every big claim must land in the material: attach a concrete deliverable, a number, a mechanism, or an outcome with a timeframe. Depth, stated plainly — that's what sells.

- No permission-asking CTAs ("feel free to," "if you'd like," "no pressure"). No price apology or over-justifying. No hedging ("I think," "hopefully," "just"). The price is stated like a fact.

- Speak as me, in first person, to one reader.

**Questions: your default is ZERO — with one narrow exception.**

If [2] (my one offer) is empty, OR I've handed you several offers without saying which one this page sells, OR the buyer in WHO I SERVE plainly doesn't match the offer you'd pick — ask **one** short message: name the offers you see, name the buyer mismatch if there is one, and ask which single offer (and its price, if missing) this page sells. Then your very next reply is the complete brief + manuscript. That is the **only** thing you may ask about. A vague corpus is never a reason to ask about anything else — infer boldly on everything but the choice of offer.

---

## YOUR OUTPUT TEMPLATE

Fill this in completely. Output nothing outside this template **except THE OFFER BRIEF from STAGE 0, which prints once, above the DESIGN CARD.** Use [SQUARE BRACKETS] only for things I alone can supply (photos, testimonial names, links).

=== THE OFFER BRIEF ===

(STAGE 0, eight lines, as specified above. Then the page.)

=== DESIGN CARD ===

(6 lines maximum: 3 hex color codes with one-word names, 2 Google Fonts — one headline, one body — and one line naming the feeling a visitor gets in the first three seconds)

=== THE PAGE ===

[HERO]

(15–40 words: my one big sentence as the headline, a one-line promise under it, and the button text. A visitor knows in three seconds who this is for.)

[THE RECOGNITION]

(60–100 words naming my reader's ache so precisely she feels seen before she's sold to. The hand on her shoulder.)

[MY STORY]

(200–300 words. Story, not résumé. Include the shadow. End by turning the lens to her so she knows she's in the right place.)

[THE OFFER]

(250–400 words, ONE offer only — the offer in [2]. Structure: the turn (why the obvious move is the wrong one) → what actually happens, step by step, in plain language → deliverables with specifics → the price stated as a flat fact → terms → the button text. This is the business core of the page. Write it like a clear deal between two adults, because it is one. No second offer. No store detour. One door.)

[PROOF]

(Real testimonials or results pulled from my corpus, formatted for the page. If proof is thin: 2–3 [PLACEHOLDER] slots with a one-line note on what to drop in. One true sentence from one real person beats ten invented ones — never invent quotes.)

[THE QUIET FAQ]

(Four questions, answered honestly in roughly 40 words each — including one that names who this is NOT for. Objections answered as discernment; she is allowed to see clearly.)

[CONTACT + CLOSE]

(50–80 words: the zero-friction way to reach me, exactly what happens after she does, and one final restatement of the offer with the button text. The last thing she reads is a door held open, not a pitch.)

[FOOTER]

(1–3 lines: my name/brand, a privacy note, social links as [PLACEHOLDERS].)

=== THE THREE SENTENCES ===

(Three sentences of brand language for me alone — for the day I forget who built this and why. Same grounded register as the page: earned, plain, unshakable. Not in mourning for those who sacrificed so I could stand here, but in praise of them, because the building is the homage. Let me read them and stand up straighter.)

Begin your reply with the line "=== THE OFFER BRIEF ===", complete STAGE 0, then continue straight into "=== DESIGN CARD ===" and write until the template is full. Write the manuscript now.