Uizard Prompts

Act as a senior product designer preparing input for Uizard Autodesigner 2.0. Write a conversational design brief for a [APP_TYPE] targeting [TARGET_USER], listing exactly these screens: [SCREEN_LIST]. For each screen specify the layout, key UI components, primary actions, and how screens connect in the user flow. Include a Theme Generator direction with keywords like [STYLE_KEYWORDS]. Keep it written so Autodesigner 2.0 can convert it into an editable, multi-screen clickable prototype.

You are a UX consultant. I will upload a screenshot of [COMPETITOR_NAME]'s [SCREEN_TYPE] into Uizard's Screenshot Scanner, which converts it into editable mockups. First, analyze this competitor screen for UX weaknesses in layout, hierarchy, and calls to action. Then give me a redesign plan for a [INDUSTRY] product serving [AUDIENCE], listing which components to change, add, or remove in the editable mockup, plus the success metric for each change: [SUCCESS_METRIC].

You are a product manager with hand-drawn wireframes on paper for a [PRODUCT_TYPE] serving [AUDIENCE]. Write guidance for using Uizard's Wireframe Scanner to digitize the sketches into editable mockups. Describe each sketched screen in structured detail: screen name, elements top to bottom, tap targets, and transitions to other screens: [SCREEN_DETAILS]. Add notes on what Autodesigner should refine, such as alignment, spacing, and [STYLE_PREFERENCE] theming, so the digitized result is presentation ready.

Act as a brand designer. I am building a [WEBSITE_TYPE] for [BUSINESS_NAME] in the [INDUSTRY] industry. Generate a Theme Generator brief using these keywords: [THEME_KEYWORDS]. Define the color palette, typography pairing, button styles, card treatments, and spacing rhythm the theme should apply across all Uizard screens. Also list what NOT to do: [AVOID_LIST]. The result must feel [BRAND_FEEL] and appeal to [TARGET_AUDIENCE].

You are a conversion optimization specialist. I will run Uizard's Focus Predictor on my [PAGE_TYPE] for [BUSINESS_NAME] to get a predictive attention heatmap. Write a review checklist for interpreting the heatmap: what it means if attention concentrates on [ELEMENT_A] versus [ELEMENT_B], which hotspots indicate the CTA is visible enough for [AUDIENCE], and 5 layout fixes to try if the hero gets less than [ATTENTION_THRESHOLD] of predicted focus. Include how to re-run the predictor after each fix and compare results.

Act as a UX writer. Generate the full microcopy set for a [APP_TYPE] serving [AUDIENCE] that I will build with Uizard and polish using Text Assistant. Cover: onboarding headlines and subheadlines for [ONBOARDING_STEPS] steps, empty states for [EMPTY_STATE_CASES], button labels, form validation messages, and error toasts. Tone: [TONE]. Every line must be short, actionable, and consistent with a [BRAND_PERSONALITY] brand voice. Flag any copy that should be A/B tested.

You are a startup founder with no design skills using Uizard for a [STARTUP_NAME] landing page targeting [INVESTOR_TYPE] and [CUSTOMER_SEGMENT]. Write the full input package: hero headline and subhead, 3 proof points for [KEY_METRICS], feature sections mapped to customer pain points: [PAIN_POINTS], pricing table tiers: [PRICING_TIERS], and a FAQ of 5 objections. Structure it so Autodesigner 2.0 generates an editable multi-section website, ready for Screenshot Scanner comparison against [COMPETITOR_NAME].

Act as a marketing designer. Plan a campaign microsite for [CAMPAIGN_NAME] promoting [OFFER] to [AUDIENCE]. Define each page: landing, offer details, signup, and thank-you, with sections, CTAs, and form fields per page: [PAGE_SPECS]. Specify the conversion goal: [CONVERSION_GOAL] and the visual style keywords for Theme Generator: [STYLE_KEYWORDS]. Format everything so I can paste it into Uizard and get editable screens, then use Focus Predictor to validate CTA visibility.

You are a design lead preparing a Uizard Pro handoff with React and CSS export for developers. Write the handoff document for a [APP_TYPE] with [SCREEN_COUNT] screens: component inventory with naming conventions: [NAMING_CONVENTION], responsive breakpoints: [BREAKPOINTS], interactive states to preserve (hover, loading, empty, error): [STATES], and design tokens (colors, type scale, spacing): [TOKEN_NOTES]. Note which parts developers should rebuild manually versus keep from the generated React/CSS, given Uizard output is a starting point.

Act as a product designer customizing a Uizard web app template for a [SAAS_PRODUCT] dashboard serving [USER_ROLE]. Specify which template sections to keep, remove, or restyle: [TEMPLATE_CHANGES]. Define the dashboard widgets needed: [WIDGET_LIST], the data each shows: [DATA_POINTS], and the empty and error states for each. Add a Theme Generator keyword set: [STYLE_KEYWORDS] matching [BRAND_FEEL]. Output an edit checklist I can apply screen by screen in the editable Uizard editor.