Claude Prompt Library

30 Claude Prompts That Design UI Screens

30 copy-paste prompts

Describe the screen and Claude returns a real, polished interface as a self-contained HTML/CSS artifact you can preview instantly. Prompts for full app screens, component libraries, design systems, settings, pricing, onboarding, empty states, mobile, and dark-mode UI. Not "give me some divs."

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

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

Full App Screens

5 prompts

Analytics Dashboard Screen

1/30

You are a senior product designer and front-end engineer who builds data-dense SaaS interfaces. <context> I need a complete analytics dashboard screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and what it measures: [E.G. EMAIL TOOL, SENDS AND OPENS] - Key metrics for the top row: [4 KPIs] - Main chart to feature: [E.G. ACTIVITY OVER TIME] - Secondary widgets: [E.G. TOP SOURCES, RECENT ACTIVITY TABLE] - Brand color and vibe: [DESCRIBE] - Audience: [WHO USES IT] </inputs> <task> Design the screen with: a left sidebar nav (logo, 5-6 menu items, active state), a top bar with page title, date-range pill, and account avatar; a row of four KPI stat cards with value, label, and a colored up/down delta; one large featured chart area drawn with CSS bars or an inline SVG line; two secondary widgets (a ranked list and a recent-activity table); and a subtle empty-data hint. Use realistic sample numbers. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, no chart libraries. - Consistent spacing scale, soft shadows, clear visual hierarchy, accessible contrast and focus states. - Charts are drawn with CSS or inline SVG, not images. </constraints> <format> Return the full HTML as an artifact, then list the layout grid and design tokens (spacing, color, type scale) so I can extend it. </format>

Generates a complete data-dense analytics dashboard screen with sidebar, KPI cards, and CSS charts as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude the single most important metric and ask it to make that card visually dominate the others.

Inbox / Messaging Screen

2/30

You are a UX engineer who designs communication and inbox interfaces. <context> I need a messaging or inbox screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product context: [E.G. SUPPORT TOOL, TEAM CHAT, EMAIL CLIENT] - Items in the list: [SENDERS AND SUBJECT LINES] - Filters or folders to show: [E.G. ALL, UNREAD, ASSIGNED] - Brand color and vibe: [DESCRIBE] - Audience: [WHO USES IT] </inputs> <task> Build a three-pane inbox layout: a narrow left rail of folders/filters with counts, a middle conversation list (avatar, sender, subject, preview snippet, timestamp, unread dot), and a right reading pane showing the selected thread as message bubbles with a reply composer at the bottom. Mark one list item active and render its thread in the reading pane. Use realistic sample content. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Unread, active, and hover states must be visually distinct; accessible contrast and focus order. - Reading pane scrolls independently of the list; composer pinned to the bottom. </constraints> <format> Return the full HTML as an artifact, then explain the three-pane responsive behavior and where to collapse panes on mobile. </format>

Builds a three-pane inbox or messaging screen with conversation list and reading pane as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to add a clear visual distinction between read and unread rows so the inbox is scannable at a glance.

Kanban Board Screen

3/30

You are a product designer who builds project-management and workflow tools. <context> I need a kanban board screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - What is being tracked: [E.G. TASKS, DEALS, CONTENT] - Columns/statuses: [E.G. BACKLOG, IN PROGRESS, REVIEW, DONE] - Card fields to show: [E.G. TITLE, ASSIGNEE, LABEL, DUE DATE] - Brand color and vibe: [DESCRIBE] - Audience: [WHO USES IT] </inputs> <task> Build a kanban board with: a top bar (board title, view switcher, filter and add-task buttons, member avatars), and a horizontally scrolling row of columns. Each column has a header with name, a count badge, and an add button, plus 3-5 cards. Cards show a colored label chip, title, a small avatar, a due-date pill, and a subtle priority indicator. Populate every column with realistic items. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Columns scroll horizontally on overflow; cards have clear hover and drag-affordance styling (visual only). - Consistent card spacing, accessible contrast, and a clear active/empty-column state. </constraints> <format> Return the full HTML as an artifact, then describe the card data structure and column tokens so I can wire it to real data. </format>

Creates a multi-column kanban board screen with realistic cards and labels as a previewable artifact.

๐Ÿ’ก

Pro tip: Hand Claude one fully detailed card and it will keep the field layout uniform across every column.

Calendar / Scheduling Screen

4/30

You are a UX engineer who designs calendar and scheduling interfaces. <context> I need a calendar screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Calendar purpose: [E.G. TEAM SCHEDULE, BOOKINGS, CONTENT PLAN] - Default view: [MONTH / WEEK] - Event types and their colors: [E.G. MEETING BLUE, FOCUS GREEN] - Sample events to place: [TITLES, DAYS, TIMES] - Brand vibe: [DESCRIBE] </inputs> <task> Build a calendar screen with: a top bar (month/week toggle, prev/next arrows, current period label, today button, and a create-event button), an optional left mini-month for navigation, and the main grid. For a month view render a 7-column grid with weekday headers and date cells; for a week view render time-slotted columns. Place color-coded event chips across several cells, with one day highlighted as today. Use realistic event titles. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Today, selected, and out-of-month days are visually distinct; event chips are color-coded with accessible contrast. - Grid stays aligned and legible; clear hover state on date cells. </constraints> <format> Return the full HTML as an artifact, then explain how the month and week views share styling and how events map to cells. </format>

