Claude Prompt Library

30 Claude Prompts That Build Waitlist Pages

30 copy-paste prompts

Fill the brackets. Claude returns one HTML waitlist as an Artifact: tease, email field, optional referral. Dummy submit only. Not a product homepage and not a live ESP.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup · Founder, Techpresso

Last updated September 8, 2026·Hand-curated & tested by the AI Academy team

Tease

5 prompts

One-Line Waitlist

1/30

✨ What it does

Claude builds a one-line waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a tease writer <context> I need one self-contained HTML one-line waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Line: [LINE] - Who it is for: [WHO] </inputs> <task> Build a responsive one-line waitlist with these sections: 1. One line 2. Email 3. Dummy submit 4. No feature grid Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: If you need a paragraph, you are not ready.

Problem Waitlist

2/30

✨ What it does

Claude builds a problem waitlist for [THE PROBLEM] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a problem-first writer <context> I need one self-contained HTML problem waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [THE PROBLEM] - Product: [PRODUCT] - Old way: [OLD WAY] </inputs> <task> Build a responsive problem waitlist with these sections: 1. Name the problem 2. Old way 3. Email 4. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not name six features.

Screenshot Tease

3/30

✨ What it does

Claude builds a screenshot waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a visual tease designer <context> I need one self-contained HTML screenshot waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Shot notes: [SHOT] - Line: [LINE] </inputs> <task> Build a responsive screenshot waitlist with these sections: 1. Big placeholder 2. Line 3. Email 4. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not invent UI in the copy.

Founder Waitlist

4/30

✨ What it does

Claude builds a founder waitlist for [FOUNDER] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a founder-note writer <context> I need one self-contained HTML founder waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [FOUNDER] - Product: [PRODUCT] - Why now: [WHY] </inputs> <task> Build a responsive founder waitlist with these sections: 1. Short note 2. Email 3. Dummy submit 4. Signature Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: First person. No we are thrilled.

Video Tease Waitlist

5/30

✨ What it does

Claude builds a video waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a video-tease designer <context> I need one self-contained HTML video waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Video: [VIDEO OR PLACEHOLDER] </inputs> <task> Build a responsive video waitlist with these sections: 1. Video placeholder 2. Email 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: No fake YouTube embed ID.

Capture

5 prompts

Email Only

6/30

✨ What it does

Claude builds a email waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a capture designer <context> I need one self-contained HTML email waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Privacy one-liner I can say: [PRIVACY] </inputs> <task> Build a responsive email waitlist with these sections: 1. Email 2. Dummy submit 3. Privacy from [PRIVACY] only Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not invent a GDPR novel.

Email Plus Role

7/30

✨ What it does

Claude builds a role waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a qualify-waitlist designer <context> I need one self-contained HTML role waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Roles: [ROLES] </inputs> <task> Build a responsive role waitlist with these sections: 1. Email 2. Role select from [ROLES] 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Only roles you will read.

Invite Code Page

8/30

✨ What it does

Claude builds a invite waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are an invite designer <context> I need one self-contained HTML invite waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - How codes work: [HOW OR VERIFY] </inputs> <task> Build a responsive invite waitlist with these sections: 1. Code field 2. Email 3. Dummy submit 4. How or [VERIFY] Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not invent a code generator.

Success State

9/30

✨ What it does

Claude builds a waitlist success page for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a success-state designer <context> I need one self-contained HTML waitlist success page I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Next: [NEXT] </inputs> <task> Build a responsive waitlist success page with these sections: 1. You are on the list 2. [NEXT] 3. No fake queue number unless I gave a rule Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not invent You are #4,201.

Error State

10/30

✨ What it does

Claude builds a waitlist error page for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are an error designer <context> I need one self-contained HTML waitlist error page I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Error: [ERROR] </inputs> <task> Build a responsive waitlist error page with these sections: 1. Form still there 2. Error from [ERROR] 3. Retry Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Keep the email they typed.

Referral

5 prompts

Referral Waitlist

11/30

✨ What it does

Claude builds a referral waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a referral designer <context> I need one self-contained HTML referral waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Reward I can honor: [REWARD OR NONE] </inputs> <task> Build a responsive referral waitlist with these sections: 1. Email 2. After dummy submit, a share stub 3. Reward or none 4. No fake position Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: If there is no reward, do not invent one.

