Claude Prompt Library

30 Claude Prompts for Survey Apps

30 copy-paste prompts

Fill the brackets. Claude returns one HTML survey as an Artifact: questions, progress, dummy submit. Answers stay in memory. Not Typeform and not a live panel.

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.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Hand-curated & tested by the AI Academy team

Ask

5 prompts

Single Page Survey

1/30

✨ What it does

Claude builds a single-page survey for [SURVEY] 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 survey designer <context> I need one self-contained HTML single-page survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive single-page survey with these sections: 1. Questions from [QUESTIONS] only 2. Dummy submit 3. Progress optional 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 question.

One Question Each

2/30

✨ What it does

Claude builds a one-by-one survey for [SURVEY] 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 step designer <context> I need one self-contained HTML one-by-one survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive one-by-one survey with these sections: 1. One at a time 2. Next back in JS 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: Back must restore the answer.

Required Mix

3/30

✨ What it does

Claude builds a required survey for [SURVEY] 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 required designer <context> I need one self-contained HTML required survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Required: [REQ] - Optional: [OPT] </inputs> <task> Build a responsive required survey with these sections: 1. Mix from those lists 2. Block submit if required empty 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 required.

Empty Survey

4/30

✨ What it does

Claude builds a empty survey for [SURVEY] 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 empty-state designer <context> I need one self-contained HTML empty survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Why empty: [WHY] </inputs> <task> Build a responsive empty survey with these sections: 1. Honest empty 2. [WHY] 3. Dummy add Q 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 sample NPS.

Intro Screen

5/30

✨ What it does

Claude builds a intro survey for [SURVEY] 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 intro designer <context> I need one self-contained HTML intro survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Why it exists: [WHY] - Time I can say: [TIME OR VERIFY] </inputs> <task> Build a responsive intro survey with these sections: 1. Why 2. Time or [VERIFY] 3. Start 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 3 minutes.

Types

5 prompts

Likert Survey

6/30

✨ What it does

Claude builds a likert survey for [SURVEY] 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 likert designer <context> I need one self-contained HTML likert survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Statements: [STATEMENTS] - Scale: [SCALE] </inputs> <task> Build a responsive likert survey with these sections: 1. Statements from [STATEMENTS] 2. Scale from [SCALE] 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 invent a statement.

NPS Stub

7/30

✨ What it does

Claude builds a nps survey 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 nps designer <context> I need one self-contained HTML nps survey 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] - Follow-up I ask: [FOLLOW] </inputs> <task> Build a responsive nps survey with these sections: 1. 0-10 2. [FOLLOW] 3. Dummy submit 4. No fake benchmark 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 industry NPS.

Multiple Choice

8/30

✨ What it does

Claude builds a choice survey for [SURVEY] 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 choice designer <context> I need one self-contained HTML choice survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Choices I wrote: [CHOICES] </inputs> <task> Build a responsive choice survey with these sections: 1. Choices from [CHOICES] 2. 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 Other unless I said so.

Open Text

9/30

✨ What it does

Claude builds a open survey for [SURVEY] 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 open-text designer <context> I need one self-contained HTML open survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Prompts: [PROMPTS] </inputs> <task> Build a responsive open survey with these sections: 1. Prompts from [PROMPTS] 2. Dummy submit 3. Soft maxlength if I set one 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 prompt.

Ranking

10/30

✨ What it does

Claude builds a rank survey for [SURVEY] 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 rank designer <context> I need one self-contained HTML rank survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Items: [ITEMS] </inputs> <task> Build a responsive rank survey with these sections: 1. Rank [ITEMS] in JS 2. 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 an item.

Logic

5 prompts

Skip Logic

11/30

✨ What it does

Claude builds a skip survey for [SURVEY] 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 skip designer <context> I need one self-contained HTML skip survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Rule: [RULE] </inputs> <task> Build a responsive skip survey with these sections: 1. Rule from [RULE] 2. Skip in JS 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 the skip you wrote.

Quota Stub

12/30

✨ What it does

Claude builds a quota survey for [SURVEY] 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 quota designer <context> I need one self-contained HTML quota survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Quota I have: [QUOTA OR NONE] </inputs> <task> Build a responsive quota survey with these sections: 1. Quota or skip 2. Dummy close 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 n=400.

Screen Out

13/30

✨ What it does

Claude builds a screenout survey for [SURVEY] 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 screen designer <context> I need one self-contained HTML screenout survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Rule: [RULE] - Copy: [COPY] </inputs> <task> Build a responsive screenout survey with these sections: 1. Rule from [RULE] 2. [COPY] 3. Stop 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 screen.

Progress Bar

14/30

✨ What it does

Claude builds a progress survey for [SURVEY] 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 progress designer <context> I need one self-contained HTML progress survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive progress survey with these sections: 1. Honest percent from count 2. Questions 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: Percent from real count.

Save Later Stub

15/30

✨ What it does