Builds a month or week calendar screen with color-coded event chips and navigation as a previewable artifact.

๐Ÿ’ก

Pro tip: Give Claude a color per event type up front so the whole calendar reads as a legend without needing one.

User Profile / Account Screen

5/30

You are a product designer who builds account and profile interfaces. <context> I need a user profile screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product context: [E.G. SOCIAL APP, SAAS TOOL, MARKETPLACE] - Profile fields to show: [E.G. NAME, ROLE, BIO, STATS, ACTIVITY] - Stats or highlights: [E.G. POSTS, FOLLOWERS, COMPLETION] - Tabs on the profile: [E.G. OVERVIEW, ACTIVITY, SETTINGS] - Brand vibe and color: [DESCRIBE] </inputs> <task> Build a profile screen with: a cover/banner band, an overlapping avatar with name, role, and a primary action button (follow / edit / message); a stat row of three to four numbers with labels; a tab bar switching content; and a default tab showing a bio block, an info card (location, joined date, links), and a recent-activity list. Use realistic sample content and one visibly active tab. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Avatar overlap, tab active state, and button hierarchy are clean and accessible. - Stacks gracefully on mobile; placeholder image areas are labeled color blocks. </constraints> <format> Return the full HTML as an artifact, then list the section structure and tokens so I can add more tabs. </format>

Generates a user profile screen with banner, stats, tabs, and activity feed as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to keep the primary action button (follow or edit) anchored next to the avatar so it never gets lost on scroll.

XML tags are just the start. Learn the full Claude workflow.

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

Start 7-Day Free Trial

Component Libraries

5 prompts

Button & Badge Library

6/30

You are a design-systems engineer who documents reusable UI components. <context> I need a button and badge component library, rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact and laid out like a living style guide. </context> <inputs> - Brand primary color and accent: [HEX OR DESCRIBE] - Vibe: [E.G. ROUNDED FRIENDLY, SHARP TECHNICAL] - Button variants I need: [E.G. PRIMARY, SECONDARY, GHOST, DESTRUCTIVE] - Sizes: [E.G. SM, MD, LG] </inputs> <task> Build a gallery page that showcases every button variant across sizes, plus default, hover, focus, active, loading (spinner), and disabled states; icon-left, icon-right, and icon-only buttons; and a set of status badges and pills (neutral, success, warning, error, info) in solid and soft styles. Label each specimen with its name and intended use. Group them in clearly titled sections on a clean canvas. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons. - Real hover/focus/active states via CSS; visible focus rings; accessible contrast for every variant. - Consistent radius, padding, and type scale across all components. </constraints> <format> Return the full HTML as an artifact, then list the CSS custom properties (color, radius, spacing) that drive the components. </format>

Produces a living style guide of button and badge variants with every interaction state as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to drive everything off CSS variables so you can retheme the whole set by changing two colors.

Card Component Set

7/30

You are a design-systems engineer who builds reusable card patterns. <context> I need a set of card components rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact and arranged like a pattern catalog. </context> <inputs> - Product context: [E.G. SAAS, ECOMMERCE, CONTENT] - Card types I need: [E.G. STAT, PRODUCT, PROFILE, ARTICLE, PRICING TEASER] - Brand color and vibe: [DESCRIBE] - Density: [COMPACT / COMFORTABLE] </inputs> <task> Build a catalog showing each card type with realistic content: a stat card (value, label, delta), a product card (image area, title, price, rating, add-to-cart), a profile card (avatar, name, role, action), an article/media card (cover, tag, title, excerpt, meta), and an interactive card with a hover lift. Include each card's default and hover state side by side, and show a loading-skeleton version of one card. Group under clear section headers. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Consistent radius, shadow, and padding system shared across all cards; accessible contrast. - Image areas are labeled color blocks; skeletons use a subtle shimmer. </constraints> <format> Return the full HTML as an artifact, then explain the shared card tokens and how to compose new card types from them. </format>

Creates a catalog of reusable card patterns with hover and skeleton states as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to reuse one base .card class so every new card type inherits the same radius, shadow, and padding.

Form Controls Kit

8/30

You are a design-systems engineer who specializes in accessible form controls. <context> I need a complete form-controls kit rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact and laid out like a documentation page. </context> <inputs> - Brand color and vibe: [DESCRIBE] - Controls I need: [E.G. TEXT INPUT, SELECT, CHECKBOX, RADIO, TOGGLE, TEXTAREA, FILE, SLIDER] - Density: [COMPACT / COMFORTABLE] </inputs> <task> Build a kit showing each control with a label, helper text, and its states: default, focus, filled, disabled, and error (with an inline error message). Include text input with leading icon, a select, grouped checkboxes and radios, a custom toggle switch, a textarea with character count, a styled file-upload, and a range slider. Add one assembled example form (e.g. a settings or signup form) to show them composed together. Use realistic labels. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Every control has a real <label>, visible focus ring, and accessible error styling (not color alone). - Consistent field height, radius, and spacing; valid native input types. </constraints> <format> Return the full HTML as an artifact, then list the field tokens and accessibility decisions (labels, focus, error pattern). </format>

