Google Stitch supports 550 monthly UI generations with HTML, React, and Figma exports

• heyrimsha's Stitch thread resurfaced Google Stitch as a free Google Labs product that offers 550 UI generations per month and runs on Gemini 3.1 Pro.
• According to heyrimsha's setup note, Stitch only needs a Google account and exports HTML, CSS, Tailwind, React, and Figma files from each screen.
• The prompt pack in heyrimsha's landing page example, heyrimsha's admin dashboard example, and heyrimsha's auth flow example shows Stitch working across marketing pages, desktop dashboards, and multi-screen mobile flows.
• heyrimsha's onboarding flow example and heyrimsha's empty state example suggest the tool is better at connected product surfaces than one-off hero shots.
• In the main HN discussion, commenters described a second step: exporting the design system into Claude Code or Claude Design, then using that output as the handoff into implementation.

You can try Google Stitch with a Google account, browse the HN discussion around Claude Design, and steal the best part of heyrimsha's thread: the prompts are written like mini creative briefs, with layout, color, components, and state details packed into a few lines.

The practical hook is not just prompt-to-mockup. It is prompt-to-assets you can move.

According to heyrimsha's setup note, Stitch exports HTML, CSS, Tailwind, React, and Figma files directly from every screen. That puts it in an awkwardly useful spot between an idea generator and a handoff tool.

The same post says Stitch is available through Google Stitch and only requires a Google account. For a Labs product, that is a very low-friction starting point.

The thread's strongest insight is simple: specificity buys fidelity.

Across the examples, the prompts keep repeating the same ingredients:

• Product type: project management tool, fintech app, AI writing tool
• Surface: landing page, dashboard, auth flow, pricing page
• Layout instructions: hero, sidebar, table, footer, bottom nav
• Visual direction: dark navy, white sections, blue accents, rounded corners
• Required components: pricing tiers, testimonials, OTP screens, filters, badges

That structure is visible in heyrimsha's landing page example, heyrimsha's admin dashboard example, and heyrimsha's auth flow example. The prompts read more like compressed design specs than vibe prompts.

The thread gets more interesting when it moves past single screens.

According to heyrimsha's auth flow example, one prompt can generate signup, login, forgot password, OTP verification, and biometric setup as one connected flow. In heyrimsha's onboarding flow example, the output spans four screens and preserves click-through prototype logic.

That matters because it pushes Stitch toward product scaffolding, not just marketing comps. The examples cover stateful app moments that usually get skipped in quick mockup tools.

The examples in the thread break into a useful starter set for creative teams and solo builders.

The pack surfaces at least six repeatable screen categories:

1. Landing pages, via heyrimsha's landing page example
2. Mobile dashboards, via heyrimsha's mobile dashboard example
3. Onboarding flows, via heyrimsha's onboarding flow example
4. Admin panels, via heyrimsha's admin dashboard example
5. Auth flows, via heyrimsha's auth flow example
6. Empty states and pricing pages, via heyrimsha's empty state example and heyrimsha's pricing page example

It is a practical inventory because these are the exact surfaces people end up rebuilding from scratch in Figma templates.

The most useful extra context came from people pairing design generation with coding agents.

In the main HN discussion, one commenter said Claude Design made it easier to explore multiple directions, then export to Claude Code with the design system attached. Another described a two-line prompt that wired Claude Design to a backend. A third said they were already pasting Stitch output into Claude Design to see what happened next.

Those comments do not say Stitch replaces Figma. They show a different workflow: generate a UI spec fast, export the artifacts, then hand them to a coding agent that can implement against an existing stack.