Claude builds a save-later survey for [SURVEY] 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 save designer <context> I need one self-contained HTML save-later survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive save-later survey with these sections: 1. Dummy save 2. Banner local only 3. Questions 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: Refresh may wipe it.

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

After

5 prompts

Thanks Survey

16/30

✨ What it does

Claude builds a thanks survey for [SURVEY] 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 thanks designer <context> I need one self-contained HTML thanks survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Thanks: [THANKS] </inputs> <task> Build a responsive thanks survey with these sections: 1. [THANKS] 2. No fake gift 3. Optional link I gave 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 gift card.

Results Stub

17/30

✨ What it does

Claude builds a results survey for [SURVEY] 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 results designer <context> I need one self-contained HTML results survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Results I have: [RESULTS OR NONE] </inputs> <task> Build a responsive results survey with these sections: 1. Results or empty 2. Dummy chart 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 67%.

Export Stub

18/30

✨ What it does

Claude builds a export survey for [SURVEY] 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 export designer <context> I need one self-contained HTML export survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Answers I have: [ANSWERS OR NONE] </inputs> <task> Build a responsive export survey with these sections: 1. Answers or empty 2. Dummy CSV 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 respondent.

Anonymous Note

19/30

✨ What it does

Claude builds a anon survey for [SURVEY] 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 anon designer <context> I need one self-contained HTML anon survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - What I store: [STORE OR VERIFY] </inputs> <task> Build a responsive anon survey with these sections: 1. Note from [STORE] or [VERIFY] 2. Questions 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 invent GDPR copy.

Closed Survey

20/30

✨ What it does

Claude builds a closed survey for [SURVEY] 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 designer <context> I need one self-contained HTML closed survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Closed copy: [COPY] </inputs> <task> Build a responsive closed survey with these sections: 1. Closed 2. [COPY] 3. No questions 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: Closed means closed.

Variants

5 prompts

Employee Pulse

21/30

✨ What it does

Claude builds a pulse survey for [TEAM] 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 pulse designer <context> I need one self-contained HTML pulse survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [TEAM] - Questions: [QUESTIONS] </inputs> <task> Build a responsive pulse survey with these sections: 1. Questions from [QUESTIONS] 2. Dummy submit 3. No fake eNPS 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 benchmark.

Class Quiz

22/30

✨ What it does

Claude builds a class quiz survey for [CLASS] 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 quiz designer <context> I need one self-contained HTML class quiz survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [CLASS] - Questions: [QUESTIONS] - Key I have: [KEY OR NONE] </inputs> <task> Build a responsive class quiz survey with these sections: 1. Questions 2. Score only if [KEY] 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 key, no score.

Rebuild Survey

23/30

✨ What it does

Claude builds a rebuilt survey 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 survey 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 survey with these sections: 1. Diagnose 2. Rebuild 3. Keep [KEEP] 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 survey.

Mobile Survey

24/30

✨ What it does

Claude builds a mobile survey for [SURVEY] 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 survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive mobile survey with these sections: 1. Big taps 2. Questions 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 to next.

Quiet Survey

25/30

✨ What it does

Claude builds a quiet survey for [SURVEY] 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 survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive quiet survey with these sections: 1. Type 2. Questions 3. No confetti 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 celebration on submit.

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

No Fake Response Count

26/30

✨ What it does

Claude builds a no-fake-n survey for [SURVEY] 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 counts skeptic <context> I need one self-contained HTML no-fake-n survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive no-fake-n survey with these sections: 1. Rebuild 2. No 1,204 responses 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: Counts you did not collect go.

A11y Survey

27/30

✨ What it does

Claude builds a accessible survey for [SURVEY] 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 a11y designer <context> I need one self-contained HTML accessible survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive accessible survey with these sections: 1. Fieldsets 2. Focus 3. Questions 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: Radios need a fieldset.

Label Dummy Submit

28/30

✨ What it does

Claude builds a labeled-dummy survey for [SURVEY] 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 honesty editor <context> I need one self-contained HTML labeled-dummy survey I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive labeled-dummy survey with these sections: 1. Dummy banner 2. Questions 3. Submit stub 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 it cannot store, say so.

Survey Plus Intro

29/30

✨ What it does

Claude builds a survey-plus-intro for [SURVEY] 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 combo designer <context> I need one self-contained HTML survey-plus-intro I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Why: [WHY] - Questions: [QUESTIONS] </inputs> <task> Build a responsive survey-plus-intro with these sections: 1. Why 2. Questions 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: Why stays short.

Survey Plus Thanks

30/30

✨ What it does

Claude builds a survey-plus-thanks for [SURVEY] 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 combo designer <context> I need one self-contained HTML survey-plus-thanks I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SURVEY] - Questions: [QUESTIONS] - Thanks: [THANKS] </inputs> <task> Build a responsive survey-plus-thanks with these sections: 1. Questions 2. [THANKS] 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: Thanks stays short.

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 survey app. 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 survey app: 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.

7-day free trial. Cancel anytime.