Builds an accessible form-controls kit with every input state plus an assembled example form as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to show the error state with both color and an icon plus message so it stays accessible to color-blind users.

Navigation Component Pack

9/30

You are a UX engineer who builds navigation patterns for web apps. <context> I need a navigation component pack rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact and grouped as a pattern library. </context> <inputs> - Product context: [E.G. SAAS APP, MARKETING SITE] - Nav patterns I need: [E.G. TOP NAV, SIDEBAR, TABS, BREADCRUMBS, PAGINATION, STEPPER] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a pack showcasing each pattern with active/hover states: a top navbar with logo, links, search, and avatar (plus a hamburger state); a collapsible sidebar with nested items, icons, and an active highlight; a tab bar (underline and pill variants); a breadcrumb trail; a pagination control with prev/next and a current page; and a multi-step progress stepper with completed, current, and upcoming steps. Label each section. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons. - Clear active, hover, and focus states; keyboard-navigable structure; accessible contrast. - Patterns are visually consistent and reusable. </constraints> <format> Return the full HTML as an artifact, then explain how the active-state styling is shared across nav patterns. </format>

Generates a navigation pattern pack (navbar, sidebar, tabs, breadcrumbs, pagination, stepper) as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to use one consistent active-state treatment across all patterns so navigation feels unified.

Modal, Toast & Overlay Set

10/30

You are a UX engineer who builds overlay and feedback components. <context> I need a set of overlay and feedback components rendered as one self-contained HTML file with inline CSS, previewable instantly as an artifact, shown in their open states on a sample page background. </context> <inputs> - Product context: [E.G. SAAS DASHBOARD] - Overlays I need: [E.G. CONFIRM MODAL, FORM MODAL, SIDE DRAWER, TOAST, ALERT BANNER, TOOLTIP, POPOVER] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a page that displays each overlay in context: a centered confirmation modal (title, body, cancel + confirm buttons) over a dimmed backdrop; a larger form modal; a right side drawer; a stack of toast notifications (success, error, info) with icons and a close button; an inline alert banner with variants; a tooltip; and a popover menu. Use realistic copy and clear visual layering. Show the page content faintly behind the overlays. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons. - Proper z-layering, backdrop, and elevation shadows; accessible roles/labels and focus styling. - Toasts and banners use icon plus color, not color alone, to signal status. </constraints> <format> Return the full HTML as an artifact, then explain the layering/elevation scale and how to trigger each overlay with minimal JS. </format>

Creates a set of modals, toasts, drawers, and overlays shown in context as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to render every overlay open at once on one page so you can compare elevation and spacing side by side.

Design Systems & Settings

5 prompts

Design System Style Guide

11/30

You are a design-systems lead who documents foundations as a visual style guide. <context> I need a one-page design-system style guide built as one self-contained HTML file with inline CSS, previewable instantly as an artifact that documents the foundations of a UI. </context> <inputs> - Brand name and personality: [E.G. CRISP, TRUSTWORTHY FINTECH] - Primary, accent, and neutral colors: [HEX OR DESCRIBE] - Typeface preference: [E.G. INTER, A SERIF DISPLAY] - Component examples to include: [E.G. BUTTONS, INPUTS, CARDS] </inputs> <task> Build a style guide with clearly titled sections: a color palette (primary, accent, neutrals, semantic success/warning/error) shown as swatches with names and hex; a type scale (display through caption) with live specimens; a spacing scale shown as labeled blocks; a radius and shadow/elevation scale; an icon-style note; and a small components preview (a button row, an input, a card) using these tokens. Make it feel like a real internal doc. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Every token is named and shown live; accessible contrast across swatches and text. - Drive components from CSS custom properties defined once at the top. </constraints> <format> Return the full HTML as an artifact, then output the full token list as CSS custom properties I can paste into a project. </format>

Builds a visual design-system style guide documenting color, type, spacing, and tokens as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to define all tokens as CSS variables at the top so the guide doubles as a real, paste-ready theme file.

Account Settings Page

12/30

You are a product designer who builds account and settings interfaces. <context> I need an account settings page built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product context: [E.G. SAAS TOOL] - Settings sections: [E.G. PROFILE, PASSWORD, NOTIFICATIONS, BILLING, DANGER ZONE] - Fields per section: [DESCRIBE] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a settings page with: a left sub-nav listing each section with an active highlight, and a main panel for the active section. Render a profile section with avatar upload, name and email fields, and a save button; show grouped form rows with labels, helper text, and inline save/cancel actions. Include a notifications section with toggle rows, a billing summary card, and a destructive danger-zone card (delete account) clearly separated with warning styling. Use realistic content. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Settings rows are aligned and scannable; toggles and inputs are accessible with real labels. - Danger zone is visually distinct (red accent, confirmation affordance); clear focus states. </constraints> <format> Return the full HTML as an artifact, then describe the settings-row pattern and how to add new sections. </format>

