30 Claude Prompts That Build About Pages
Fill the brackets. Claude returns one HTML About page as an Artifact: founder story, team, values, timeline, press. Swap the copy and photos, then publish. Not a full website and not a sales landing page.
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. Drafted with AI writing assistance and checked against our editorial policy.
Founder Story
5 promptsOrigin Story Page
1/30✨ What it does
Claude builds a founder origin About page for [COMPANY] 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 ghostwriter and front-end designer <context> I need one self-contained HTML founder-origin 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: [COMPANY] - Founder: [FOUNDER] - First messy week: [ORIGIN SCENE] - Problem: [THE PROBLEM] - First proof: [FIRST PROOF] - Vibe: [WARM / DIRECT] </inputs> <task> Build a responsive founder-origin About page with these sections: 1. Hero from [ORIGIN SCENE] 2. Three short origin scenes 3. The problem and who it hurt 4. First proof only from [FIRST PROOF] 5. What is still true 6. Soft close, no pricing 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: Give the messy week, not We are passionate about.
Founder Letter Page
2/30✨ What it does
Claude builds a founder letter About page for [FOUNDER NAME] 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 who writes a public letter <context> I need one self-contained HTML first-person founder letter 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: [FOUNDER NAME] - Company: [COMPANY] - Reader: [READER] - Feeling: [FEELING] - Safe detail: [PRIVATE-OK DETAIL] - Off-limits: [OFF-LIMITS CLAIMS] </inputs> <task> Build a responsive first-person founder letter About page with these sections: 1. Quiet header 2. 450-700 word letter 3. Pull-quote 4. Bio card and headshot placeholder 5. One next step 6. Signature line 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: Write as if one customer will read it.
Why We Started Page
3/30✨ What it does
Claude builds a why-we-started About page 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 positioning writer <context> I need one self-contained HTML why-we-started 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: [THE PROBLEM] - Company: [COMPANY] - Old workaround: [OLD WAY] - Who hurts: [WHO HURTS] - First thing built: [FIRST THING] </inputs> <task> Build a responsive why-we-started About page with these sections: 1. Hero that names [THE PROBLEM] 2. The old way in steps 3. Who it costs 4. Why we started 5. What we built first, not a tour 6. Who should keep the old way 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: Name the old workaround people still use.
Personal Brand About
4/30✨ What it does
Claude builds a personal-brand About page for [YOUR NAME] 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 personal-brand editor <context> I need one self-contained HTML one-person 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: [YOUR NAME] - Who you help: [WHO YOU HELP] - Job they hire: [THE JOB] - Proof: [PROOF] - How you work: [HOW YOU WORK] - Links: [LINKS] </inputs> <task> Build a responsive one-person About page with these sections: 1. Hero with positioning line 2. The job in plain words 3. For / not for 4. Proof only from [PROOF] 5. How working together goes 6. Contact strip 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: Lead with the job, not a title.
Partnership Story Page
5/30✨ What it does
Claude builds a partnership About page for [BUSINESS NAME] 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 writer for two-person shops <context> I need one self-contained HTML partnership 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: [BUSINESS NAME] - People and split: [PEOPLE] [SPLIT] - Start place: [START PLACE] - What you do: [WHAT WE DO] - House rule: [HOUSE RULE] </inputs> <task> Build a responsive partnership About page with these sections: 1. Hero with both names 2. How it started 3. Who does what 4. House rule 5. First visit 6. Soft 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: Say how you actually split the work.
Team
5 promptsTeam Grid Page
6/30✨ What it does
Claude builds a team-grid About page for [COMPANY] 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 studio designer <context> I need one self-contained HTML team-grid 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: [COMPANY] - Team line: [TEAM LINE] - People: [TEAM LIST] - How we work: [HOW WE WORK] </inputs> <task> Build a responsive team-grid About page with these sections: 1. Hero plus group photo placeholder 2. Equal-height cards from [TEAM LIST] only 3. How we work, 3 points 4. We are small on purpose if the list is short 5. Soft 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: One human line per person, not a LinkedIn dump.
Leadership Bios Page
7/30✨ What it does
Claude builds a leadership bios About page for [LEADER LIST] 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 corporate editor <context> I need one self-contained HTML leadership 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: [LEADER LIST] - Company: [COMPANY] - Off-limits: [OFF-LIMITS] - Board note: [BOARD OR NONE] </inputs> <task> Build a responsive leadership About page with these sections: 1. Hero: who leads this 2. Featured first leader 3. Remaining bios 120-180 words from facts given 4. Skip invented degrees 5. Contact line, no fake awards 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: Give scope they actually own.
Hiring-Led Team Page
8/30✨ What it does
Claude builds a hiring-led team About page for [OPEN ROLES] 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 recruiting marketer <context> I need one self-contained HTML hiring-led team 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: [OPEN ROLES] - Company: [COMPANY] - Current team: [CURRENT TEAM] - Work life: [WORK LIFE] - Apply: [APPLY LINK OR EMAIL] </inputs> <task> Build a responsive hiring-led team About page with these sections: 1. Meet the team, then we are hiring 2. Current team only 3. What work feels like 4. Role cards from [OPEN ROLES] 5. Fit / not a fit 6. One apply action 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: Show the living team first.
Remote Team Page
9/30✨ What it does
Claude builds a remote-team About page for [COMPANY] 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 distributed-team designer <context> I need one self-contained HTML remote-team 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: [COMPANY] - Timezones: [TIMEZONES] - How we meet: [RITUALS] - People: [TEAM LIST] </inputs> <task> Build a responsive remote-team About page with these sections: 1. Hero that says we are not in one office 2. Map or timezone strip from [TIMEZONES] 3. Team cards 4. How we actually meet 5. Soft 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 an HQ city.
Small Studio Page
10/30✨ What it does
Claude builds a small-studio About page for [STUDIO NAME] 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 studio copywriter <context> I need one self-contained HTML small-studio 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: [STUDIO NAME] - Craft: [CRAFT] - Clients we name: [NAMED CLIENTS OR NONE] - People: [PEOPLE] </inputs> <task> Build a responsive small-studio About page with these sections: 1. Hero with the craft 2. How a project runs 3. People 4. Selected work only if named 5. Write us 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 cannot name a client, skip the logo wall.
Values & Mission
5 promptsValues In Practice
11/30✨ What it does
Claude builds a values About page for [COMPANY] 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 editor who hates poster values <context> I need one self-contained HTML values 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: [COMPANY] - Values we can prove: [VALUES] - A time we paid for one: [PROOF STORY] </inputs> <task> Build a responsive values About page with these sections: 1. Hero that refuses poster words 2. Each value with a proof from [PROOF STORY] or [VERIFY] 3. What we will not do 4. Soft 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: A value without a story is a poster.
Mission Without Slides
12/30✨ What it does
Claude builds a mission About page for [MISSION IN OUR WORDS] 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 plain-speech writer <context> I need one self-contained HTML mission 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: [MISSION IN OUR WORDS] - Company: [COMPANY] - Who we refuse: [NOT FOR] </inputs> <task> Build a responsive mission About page with these sections: 1. Mission in spoken language 2. Who it is for 3. Who should leave 4. How a visitor sees it in the product 5. Soft 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: If it could sit on any SaaS site, rewrite.
Principles Page
13/30✨ What it does
Claude builds a principles About page for [PRINCIPLES] 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 product editor <context> I need one self-contained HTML working-principles 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: [PRINCIPLES] - Company: [COMPANY] - Tradeoff we picked: [TRADEOFF] </inputs> <task> Build a responsive working-principles About page with these sections: 1. Hero: how we decide 2. Numbered principles from [PRINCIPLES] 3. The tradeoff we live with 4. Soft 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: Name the thing you gave up.
Culture Without Perks
14/30✨ What it does
Claude builds a culture About page for [COMPANY] 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 hiring editor <context> I need one self-contained HTML culture 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: [COMPANY] - How work feels: [WORK FEEL] - Perk we will not list: [SKIP PERKS] </inputs> <task> Build a responsive culture About page with these sections: 1. Hero about the work 2. A normal week 3. What is hard 4. Who thrives 5. No snack-wall section 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: Skip the snack wall. Describe a Tuesday.
Ethics Note Page
15/30✨ What it does
Claude builds a ethics-note About page for [COMPANY] 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 careful public-notes writer <context> I need one self-contained HTML ethics-note 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: [COMPANY] - What we collect: [DATA WE TOUCH] - What we refuse: [REFUSALS] </inputs> <task> Build a responsive ethics-note About page with these sections: 1. Hero: how we treat people and data 2. What we collect 3. What we refuse 4. How to ask a question 5. No legal novel 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 privacy lawyer quote.
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. The library keeps growing.
Timeline & History
5 promptsHonest Timeline Page
16/30✨ What it does
Claude builds a timeline About page for [COMPANY] 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 company historian who will not invent years <context> I need one self-contained HTML timeline 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: [COMPANY] - Dated events I can stand behind: [EVENTS] - Gaps: [UNKNOWN YEARS] </inputs> <task> Build a responsive timeline About page with these sections: 1. Hero 2. Timeline only from [EVENTS] 3. Gaps labeled, not filled 4. Soft 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: Empty years stay empty.
Milestones Only Page
17/30✨ What it does
Claude builds a milestones About page for [MILESTONES] 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 editor of proof <context> I need one self-contained HTML milestones 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: [MILESTONES] - Company: [COMPANY] - What counts: [RULE] </inputs> <task> Build a responsive milestones About page with these sections: 1. Hero 2. Milestone cards from [MILESTONES] only 3. What does not count 4. Soft 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: A launch party is not a milestone unless you said so.
Before And After Page
18/30✨ What it does
Claude builds a before-and-after About page for [COMPANY] 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 story editor <context> I need one self-contained HTML before-and-after 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: [COMPANY] - Before: [BEFORE] - After we can prove: [AFTER] </inputs> <task> Build a responsive before-and-after About page with these sections: 1. Split hero 2. Before scene 3. After scene using only [AFTER] 4. What is still messy 5. Soft 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: Keep a messy leftover so it stays honest.
Place Story Page
19/30✨ What it does
Claude builds a place-based About page for [PLACE] 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 local writer <context> I need one self-contained HTML place-based 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: [PLACE] - Company: [COMPANY] - Why this place: [WHY HERE] </inputs> <task> Build a responsive place-based About page with these sections: 1. Hero with [PLACE] 2. Why here 3. What the place changes about the work 4. Visit or write 5. No fake landmark history 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 founding myth about the city.
Archive Note Page
20/30✨ What it does
Claude builds a archive About page for [COMPANY] 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 archivist <context> I need one self-contained HTML archive 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: [COMPANY] - What we kept: [ARTIFACTS] - What we lost: [LOST] </inputs> <task> Build a responsive archive About page with these sections: 1. Hero 2. Artifacts with placeholders 3. What we lost, named 4. Soft 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: A missing box is more honest than a stock photo.
Press & Proof
5 promptsPress Kit About Page
21/30✨ What it does
Claude builds a press-kit About page for [COMPANY] 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 PR editor <context> I need one self-contained HTML press-kit 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: [COMPANY] - Boilerplate I approve: [BOILERPLATE] - Assets: [ASSET LIST] - Contact: [PRESS EMAIL] </inputs> <task> Build a responsive press-kit About page with these sections: 1. Hero 2. Short boilerplate 3. Asset list with placeholders 4. Facts we will confirm 5. Press email 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 coverage you do not have.
Proof Wall Page
22/30✨ What it does
Claude builds a proof About page for [PROOF LIST] 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 proof editor <context> I need one self-contained HTML proof 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: [PROOF LIST] - Company: [COMPANY] - Off-limits claims: [OFF-LIMITS] </inputs> <task> Build a responsive proof About page with these sections: 1. Hero 2. Proof cards only from [PROOF LIST] 3. [VERIFY] on thin items 4. Soft 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: Logos you cannot name do not go on the wall.
Customer Words Page
23/30✨ What it does
Claude builds a customer-words About page for [QUOTES I HAVE] 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 testimonials editor <context> I need one self-contained HTML customer-words 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: [QUOTES I HAVE] - Company: [COMPANY] - Attribution rules: [HOW TO NAME THEM] </inputs> <task> Build a responsive customer-words About page with these sections: 1. Hero 2. Quotes only from [QUOTES I HAVE] 3. Attribution as allowed 4. Soft 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: No invented customer. A blank is better.
Awards We Actually Won
24/30✨ What it does
Claude builds a awards About page for [AWARDS] 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 restrained editor <context> I need one self-contained HTML awards 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: [AWARDS] - Company: [COMPANY] </inputs> <task> Build a responsive awards About page with these sections: 1. Hero 2. Award list from [AWARDS] only 3. Skip years you do not have 4. Soft 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: If the list is one line, the page can be one line.
FAQ About Page
25/30✨ What it does
Claude builds a FAQ About page for [COMPANY] 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 plain FAQ writer <context> I need one self-contained HTML FAQ 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: [COMPANY] - Real questions: [QUESTIONS] - Answers I can stand behind: [ANSWERS] </inputs> <task> Build a responsive FAQ About page with these sections: 1. Hero 2. Accordion from [QUESTIONS] 3. What we will not answer here 4. Write us 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 to look thorough.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: hands-on tutorials on Claude, ChatGPT, Midjourney, and many other AI tools. New tutorials are added regularly.
Fixes & Variants
5 promptsNonprofit About Page
26/30✨ What it does
Claude builds a nonprofit About page for [ORG NAME] 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 nonprofit editor <context> I need one self-contained HTML nonprofit 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: [ORG NAME] - Who you serve: [WHO] - What the money does: [MONEY DOES] - How to help: [HELP] </inputs> <task> Build a responsive nonprofit About page with these sections: 1. Hero with who you serve 2. What the work is 3. Where money goes, only if you said 4. Help actions 5. No guilt 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 an impact percent.
Local Shop About Page
27/30✨ What it does
Claude builds a local-shop About page for [SHOP NAME] 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 shop writer <context> I need one self-contained HTML local-shop 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: [SHOP NAME] - Hours: [HOURS OR UNKNOWN] - Address: [ADDRESS] - What you sell: [WHAT] </inputs> <task> Build a responsive local-shop About page with these sections: 1. Hero 2. What you sell 3. Hours and address or [VERIFY] 4. How a first visit goes 5. Map placeholder 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: Unknown hours stay unknown.
Rebuild My Weak About
28/30✨ What it does
Claude builds a rebuilt About page for [CURRENT ABOUT URL OR 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 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: [CURRENT ABOUT URL OR PASTE] - What must stay: [KEEP] - Lies to cut: [CUT] </inputs> <task> Build a responsive rebuilt About page with these sections: 1. Diagnose the paste 2. Rebuild one HTML page 3. Keep [KEEP] 4. Cut [CUT] 5. List what you refused to invent 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. Do not describe it from memory.
Short About, One Screen
29/30✨ What it does
Claude builds a one-screen About page for [COMPANY] 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 concise designer <context> I need one self-contained HTML one-screen 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: [COMPANY] - One sentence: [ONE SENTENCE] - One proof: [ONE PROOF] - One action: [ACTION] </inputs> <task> Build a responsive one-screen About page with these sections: 1. Single screen 2. Sentence, proof, action 3. Photo placeholder 4. No extra sections 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 scroll, you are on the wrong prompt.
About Plus Contact
30/30✨ What it does
Claude builds a About-plus-contact page for [COMPANY] 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 designer of simple sites <context> I need one self-contained HTML About-plus-contact 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: [COMPANY] - Story: [STORY] - Email: [EMAIL] - Other: [OTHER CONTACT OR NONE] </inputs> <task> Build a responsive About-plus-contact page with these sections: 1. Short story 2. Contact block with real mailto 3. No newsletter dark pattern 4. Soft 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: One email is enough if that is all you have.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.
7-day free trial. Cancel anytime.
Related guides