Back to tips

How to Generate Multiple UI Design Variations With AI (2026)

Ask AI for several directions on named UI axes, compare them side by side as real screens, combine the best parts, then hand the winner to your coding agent.

How to get AI to generate multiple UI design variations (the short answer)

Ask for directions, not a design. Keep the real content and your design system fixed, give each option a different job (a different layout, hierarchy, navigation or density), and say "not color". That gets you options worth comparing. The step most answers skip is what happens next: compare the options side by side as real screens, then combine the best parts ("the header from variation 1 with the layout from variation 3"), fix the details directly, and only then have your coding agent build it.

Where you do it decides how easy that is. A chatbot gives you options in a thread. Claude Design, Google Stitch and Figma's agent put options on a canvas. In Subframe, agents build the variations you ask for as real pages side by side on a canvas, working in parallel so you can watch each page fill in. You combine them by asking or by dragging elements between pages, and the page you pick goes to your codebase as React and Tailwind, through your coding agent or Subframe's own agent (desktop app for macOS and Windows).

Making images, not screens? Use your image tool's own variation settings; this guide is about UI.

The steps:

  1. Fix what shouldn't change: real content, your design system, the screen's one job.
  2. Ask for a few directions, each on a named UI axis.
  3. Compare them side by side as real screens.
  4. Combine the best parts.
  5. Refine the winner with design control for precise edits.
  6. Hand the winner to your coding agent or engineers.

Why AI gives you one design, and why rewording the prompt doesn't fix it

Ask a model for "a dashboard" and it returns the most likely one. Ask for "a few variations" and you often get the same layout in new colors. Current answers to this question still treat it as a prompting problem: ChatGPT suggests asking for six named creative directions "side by side", and Gemini answers with image settings like Midjourney's permutations. Both get you more options. Neither helps you decide between them, or turn the winner into a screen in your app.

The deeper problem: most people can't describe the screen they want, but they recognize it when they see it. In our customer calls, a founder-engineer at an early-stage startup said, "I'm not even sure directionally what I want." An independent builder said, "I'll know it when I see it." Rewording the prompt asks you to describe the answer in advance. Reviewing options only asks you to react. (For the wider loop, see how to make your product look good without a designer.)

How to generate UI design variations, step by step

Step 1: Fix what shouldn't change

Options are only comparable if they differ where you're deciding. Pin down:

  • Real content: the actual columns, labels and copy, not placeholder text.
  • Your design system: colors, fonts and spacing in a file your agent reads, such as a DESIGN.md or CLAUDE.md. In Subframe, that's the project's Design Guidelines doc, marked "Always read by the agent".
  • The screen's one job, such as "help a support agent find the oldest open ticket fast".
  • Your starting point: a written brief, a screenshot, a pasted URL or, in Subframe's desktop app, a page captured from your running app as an editable design.

Step 2: Ask for a few directions on named UI axes

"Give me 4 variations" invites four near-identical screens. Give each option its own angle instead. Three or four is usually enough to compare at full size. Copy this and fill in the brackets:

Design the [screen] for [product]. Its one job: [job].
Use this content exactly: [paste real content].
Follow our design system: [file or doc].
Give me 4 directions that differ in layout and hierarchy, not color:
1. Table-first: dense rows, filters in a left sidebar
2. Card grid: more whitespace, filters in a top bar
3. Split view: list on the left, detail on the right
4. Your boldest take that still does the job
Label each one with the trade-off it makes.

In Subframe, send the prompt in Agent chat and name the directions you want to compare. Agents build the pages in parallel, side by side on the canvas, and each page fills in a section at a time while you watch. Attach a screenshot or mockup and they build pages that match its structure, using your Subframe components.

From Claude Code, install the Subframe plugin, which sets up the MCP server and agent skills in one step:

claude plugin marketplace add https://github.com/SubframeApp/subframe && claude plugin install subframe@subframe

Then ask Claude Code for the variations without leaving your coding agent. They land as pages in your Subframe project, side by side, so you open them in Subframe to compare and edit.

Step 3: Compare them side by side as real screens

This is where most workflows fall apart: the options sit in a chat thread or a row of thumbnails, and you compare them from memory. Put them next to each other at the same size, with the same content, and judge them against the screen's job rather than taste. Check what breaks first: long rows of real data, empty and error states, mobile width. Keep one or two; delete the rest.

In Subframe, each variation's tile in Agent chat jumps to its page on the canvas. The canvas is free-form: place pages wherever you want them, drag to select several at once, and hold Option (⌥) while dragging a page to duplicate it when you want to try a change by hand next to the original.

Step 4: Combine the best parts

Most guides skip this step, yet it's what people ask for. As one founder we spoke with put it: "I kind of like an element from this. Can we wrap it into that?" Name each part and its source:

Use the header from variation 1 with the layout from variation 3,
but keep the filter bar from variation 2.