Generates an account settings page with sub-nav, grouped form rows, toggles, and a danger zone as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to make the danger zone visually heavier than everything else so destructive actions never get clicked by accident.

Team & Permissions Settings

13/30

You are a product designer for B2B SaaS admin and access-control screens. <context> I need a team and permissions settings screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product context: [E.G. PROJECT TOOL, ANALYTICS PLATFORM] - Roles: [E.G. OWNER, ADMIN, MEMBER, VIEWER] - Sample members: [NAMES, EMAILS, ROLES, STATUS] - Brand vibe: [DESCRIBE] </inputs> <task> Build a team management screen with: a header showing team name and seat usage with an invite button; an invite bar (email input, role select, send); a members table with avatar, name, email, a role dropdown, status badge (active / invited / suspended), and a row actions menu; and a roles-and-permissions reference card or matrix mapping each role to capabilities (with checkmarks). Show a pending invite row and a few active members with different roles. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Table is scannable with clear status badges and accessible role selects; row hover and focus states. - Permissions matrix is legible with checkmarks/dashes, not color alone. </constraints> <format> Return the full HTML as an artifact, then explain the member row structure and the role-to-permission mapping. </format>

Builds a team and permissions settings screen with a members table and a role matrix as a previewable artifact.

๐Ÿ’ก

Pro tip: Give Claude the exact role names and their capabilities so the permissions matrix reflects your real access model.

Theme & Appearance Settings

14/30

You are a product designer who builds theming and personalization controls. <context> I need a theme and appearance settings panel built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, ideally with a live preview area. </context> <inputs> - Product context: [E.G. NOTE APP, DASHBOARD] - Theme options: [LIGHT / DARK / SYSTEM] - Accent colors to offer: [LIST OF 4-6] - Other options: [E.G. FONT SIZE, DENSITY, REDUCED MOTION] - Brand vibe: [DESCRIBE] </inputs> <task> Build an appearance settings screen with: a theme selector showing light/dark/system as selectable preview thumbnails; an accent-color swatch picker with the selected one highlighted; a density toggle (comfortable/compact); a font-size control; an accessibility toggle (reduced motion / high contrast); and a live preview card on the right that reflects the chosen accent and theme. Pre-select sensible defaults and make the selected options obvious. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Selected states are unmistakable (ring, checkmark); controls are accessible with labels and focus rings. - The preview card visibly uses the chosen accent color. </constraints> <format> Return the full HTML as an artifact, then explain how the accent choice maps to CSS variables driving the preview. </format>

Creates a theme and appearance settings panel with selectable previews and a live preview card as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to wire the accent swatches to a CSS variable so clicking one instantly recolors the live preview.

Integrations / Connected Apps Screen

15/30

You are a product designer who builds integration and marketplace screens. <context> I need an integrations / connected-apps settings screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product context: [E.G. CRM, ANALYTICS TOOL] - Integrations to list: [E.G. SLACK, GOOGLE, STRIPE, ZAPIER] - Categories to group by: [E.G. COMMUNICATION, PAYMENTS, AUTOMATION] - Brand vibe: [DESCRIBE] </inputs> <task> Build an integrations screen with: a header with title and a search box; category filter chips; and a responsive grid of integration cards. Each card shows a logo placeholder, app name, a one-line description, a category tag, and a connect/manage button reflecting connection status (connected shows a green check and a manage button; not connected shows a connect button). Include a 'connected apps' summary at the top and a few cards in each state. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Connected vs available states are visually clear; cards are uniform and scannable. - Accessible buttons and contrast; logo areas are labeled placeholder blocks. </constraints> <format> Return the full HTML as an artifact, then describe the card status pattern and how to filter by category. </format>

Generates an integrations directory screen with status-aware connect cards and filters as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude which integrations are already connected so it renders the right mix of connect and manage states.

Pricing & Onboarding

5 prompts

In-App Pricing & Plan Selector

16/30

You are a SaaS product designer who builds upgrade and plan-selection UIs. <context> I need an in-app pricing / plan-selection screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Plans and prices: [E.G. FREE, PRO 19, TEAM 49] - Key features per plan: [BULLETS] - Which plan to highlight: [E.G. PRO] - Billing toggle: [MONTHLY / ANNUAL WITH DISCOUNT] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a plan-selection screen with: a monthly/annual billing toggle that updates a 'save X%' badge, and a row of three pricing cards. Each card has plan name, price with cadence, a short positioning line, a feature list with checkmarks, and a CTA. Visually elevate the recommended plan (badge, ring, lift). Add a current-plan indicator on one card and a short FAQ or trust line below. Use realistic feature copy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Recommended plan is clearly emphasized without crowding the others; cards align on a shared baseline. - Accessible toggle and buttons; the annual discount math is shown. </constraints> <format> Return the full HTML as an artifact, then explain the emphasis hierarchy and what to A/B test on the recommended plan. </format>