Share Cards

12/30

✨ What it does

Claude builds a share-card waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a share-card designer <context> I need one self-contained HTML share-card waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Line they can paste: [LINE] </inputs> <task> Build a responsive share-card waitlist with these sections: 1. Success 2. Copy [LINE] 3. Dummy copy button in JS Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: The copy button should work in the Artifact.

Team Waitlist

13/30

✨ What it does

Claude builds a team waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a team-waitlist designer <context> I need one self-contained HTML team waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Seats: [SEATS OR VERIFY] </inputs> <task> Build a responsive team waitlist with these sections: 1. Team name 2. Emails 3. Dummy submit 4. Seats or [VERIFY] Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not invent a 5-seat gift.

Leaderboard Honest

14/30

✨ What it does

Claude builds a no-fake-rank waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are an anti-gamify designer <context> I need one self-contained HTML no-fake-rank waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - What we show: [SHOW] </inputs> <task> Build a responsive no-fake-rank waitlist with these sections: 1. Email 2. Only [SHOW] 3. No fake rank Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Ranks you cannot compute do not appear.

Double Opt Stub

15/30

✨ What it does

Claude builds a double-opt waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a consent designer <context> I need one self-contained HTML double-opt waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Confirm copy: [CONFIRM] </inputs> <task> Build a responsive double-opt waitlist with these sections: 1. Email 2. Check your email message from [CONFIRM] 3. Dummy only Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not send real mail from the Artifact.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Launch

5 prompts

Launch Date Known

16/30

✨ What it does

Claude builds a dated waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a launch-date designer <context> I need one self-contained HTML dated waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Date: [DATE OR VERIFY] </inputs> <task> Build a responsive dated waitlist with these sections: 1. Date or [VERIFY] 2. Email 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: No fake October if you are unsure.

No Date Waitlist

17/30

✨ What it does

Claude builds a dateless waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a no-date designer <context> I need one self-contained HTML dateless waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Why no date: [WHY] </inputs> <task> Build a responsive dateless waitlist with these sections: 1. We do not have a date 2. [WHY] 3. Email Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Honesty beats Q4 2026 theater.

Changelog Tease

18/30

✨ What it does

Claude builds a changelog waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a changelog teaser <context> I need one self-contained HTML changelog waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Shipped: [SHIPPED] - Next: [NEXT OR VERIFY] </inputs> <task> Build a responsive changelog waitlist with these sections: 1. Shipped list 2. Next or [VERIFY] 3. Email Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not invent a shipped feature.

City Launch

19/30

✨ What it does

Claude builds a city waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a city-launch designer <context> I need one self-contained HTML city waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Cities: [CITIES] </inputs> <task> Build a responsive city waitlist with these sections: 1. City select from [CITIES] 2. Email 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Only cities you will actually open.

Waitlist Plus About

20/30

✨ What it does

Claude builds a waitlist-plus-about page for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a two-block designer <context> I need one self-contained HTML waitlist-plus-about page I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - About: [ABOUT] - Email label: [LABEL] </inputs> <task> Build a responsive waitlist-plus-about page with these sections: 1. Short about 2. Email 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: About stays short. This is still a waitlist.

Visual

5 prompts

Quiet Waitlist

21/30

✨ What it does

Claude builds a quiet waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a quiet designer <context> I need one self-contained HTML quiet waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Line: [LINE] </inputs> <task> Build a responsive quiet waitlist with these sections: 1. Space 2. Line 3. Email 4. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: No countdown clock.

Loud Waitlist

22/30

✨ What it does

Claude builds a loud waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a loud designer <context> I need one self-contained HTML loud waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Line: [LINE] - Accent: [COLOR] </inputs> <task> Build a responsive loud waitlist with these sections: 1. Big type 2. Email 3. Dummy submit 4. Still no fake timer Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Loud type, honest claims.

Mobile Waitlist

23/30

✨ What it does

Claude builds a mobile waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a mobile designer <context> I need one self-contained HTML mobile waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Line: [LINE] </inputs> <task> Build a responsive mobile waitlist with these sections: 1. Large input 2. Sticky submit 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Thumb first.

Rebuild Waitlist

24/30

