Subframe

Use it when

You need product UI that leaves the canvas as production React and Tailwind—especially when designers and engineers share one component source of truth, or when Cursor/Claude Code should read and edit the same design via MCP.

What it does well

• Visual editing that maps to deterministic React + Tailwind components—canvas changes are the code, not a separate export guess
• AI assists with pages, themes, and variants while keeping theme tokens and patterns as living context for agents
• MCP server so coding assistants can read pages, components, themes, and prototypes and implement into local repos
• Unlimited team members for review; Pro bills by editor seat and unlocks unlimited projects, pages, prototypes, and AI usage
• Custom fonts on Pro; Custom plan adds component import and longer version history when you outgrow Pro

Skip it when

• Free’s 1 project, up to 10 pages, 2 prototypes, limited AI, and 24-hour version history cannot cover a real product surface
• You need version history beyond Pro’s 7 days without Custom or external git
• Your deliverable is Figma-only handoff or a non-React / non-Tailwind stack
• You want a chat-only app builder rather than a visual, code-native UI editor
• You must import existing React components into the design tool—that is Custom-tier, not Free/Pro

Fits your workflow

Design on the Subframe canvas → refine with AI where useful → export or sync React + Tailwind into Next.js/Vite (CLI or manual), or connect MCP in Cursor/Claude Code to implement. Smoke-test on Free; move to Pro for unlimited pages/AI and custom fonts. Keep business logic in the repo—Subframe owns UI structure and components.