Builds an in-app pricing and plan-selection screen with a billing toggle and an emphasized plan as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude which plan you want to win and it will tune the badge, ordering, and contrast to steer eyes there.

Multi-Step Onboarding Wizard

17/30

You are a product designer who builds first-run onboarding flows. <context> I need a multi-step onboarding wizard screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, shown on one representative step. </context> <inputs> - Product context: [E.G. PROJECT TOOL] - Onboarding steps: [E.G. WELCOME, ABOUT YOU, INVITE TEAM, CONNECT DATA, DONE] - The step to render in detail: [PICK ONE] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build an onboarding wizard frame with: a progress indicator at the top (numbered stepper or progress bar) showing completed, current, and upcoming steps; a centered card containing the current step's heading, a friendly one-line subhead, the step's inputs or option cards, and a back/continue button pair (continue is primary). For an 'about you' or 'choose a goal' step, render selectable option cards with one pre-selected. Add a 'skip for now' link. Keep it focused and welcoming. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Progress, selected option, and primary CTA are visually clear; accessible focus and labels. - Single focused action per step; no distracting nav. </constraints> <format> Return the full HTML as an artifact, then explain the stepper states and how the other steps would reuse this frame. </format>

Generates a multi-step onboarding wizard screen with a progress stepper and selectable options as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to keep one single primary action per step so users never wonder what to click next.

Welcome Empty State Dashboard

18/30

You are a product designer who specializes in first-run empty states that drive activation. <context> I need a welcome / first-run dashboard empty state built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product context: [E.G. CRM, ANALYTICS, NOTES] - The first 'aha' action: [E.G. CREATE FIRST PROJECT] - Setup checklist items: [3-5 STEPS] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a first-run dashboard with: a warm welcome header (greeting + the value the user is about to get); a prominent illustrated empty-state block with a single primary CTA for the first key action; a getting-started checklist card with 3-5 steps, each with a checkbox, label, and the first item highlighted, plus a progress count; and one or two muted placeholder widgets hinting at what the dashboard fills with once they start. Keep momentum and guidance front and center. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; illustration is a tasteful CSS/SVG placeholder. - One unmistakable primary action; checklist is accessible and shows progress. - Encouraging, specific copy; no generic 'no data' dead end. </constraints> <format> Return the full HTML as an artifact, then explain how the checklist and empty state push toward the activation action. </format>

Creates an activation-focused welcome empty-state dashboard with a setup checklist as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude the single action that makes users 'get it' and it will make that the loudest thing on the screen.

Empty States Collection

19/30

You are a product designer who crafts empty and edge states across an app. <context> I need a collection of empty and edge states built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, laid out as a gallery. </context> <inputs> - Product context: [E.G. SAAS APP] - States to cover: [E.G. NO DATA YET, NO SEARCH RESULTS, ERROR/404, ALL DONE, NO PERMISSIONS] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a gallery of empty-state panels, each in its own card: 'nothing here yet' (icon, headline, helpful subtext, primary CTA), 'no results found' (with a clear-filters action), an error/404 state (with retry and go-home), an 'all caught up' success state, and a 'no access' state (with a request-access action). Each uses a tasteful CSS/SVG illustration, encouraging copy, and the right action. Label each panel with its scenario. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; illustrations are CSS/SVG placeholders. - Each state has a clear primary action and supportive, specific copy; accessible contrast. - Consistent illustration style and spacing across panels. </constraints> <format> Return the full HTML as an artifact, then explain the shared empty-state anatomy (icon, headline, subtext, action). </format>

Builds a gallery of empty and edge states (no data, no results, error, success, no access) as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to give every empty state a real next-step action so none of them become a dead end.

Feature Upgrade / Paywall Modal

20/30

You are a SaaS product designer who builds in-product upgrade moments. <context> I need a feature upgrade / paywall modal built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, shown open over a dimmed app background. </context> <inputs> - Locked feature: [WHAT THEY HIT] - The value of unlocking it: [WHAT THEY GAIN] - Plan that unlocks it and price: [E.G. PRO 19/MO] - Proof or reassurance: [E.G. TRIAL, GUARANTEE, USAGE STAT] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build an upgrade modal over a faint app screenshot: a centered modal with a small lock/spark icon, a benefit-led headline naming what unlocking gives them, a short list of three things the upgrade includes (checkmarks), a price line with the cadence, a primary upgrade CTA, a secondary 'maybe later' link, and a small reassurance line (trial / cancel anytime). Write specific, value-first copy that doesn't feel pushy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons. - Proper backdrop, elevation, and focus styling; accessible roles and a visible close affordance. - Lead with the gain, not the restriction; specific copy, no hype words. </constraints> <format> Return the full HTML as an artifact, then explain the value framing and what to A/B test on the CTA. </format>