✨ What it does

Claude builds a rebuilt waitlist for [CURRENT PASTE] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a ruthless editor <context> I need one self-contained HTML rebuilt waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [CURRENT PASTE] - Keep: [KEEP] - Cut: [CUT] </inputs> <task> Build a responsive rebuilt waitlist with these sections: 1. Diagnose 2. Rebuild 3. Keep [KEEP] 4. Cut [CUT] Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Paste the current page.

Multi-Language Stub

25/30

✨ What it does

Claude builds a i18n waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are an i18n designer <context> I need one self-contained HTML i18n waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Languages I have copy for: [LANGS] </inputs> <task> Build a responsive i18n waitlist with these sections: 1. Lang toggle only for [LANGS] 2. Email 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not machine-translate extra languages.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Fixes

5 prompts

Cut The Fake Count

26/30

✨ What it does

Claude builds a honest waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are an ethics editor <context> I need one self-contained HTML honest waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Count I have: [COUNT OR NONE] </inputs> <task> Build a responsive honest waitlist with these sections: 1. Rebuild 2. Count or no count 3. Email Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: If you do not have a count, drop the badge.

Spam-Honest Note

27/30

✨ What it does

Claude builds a spam-honest waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a deliverability-minded editor <context> I need one self-contained HTML spam-honest waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - What they get: [WHAT] </inputs> <task> Build a responsive spam-honest waitlist with these sections: 1. Email 2. What they get from [WHAT] 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not promise a weekly essay you will not send.

Closed Waitlist

28/30

✨ What it does

Claude builds a closed waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a closed-list designer <context> I need one self-contained HTML closed waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Why closed: [WHY] - What to do: [WHAT] </inputs> <task> Build a responsive closed waitlist with these sections: 1. We are closed 2. [WHY] 3. [WHAT] 4. Optional contact Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: A closed page should not still take emails.

Waitlist FAQ

29/30

✨ What it does

Claude builds a waitlist FAQ page for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are a FAQ writer <context> I need one self-contained HTML waitlist FAQ page I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - Questions: [QUESTIONS] </inputs> <task> Build a responsive waitlist FAQ page with these sections: 1. Tease 2. Email 3. FAQ from [QUESTIONS] 4. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Do not invent When do I get in.

Unsub Stub

30/30

✨ What it does

Claude builds a unsub-note waitlist for [PRODUCT] as a working page you can open in the chat. Check every [VERIFY] against your facts, then save the HTML and publish.

You are an unsub designer <context> I need one self-contained HTML unsub-note waitlist I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [PRODUCT] - How to leave: [LEAVE] </inputs> <task> Build a responsive unsub-note waitlist with these sections: 1. Email 2. How to leave from [LEAVE] 3. Dummy submit Use vanilla JS only if a control must actually work. </task> <constraints> - One self-contained HTML file. No build step, no frameworks. - Do not invent metrics, customers, prices, or dates. Mark gaps as [VERIFY]. - Semantic accessible markup, visible focus, labeled placeholders I can swap. - No We are passionate, unlock your potential, or in today's world. </constraints> <format> Return the full HTML as an Artifact, then name the one sentence a visitor should remember. </format>

💡

Pro tip: Say how they leave before they join.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

No. Every prompt tells Claude to mark missing facts as [VERIFY] instead of inventing customers, prices, or dates on the waitlist page. You still review the Artifact before you publish.

Use Claude with Artifacts (claude.ai or the desktop app). Paste a prompt, fill the brackets, and open the HTML Artifact in the chat. Download the file when it looks right.

Yes, it is one self-contained file with inline CSS. Swap photo placeholders and [VERIFY] lines, then host it. It is a working first page, not a production design system.

The prompts are free to copy. Generating Artifacts needs a Claude plan that can create them. The free tier has limits. Paid plans run more generously.

The hub covers a whole site. This page is only the waitlist page: thirty prompts, one job, so the Artifact stays on that page instead of turning into a generic homepage.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Entrepreneurs

7-day free trial. Cancel anytime.

Browse All Claude Prompt Collections Browse All Prompt Collections

Popular prompt collections

AI Photo Editing Prompts ChatGPT Jailbreak Prompt Best ChatGPT Prompts Funny Hinge Prompts ChatGPT Caricature Prompts