In Subframe, send that as a follow-up in Agent chat, or combine by hand: drag an element from one page on the canvas to another.

Step 5: Refine the winner with design control for precise edits

Once the direction is right, change the exact element instead of regenerating the screen and losing what you liked. In Subframe, click any element on the canvas and edit it in the Inspector. To have the agent do it, select the element and ask Agent chat to change it; the agent edits exactly what you selected and leaves the rest of the page alone.

Step 6: Hand the winner to your coding agent or engineers

The design you picked is the spec; hand over the design, not a description of it. From Subframe:

  • Your coding agent, through MCP: copy the page's MCP link from the Export tab and ask Claude Code, Cursor or Codex to implement it and wire up the app logic.
  • Subframe's Agent chat: in the desktop app (macOS or Windows), connect your codebase and ask the agent to implement the page. It edits the files in your connected folder.
  • Copy the code: the Export tab has the page's React and Tailwind code, generated from the design without an LLM, so it matches what you approved.

Components sync one way, from Subframe to your code; pages are exported, and your engineers or agent add the business logic.

Other ways to do it

Prompt a chatbot (ChatGPT or Claude). Free and instant, and good for thinking through directions in words. But the options come back in a chat thread, and you rebuild the one you pick.

Claude Code alone. Ask for each layout as a separate page or a temporary toggle in the running app. It's the best fit for one decision in code you already have, but the options live in throwaway code, and each precise fix is another prompt.

Claude Design. Anthropic's help page suggests asking Claude to show you 2–3 options when you're unsure of a direction, and it now runs as an artifact template in any chat and in Claude Code (/design); the standalone site at claude.ai/design closes on December 14, 2026. You refine on the canvas, with inline comments or in chat, then hand the design to Claude Code. Choose it if you already live in Claude's apps. The difference: with Claude Design, Claude Code builds from a handoff; Subframe generates the page's React and Tailwind code from the design itself, and your agent integrates that code.

Google Stitch. Google Labs' AI design canvas. Its Agent manager works on several ideas in parallel, and you can ask by voice for things like three different menu options. It reads and writes a DESIGN.md for your design rules, and exports to Google's developer tools or through its MCP server. Choose it for fast, free-form exploration when you don't need the result in an existing codebase yet.

Figma. ChatGPT often names Figma Make for prototyping. For options side by side, Figma's agent in Figma Design (on paid plans) generates variations in parallel on the canvas from your connected design library, so your team compares them in the file they already use. Choose it if your team designs in Figma; the code still has to be built from the design.

v0. Vercel's builder generates a working app from a prompt, with a design mode for visual fine-tuning, GitHub sync and one-click deploys. Its homepage describes building one app you iterate on, not options side by side. Choose it for a standalone prototype you want live quickly.

What most guides on design variations miss

The most-cited results on this question teach the same trick (say a number, name what varies, fix the brand, pick one), which is step 2 above. Many of them, including the most-cited this month, are about images. They share four gaps:

  • They're about images. A screen varies on layout, hierarchy, navigation, density and states.
  • They stop at the pick. None explains how to combine parts of different options.
  • The winner stays a picture. None ends with the chosen design in your app.
  • They start from scratch. Few start from a screen you already have.

FAQ

How do I get ChatGPT or Claude to give me multiple design options instead of one?

Ask for a number of directions and give each an angle: "4 layouts: table-first, card grid, split view and your boldest take." Keep the content and brand fixed, and add "not color".

How many design variations should I ask for?

Three or four is usually enough range and few enough to compare at full size. Then ask for more versions of the one you like.

Why do my AI design variations all look the same?

"Variations" doesn't say what to vary, so the model keeps its most likely layout and changes colors. Name the axis for each option (layout, hierarchy, navigation or density) and add "not color".

What's the fastest way to try different UI layouts before asking Claude to build one?

Generate a few layouts side by side on a canvas, pick or combine, then hand Claude the chosen design. In Claude Code, use /design or the Subframe plugin, which puts the variations side by side in Subframe for you to compare, edit and send back to your codebase.

Can I combine parts of different AI design variations?

Yes. Name the part and its source: "the header from variation 1 with the layout from variation 3." Subframe's agent does this as a follow-up, and you can drag elements between pages on the canvas.

Can I generate variations of a screen in my existing app?

Yes. Start from a screenshot, a pasted URL or, in Subframe's desktop app (macOS or Windows), a page captured from your running app. From a screenshot, Subframe's agents build pages that match its structure, using your Subframe components, side by side so you can compare them.

Try it in Subframe

Describe a screen, or paste a screenshot of yours, and get the variations you ask for side by side on a canvas. Combine the best parts, fix the details with design control for precise edits, then send the page to your codebase through Claude Code, Cursor, Codex or Subframe's own agent. Try Subframe free.

Join thousands of builders.

Subframe lets you build stunning UI with beautifully crafted components and a drag-and-drop visual editor.