Generates an in-product feature upgrade/paywall modal that leads with value as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to headline the benefit of unlocking, not the wall itself, so the modal feels like an offer, not a block.

Mobile UI

5 prompts

Mobile App Home Screen

21/30

You are a mobile UI designer who builds native-feeling app screens. <context> I need a mobile app home screen built as one self-contained HTML file with inline CSS, framed inside a phone mockup and previewable instantly as an artifact. </context> <inputs> - App type: [E.G. FITNESS, FINANCE, SOCIAL, FOOD] - Primary content blocks: [E.G. GREETING, STATS, FEED, QUICK ACTIONS] - Bottom-nav tabs: [E.G. HOME, EXPLORE, ADD, ACTIVITY, PROFILE] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a phone-framed home screen with: a status-bar strip, a header (greeting/avatar/notification icon), a hero summary or balance/stat card, a horizontal scroll row of quick-action chips or category cards, a vertical feed/list of content cards, and a fixed bottom tab bar with icons and labels (one active). Use realistic mobile content and generous touch targets. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons. - Phone frame with rounded corners; mobile-first spacing and tap targets of at least 44px. - Bottom nav fixed; active tab clearly indicated; accessible contrast. </constraints> <format> Return the full HTML as an artifact, then describe the mobile layout system and how the content scrolls within the frame. </format>

Builds a phone-framed mobile app home screen with hero card, feed, and bottom nav as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude the one thing users open the app to see and it will put that card right under the header.

Mobile Onboarding Carousel

22/30

You are a mobile UI designer who builds first-launch onboarding carousels. <context> I need a mobile onboarding carousel built as one self-contained HTML file with inline CSS, framed inside a phone mockup and previewable instantly as an artifact. </context> <inputs> - App type and core value: [DESCRIBE] - Three to four intro slides: [HEADLINE + ONE LINE EACH] - Final CTA: [E.G. GET STARTED, SIGN UP] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a phone-framed onboarding carousel showing one slide in detail: a large illustration area, a benefit headline, a one-line description, page-dot indicators (current dot active), a skip link top-right, and a next/get-started button. Render the structure so all slides share the same layout. On the final slide show a primary get-started CTA and a secondary sign-in link. Use warm, specific copy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; illustrations are CSS/SVG placeholders. - Phone frame, mobile spacing, large tap targets; active page dot clearly shown. - Accessible buttons and contrast; one clear action per slide. </constraints> <format> Return the full HTML as an artifact, then explain how slides share the frame and where swipe/dots would be wired. </format>

Creates a phone-framed mobile onboarding carousel with page dots and a final CTA as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to make each slide sell one benefit only so the carousel stays crisp instead of cramming features.

Mobile Checkout / Payment Screen

23/30

You are a mobile UI designer who builds high-trust checkout flows. <context> I need a mobile checkout / payment screen built as one self-contained HTML file with inline CSS, framed inside a phone mockup and previewable instantly as an artifact. </context> <inputs> - What is being bought: [PRODUCT OR PLAN + PRICE] - Order line items: [ITEMS, QUANTITIES, PRICES] - Payment methods: [E.G. CARD, APPLE PAY, PAYPAL] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a phone-framed checkout screen with: a top bar with back arrow and 'Checkout' title; an order summary card listing line items, subtotal, tax/shipping, and a bold total; an express-pay button row (e.g. Apple Pay) with an 'or pay with card' divider; a card form (number with brand icon, expiry, CVC, name) with mobile-friendly fields; a promo-code row; a trust line (secure padlock); and a sticky bottom 'Pay $X' button. Use realistic amounts. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons. - Phone frame; the total and pay button are unmissable; fields use correct input types and large tap targets. - Accessible labels and focus; trust/security cue near the pay button. </constraints> <format> Return the full HTML as an artifact, then explain the trust signals and the field choices that reduce checkout friction on mobile. </format>

Generates a phone-framed mobile checkout screen with order summary, card form, and sticky pay button as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to pin the total and pay button to the bottom so they stay visible no matter how the form scrolls.

Mobile Settings & Profile Screen

24/30

You are a mobile UI designer who builds settings and profile screens. <context> I need a mobile settings/profile screen built as one self-contained HTML file with inline CSS, framed inside a phone mockup and previewable instantly as an artifact. </context> <inputs> - App type: [DESCRIBE] - Profile info: [NAME, HANDLE/EMAIL, PLAN/STATUS] - Settings groups: [E.G. ACCOUNT, NOTIFICATIONS, PRIVACY, SUPPORT] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build a phone-framed settings screen with: a profile header card (avatar, name, handle, an edit button and maybe a plan badge); grouped settings lists with section headers, where each row has a leading icon, a label, and a trailing control (chevron, value text, or toggle); a notifications group with toggle rows; and a footer group with sign-out (destructive styling) and an app-version line. Use realistic labels and a few toggles in different states. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons. - Phone frame; grouped list styling with dividers; rows have large tap targets and accessible labels. - Toggles and destructive actions are visually clear; consistent iconography. </constraints> <format> Return the full HTML as an artifact, then describe the grouped-list row pattern so I can add more settings. </format>

