Claude Prompt Library

30 Claude Prompts for Customer Portals

30 copy-paste prompts

Fill the brackets. Claude returns one HTML customer portal as an Artifact: home, invoices, tickets. Dummy auth only. Not a live billing portal and not an admin 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

Home

5 prompts

Portal Home

1/30

✨ What it does

Claude builds a customer portal home 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 portal designer <context> I need one self-contained HTML customer portal home 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] - Widgets I can show: [WIDGETS] </inputs> <task> Build a responsive customer portal home with these sections: 1. Widgets from [WIDGETS] 2. Dummy sign out 3. Banner dummy auth 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 balance.

Welcome First Login

2/30

✨ What it does

Claude builds a first-login portal 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 first-run designer <context> I need one self-contained HTML first-login portal 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] - First steps: [STEPS] </inputs> <task> Build a responsive first-login portal with these sections: 1. Steps from [STEPS] 2. Skip 3. Dummy done 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 tour metric.

Empty Portal

3/30

✨ What it does

Claude builds a empty portal 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 empty-state designer <context> I need one self-contained HTML empty portal 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 empty: [WHY] </inputs> <task> Build a responsive empty portal with these sections: 1. Honest empty 2. [WHY] 3. How to get help 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 invoices.

Multi Account Switch

4/30

✨ What it does

Claude builds a account-switch portal 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 switcher designer <context> I need one self-contained HTML account-switch portal 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] - Accounts I have: [ACCOUNTS] </inputs> <task> Build a responsive account-switch portal with these sections: 1. Switcher from [ACCOUNTS] 2. Dummy switch 3. Banner dummy 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 org.

Status Banner

5/30

✨ What it does

Claude builds a status-banner portal 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 status designer <context> I need one self-contained HTML status-banner portal 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] - Status I can say: [STATUS OR NONE] </inputs> <task> Build a responsive status-banner portal with these sections: 1. Banner or skip 2. Home stub 3. No fake outage 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 none, skip the banner.

Billing

5 prompts

Invoice List

6/30

✨ What it does

Claude builds a invoice portal 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 invoice designer <context> I need one self-contained HTML invoice portal 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] - Invoices I have: [INVOICES OR NONE] </inputs> <task> Build a responsive invoice portal with these sections: 1. List or empty 2. Dummy PDF 3. [VERIFY] on amounts I did not give 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 $120.

Pay Invoice Stub

7/30

✨ What it does

Claude builds a pay-invoice portal for [INVOICE] 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 pay-invoice designer <context> I need one self-contained HTML pay-invoice portal I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [INVOICE] - Amount: [AMOUNT OR VERIFY] </inputs> <task> Build a responsive pay-invoice portal with these sections: 1. Amount or [VERIFY] 2. Dummy pay 3. Banner dummy 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 charge anyone.

Payment Method Stub

8/30

✨ What it does

Claude builds a payment-method portal 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 cards designer <context> I need one self-contained HTML payment-method portal 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] - Methods I can show: [METHODS OR NONE] </inputs> <task> Build a responsive payment-method portal with these sections: 1. Methods or none 2. Dummy add 3. No last four unless given 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 Visa 4242.

Plan Portal

9/30

✨ What it does

Claude builds a plan portal 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 plan designer <context> I need one self-contained HTML plan portal 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] - Plan: [PLAN OR VERIFY] </inputs> <task> Build a responsive plan portal with these sections: 1. Plan or [VERIFY] 2. Dummy change 3. No live Stripe 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 price.

Credits Stub

10/30

✨ What it does

Claude builds a credits portal 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 credits designer <context> I need one self-contained HTML credits portal 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] - Credits I have: [CREDITS OR NONE] </inputs> <task> Build a responsive credits portal with these sections: 1. Credits or none 2. How they expire [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 500 credits.

Support

5 prompts

Ticket List

11/30

✨ What it does

Claude builds a ticket portal 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 tickets designer <context> I need one self-contained HTML ticket portal 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] - Tickets: [TICKETS OR NONE] </inputs> <task> Build a responsive ticket portal with these sections: 1. Tickets or empty 2. Dummy new 3. Status only if given 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 ticket.

New Ticket

12/30

✨ What it does

Claude builds a new-ticket portal 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 form designer <context> I need one self-contained HTML new-ticket portal 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] - Fields: [FIELDS] </inputs> <task> Build a responsive new-ticket portal with these sections: 1. Fields from [FIELDS] 2. Dummy submit 3. No fake SLA 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 4 hour reply.

Ticket Thread

13/30

✨ What it does

Claude builds a ticket-thread portal for [TICKET] 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 thread designer <context> I need one self-contained HTML ticket-thread portal I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [TICKET] - Messages I have: [MESSAGES] </inputs> <task> Build a responsive ticket-thread portal with these sections: 1. Thread from [MESSAGES] 2. Dummy reply 3. No invented agent 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 messages you pasted.

Knowledge Stub

14/30

✨ What it does

Claude builds a help portal 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 help-center designer <context> I need one self-contained HTML help portal 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] - Articles: [ARTICLES OR NONE] </inputs> <task> Build a responsive help portal with these sections: 1. Articles or empty 2. Search 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: Do not invent an article.

Callback Stub

15/30

✨ What it does

