Skip to main content

Lamina vs Google Stitch

Google Stitch is an AI UI design canvas: prompts to screens, export to Figma or code. Lamina specs behavior in your repo and verifies implementation.

Curated by Aryan Iyappan · Updated 2026-07-13

Stitch outputs visual designs and DESIGN.md tokens. Lamina outputs run.yaml behavior contracts.

Who this comparison is for

You are in the right place if

  • You used Stitch to explore screens, then flows broke after implementation.
  • You exported Stitch code but gates and role rules were never specced.
  • The name design in Stitch made you expect product behavior specs.
  • Figma MCP plus Stitch export still ships happy-path-only checkout.

Context

Stitch excels at fast visual exploration: prompt a screen, refine in the canvas, export assets or code. That is valuable early in a feature. The gap appears at merge time when your agent implements screens without a behavior contract. Stitch DESIGN.md carries tokens and layout intent; it does not carry hold lifecycles or partner submit gates. Lamina fills the behavior layer in the same repo your agent already edits.

Common situations

Concrete cases from AI-shipping workflows. Each shows what the alternative handles and where a behavior contract helps.

Exported checkout screen without hold rules

Situation
Stitch generated a polished checkout with timer UI. After export, the agent wired Confirm pay without enforcing email verification or hold expiry.
What Google Stitch does
Stitch produced the visual pattern for a hold banner and payment CTA. Export gives you components, not domain rules.
What Lamina adds
run.yaml defines legal transitions: hold active, email verified, policy agreed, then pay. Verify walks the guest path on the live build.
Takeaway
Export Stitch UI, spec behavior with Lamina before merge.

Exploring partner dashboard layouts

Situation
You used Stitch to compare sidebar vs stepped onboarding layouts before picking one for implementation.
What Google Stitch does
Stitch is the right tool for layout exploration and stakeholder review in the canvas.
What Lamina adds
After you pick a layout, /lamina-design defines which steps exist and when submit unlocks, independent of the visual pattern.
Takeaway
Stitch for exploration; Lamina for rules once you commit to a flow.

Static marketing site only

Situation
Stitch mockups for a launch page with no auth, checkout, or role-specific UI.
What Google Stitch does
Stitch alone is sufficient through export and implementation.
What Lamina adds
Not needed until the site gains interactive product behavior.
Takeaway
No behavior layer required for static pages.

Comparison

Lamina vs Google Stitch for AI developers
DimensionGoogle StitchLamina
Primary jobGenerate high-fidelity UI from natural languageSpec states, flows, permissions
Layer in stackVisual design canvasHeadless product design skill
Primary outputScreens, DESIGN.md, exportable coderun.yaml + implement.md
Writes app source?Exports code you integrateNo
Behavior spec (states, flows, permissions)Layout intent, not domain state machinesPermission matrices and legal transitions
Durable in-repo artifactDesign exports in project.lamina/ contracts in git
Post-build verificationVisual iteration in Stitch canvas/lamina-verify persona walks
Repo and stack fitExport into your stackNative to your repo and agent
Best whenExploring layouts and visual direction fastShipping features with roles and gates
When you don't need LaminaStatic mockups or throwaway explorationNo production behavior rules needed
Compose with Lamina?Explore UI in Stitch, exportStitch → /lamina-design → implement → verify

Workflow

Lamina vs Google Stitch: recommended workflow
StepGoogle StitchLamina
1Prompt screens in StitchOptional: parallel /lamina-design for behavior
2Export to Figma or codeimplement.md guides agent merge
3Agent integrates visual componentsAgent enforces contract rules
4Visual QA in browser/lamina-verify on staging

When to use which

Lamina vs Google Stitch: when to use each
SituationGoogle StitchLamina
Choosing between two dashboard layoutsStitch explorationAfter layout is chosen
Production booking with timers and gatesStitch for UI chromeContract + verify required
Design system token draftStitch DESIGN.mdNot for tokens alone

Worked example

Inventory hold with countdown. Stitch can generate checkout UI with a countdown banner. Lamina specs hold timer rules, email verification gate, and cancellation consent before Confirm pay. HavenStay verify found pay enabled without verified email when the contract was skipped.

HavenStay demo walkthrough

Frequently asked questions

Stitch uses DESIGN.md. Is that the same as Lamina contracts?

No. DESIGN.md is visual tokens and layout notes. run.yaml is product behavior: actors, states, permissions, and recovery.

Does Lamina replace Stitch?

No. Lamina does not generate screens or run a design canvas.

Should I use Stitch, Figma MCP, or both with Lamina?

Use whichever visual handoff fits your team. Lamina sits after visual direction is chosen and before behavior-critical implementation.

Comparisons map stack layers, repo artifacts, and HavenStay demo examples. Updated when major tools change positioning.

Install in one command.

A headless product-design skill for your AI coding agent. Then run the design → implement → verify loop on your next feature.

Apache-2.0 · open source. Star on GitHub if Lamina saves you a loop.

npx skills install aryaniyaps/lamina

Works with your coding agent

  • Cursor
  • Claude Code
  • Codex
  • Gemini
  • Pi
  • and more