Builds a phone-framed mobile settings and profile screen with grouped lists and toggles as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to group related settings under clear section headers so the list scans like a native iOS or Android screen.

Mobile Feed & Detail Pair

25/30

You are a mobile UI designer who builds content-feed apps. <context> I need a mobile feed screen paired with its detail screen, built as one self-contained HTML file with inline CSS, shown as two phone mockups side by side and previewable instantly as an artifact. </context> <inputs> - App type: [E.G. NEWS, RECIPES, SOCIAL, JOBS] - Feed item fields: [E.G. IMAGE, TITLE, META, LIKE/SAVE] - Detail screen content: [WHAT THE FULL VIEW SHOWS] - Brand color and vibe: [DESCRIBE] </inputs> <task> Build two phone frames: (1) a feed screen with a header, a search/filter bar, and a vertical list of content cards (image area, title, meta line, action icons), plus a bottom nav; and (2) the matching detail screen for one item with a back arrow, a hero image area, a title and meta, body content, an action bar (like/save/share), and a primary CTA. Keep the two screens visually consistent. Use realistic content. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG icons; image areas are labeled placeholders. - Both phone frames are mobile-first with large tap targets; consistent type and spacing across screens. - Accessible contrast and clear active/nav states. </constraints> <format> Return the full HTML as an artifact, then explain how the feed card maps to the detail screen and the shared mobile tokens. </format>

Creates a paired mobile feed and detail screen in two phone frames as a previewable artifact.

๐Ÿ’ก

Pro tip: Hand Claude one detailed feed item and ask it to carry the exact title and meta into the detail screen so the pair feels connected.

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

Dark Mode & Visual Polish

5 prompts

Dark-Mode SaaS Dashboard

26/30

You are a UI designer who specializes in refined dark-mode interfaces. <context> I need a dark-mode SaaS dashboard screen built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - Product and what it tracks: [DESCRIBE] - Top KPIs: [3-4 METRICS] - Accent color for the dark theme: [E.G. ELECTRIC BLUE, VIOLET] - Widgets to include: [E.G. CHART, LIST, TABLE] - Vibe: [E.G. SLEEK, TECHNICAL] </inputs> <task> Build a dark dashboard with: a dark sidebar (logo, nav items, active glow), a top bar, a row of KPI cards on elevated dark surfaces with a colored accent on each value, a featured chart drawn in CSS/SVG with a glowing accent line, and two secondary widgets (a ranked list and a table). Use a layered dark palette (background, surface, raised surface) rather than flat black, and apply the accent sparingly for emphasis. Use realistic numbers. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; no chart libs. - Use elevation via surface lightness and subtle borders, not heavy shadows; meet WCAG contrast for text on dark surfaces. - Accent color used purposefully, not everywhere; clear focus states. </constraints> <format> Return the full HTML as an artifact, then list the dark-palette tokens (bg, surface, raised, text, accent) and the contrast logic. </format>

Builds a refined dark-mode SaaS dashboard with layered surfaces and a glowing accent as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to use layered grays for elevation instead of pure black so the dark UI reads as depth, not a void.

Light & Dark Theme Toggle Demo

27/30

You are a front-end engineer who builds themeable interfaces. <context> I need a single screen that demonstrates a working light/dark theme toggle, built as one self-contained HTML file with inline CSS and a tiny bit of JS, previewable instantly as an artifact. </context> <inputs> - Screen to theme: [E.G. A SETTINGS PAGE, A CARD GALLERY] - Accent color: [HEX OR DESCRIBE] - Default theme: [LIGHT / DARK] - Vibe: [DESCRIBE] </inputs> <task> Build a representative screen (header, a few cards, a form control, buttons, a chart or stat) plus a theme toggle in the header. Drive both themes entirely from CSS custom properties, swapped by toggling a data-theme attribute on the root with minimal JS. Ensure both themes look intentional and meet contrast, and animate the transition smoothly. Render in the chosen default theme so the toggle visibly flips everything. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; minimal vanilla JS for the toggle only. - All colors come from CSS variables defined for both themes; no hardcoded per-element colors. - Both themes are accessible (contrast, focus rings); smooth, non-jarring transition. </constraints> <format> Return the full HTML as an artifact, then list the CSS variables for both themes and explain the toggle mechanism. </format>

Creates a working light/dark theme toggle demo driven by CSS variables as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to define every color as a CSS variable for both themes so adding a third theme later is a copy-paste.

Glassmorphism Card UI

28/30