Claude builds a callback portal 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 callback designer <context> I need one self-contained HTML callback portal 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] - Hours: [HOURS OR VERIFY] </inputs> <task> Build a responsive callback portal with these sections: 1. Hours or [VERIFY] 2. Dummy request 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 phone queue.

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

Profile

5 prompts

Profile Form

16/30

✨ What it does

Claude builds a profile portal 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 profile designer <context> I need one self-contained HTML profile portal 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] - Fields: [FIELDS] </inputs> <task> Build a responsive profile portal with these sections: 1. Fields from [FIELDS] 2. Dummy save 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 birthday.

Team Seats

17/30

✨ What it does

Claude builds a seats portal 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 seats designer <context> I need one self-contained HTML seats portal 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 seats portal with these sections: 1. Seats or [VERIFY] 2. Dummy invite 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 10 seats.

Notifications Prefs

18/30

✨ What it does

Claude builds a notif portal 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 prefs designer <context> I need one self-contained HTML notif portal 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] - Channels I have: [CHANNELS] </inputs> <task> Build a responsive notif portal with these sections: 1. Channels from [CHANNELS] 2. Dummy save 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 SMS if you have none.

Api Keys Stub

19/30

✨ What it does

Claude builds a api-keys portal 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 keys designer <context> I need one self-contained HTML api-keys portal 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] - Keys I can show: [KEYS OR NONE] </inputs> <task> Build a responsive api-keys portal with these sections: 1. Keys or none 2. Dummy create 3. Mask secrets 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 live key.

Close Account

20/30

✨ What it does

Claude builds a close-account portal 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 close-flow designer <context> I need one self-contained HTML close-account portal 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] - Copy I want: [COPY] </inputs> <task> Build a responsive close-account portal with these sections: 1. Copy from [COPY] 2. Dummy close 3. No guilt 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 confirm-shaming you did not write.

Variants

5 prompts

B2B Portal

21/30

✨ What it does

Claude builds a b2b portal 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 B2B portal designer <context> I need one self-contained HTML b2b portal 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] - Orgs: [ORGS] </inputs> <task> Build a responsive b2b portal with these sections: 1. Org home 2. Invoices stub 3. Dummy switch 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 orgs you named.

Agency Client Portal

22/30

✨ What it does

Claude builds a agency portal for [AGENCY] 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 agency designer <context> I need one self-contained HTML agency portal I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [AGENCY] - Clients: [CLIENTS] - Files: [FILES OR NONE] </inputs> <task> Build a responsive agency portal with these sections: 1. Clients from [CLIENTS] 2. Files or empty 3. Dummy comment 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 client.

School Parent Portal

23/30

✨ What it does

Claude builds a parent portal for [SCHOOL] 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 school-portal designer <context> I need one self-contained HTML parent portal I can open in this chat as an Artifact. One file. Inline CSS. Google Fonts only. Real copy, no lorem ipsum. </context> <inputs> - Primary: [SCHOOL] - Kids I can show: [KIDS] </inputs> <task> Build a responsive parent portal with these sections: 1. Kids from [KIDS] 2. Dummy message 3. No invented grades 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 GPA.

Rebuild Portal

24/30

✨ What it does

Claude builds a rebuilt portal 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 portal 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 portal 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 portal.

Mobile Portal

25/30

✨ What it does

Claude builds a mobile portal 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 portal 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] - Widgets: [WIDGETS] </inputs> <task> Build a responsive mobile portal with these sections: 1. Stack 2. Sticky help 3. Dummy sign out 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 help.

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

Label Dummy Auth

26/30

✨ What it does

Claude builds a labeled-dummy portal 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 honesty editor <context> I need one self-contained HTML labeled-dummy portal 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] - Widgets: [WIDGETS] </inputs> <task> Build a responsive labeled-dummy portal with these sections: 1. Rebuild 2. Dummy auth banner 3. Home 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 they cannot log in, say so.

A11y Portal

27/30

✨ What it does

Claude builds a accessible portal 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 a11y designer <context> I need one self-contained HTML accessible portal 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] - Widgets: [WIDGETS] </inputs> <task> Build a responsive accessible portal with these sections: 1. Labels 2. Focus 3. Home 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: Sign out is a button.

No Fake SLA

28/30

✨ What it does

Claude builds a no-fake-sla portal 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 sla skeptic <context> I need one self-contained HTML no-fake-sla portal 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] - Tickets: [TICKETS OR NONE] </inputs> <task> Build a responsive no-fake-sla portal with these sections: 1. Tickets 2. No 2h reply unless I wrote it 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: SLA you cannot keep goes.

Portal Plus Invoices

29/30

✨ What it does

Claude builds a portal-plus-invoices 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 combo designer <context> I need one self-contained HTML portal-plus-invoices 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] - Invoices: [INVOICES OR NONE] </inputs> <task> Build a responsive portal-plus-invoices with these sections: 1. Home 2. Invoices or 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: Empty is honest.

Portal Plus Tickets

30/30

✨ What it does

Claude builds a portal-plus-tickets 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 combo designer <context> I need one self-contained HTML portal-plus-tickets 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] - Tickets: [TICKETS OR NONE] </inputs> <task> Build a responsive portal-plus-tickets with these sections: 1. Home 2. Tickets or 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 a ticket.

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 customer portal. 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 customer portal: 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.