You are a UI designer known for tasteful glassmorphism and depth. <context> I need a glassmorphism-style UI panel set built as one self-contained HTML file with inline CSS, previewable instantly as an artifact. </context> <inputs> - What the panels show: [E.G. WEATHER, MUSIC PLAYER, STATS, LOGIN] - Background vibe and colors: [E.G. PURPLE-TO-PINK GRADIENT, MESH] - Accent color: [DESCRIBE] - Mood: [DESCRIBE] </inputs> <task> Build a scene with a rich gradient or mesh background and two to three frosted-glass cards floating on it: a primary card (e.g. a stat or now-playing panel) and supporting cards. Each uses a translucent background, backdrop blur, a subtle 1px light border, soft inner highlight, and gentle shadow for depth. Include real content (numbers, controls, text) so it reads as a usable UI, not just a visual. Keep type crisp and legible over the blur. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only. - Glass effect via backdrop-filter with a fallback; ensure text stays readable (contrast) over the blur. - Restrained, elegant depth; accessible focus states on any interactive element. </constraints> <format> Return the full HTML as an artifact, then explain the glass recipe (blur, border, highlight, shadow) and the readability safeguards. </format>

Builds a tasteful glassmorphism card UI with frosted panels over a gradient as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to keep text on a slightly more opaque layer so the glass stays beautiful without hurting readability.

Login & Auth Screen Set

29/30

You are a UI designer who crafts polished authentication screens. <context> I need a set of authentication screens built as one self-contained HTML file with inline CSS, previewable instantly as an artifact, arranged as a small gallery. </context> <inputs> - Product name and vibe: [DESCRIBE] - Auth methods: [E.G. EMAIL/PASSWORD, GOOGLE, SSO, MAGIC LINK] - Brand color and theme: [LIGHT OR DARK, ACCENT] - Side panel content: [E.G. TAGLINE, ILLUSTRATION, TESTIMONIAL] </inputs> <task> Build three auth screens sharing one design language: (1) a sign-in screen with a split layout (branded visual panel on one side, form on the other), email + password fields, a remember/forgot row, a primary sign-in button, social/SSO buttons, and a 'create account' link; (2) a sign-up screen; and (3) a forgot-password screen with a single email field and a send-reset button plus a 'back to sign in' link. Keep spacing and components consistent across all three. Use realistic copy. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only, inline SVG for social icons. - Accessible labels, visible focus rings, valid input types, and clear primary-vs-secondary buttons. - The branded side panel collapses gracefully on mobile; consistent components across screens. </constraints> <format> Return the full HTML as an artifact, then explain the shared auth-form pattern and the responsive split-layout behavior. </format>

Generates a consistent set of sign-in, sign-up, and forgot-password screens as a previewable artifact.

๐Ÿ’ก

Pro tip: Tell Claude to build the form once and reuse it across all three screens so the auth flow feels like one product.

Micro-Interactions Showcase

30/30

You are a motion-minded UI engineer who designs delightful micro-interactions. <context> I need a micro-interactions showcase built as one self-contained HTML file with inline CSS (and minimal JS only if needed), previewable instantly as an artifact, laid out as a gallery of interactive specimens. </context> <inputs> - Brand color and vibe: [DESCRIBE] - Interactions I want: [E.G. BUTTON PRESS, TOGGLE, LIKE/HEART, COPY-TO-CLIPBOARD, SKELETON LOADER, SUCCESS CHECK, HOVER CARD] - Theme: [LIGHT / DARK] </inputs> <task> Build a gallery where each specimen is a labeled card demonstrating one interaction with real CSS animation: a button with a satisfying press and ripple, an animated toggle switch, a heart/like that pops and fills on click, a copy button that swaps to a checkmark, a loading skeleton with shimmer, an animated success checkmark, a spinner, and a card with a smooth hover lift. Keep animations quick, eased, and purposeful. Respect prefers-reduced-motion. </task> <constraints> - One self-contained responsive HTML file; Google Fonts only; vanilla JS only where an interaction truly needs it. - Animations are short and eased (not bouncy/distracting); include a prefers-reduced-motion fallback. - Each specimen is labeled and accessible (focus states, ARIA where relevant). </constraints> <format> Return the full HTML as an artifact, then explain the timing/easing choices and how to reuse each interaction. </format>

Creates an interactive micro-interactions showcase with animated buttons, toggles, and loaders as a previewable artifact.

๐Ÿ’ก

Pro tip: Ask Claude to keep every animation under ~250ms and add a reduced-motion fallback so the polish never feels gimmicky.

Frequently Asked Questions

Yes. Each prompt tells Claude to return a self-contained HTML file with inline CSS, which renders as a live artifact you can see and click immediately. You get a real, styled screen, not a written description of one.
No. You fill in the bracketed inputs in plain language and Claude writes all the HTML and CSS. You can preview the result instantly and copy the code into a project later, but you never have to write any of it yourself.
Fill in the brand color, vibe, and accent inputs in each prompt. For tighter control, ask Claude to drive everything off CSS variables, then change two or three values to retheme the entire screen at once.
Yes. Most prompts end by asking Claude to list its design tokens (color, spacing, type scale, radius). Start with the Design System Style Guide prompt to define those tokens, then ask later prompts to reuse them so all your screens stay consistent.
The prompts require responsive, mobile-first layouts, accessible contrast, real form labels, and visible focus states. The mobile prompts also frame the screen in a phone mockup with large tap targets so you can judge the real handheld experience.

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.