What Is Kombai and What Does It Do?

Kombai is an AI design engineer for building websites and product UIs. It handles design and production-ready frontend code in the same loop, and it's aimed at developers and product teams who need to both design an interface and ship it. It runs on macOS, Windows, Linux, VS Code, and Cursor, and reports 600K+ installs.

The problem it targets is specific: AI outputs tend to repeat generic design choices across very different tasks, while also missing the code patterns already established in large repositories. Kombai claims to fix both ends of that.

What Kombai actually does

Two capabilities define the product:

• Design that stands out. A "taste agent" identifies the important design decisions for each task and makes deliberate choices instead of falling back on AI defaults. It considers information architecture, structure, style, content, and motion, and draws on a gallery of 20k+ curated pages and sections for inspiration.
• Code that fits in. Kombai reuses components, tokens, and hooks from your repo, npm package, or Storybook, and carries them into new work. It supports 400+ libraries with built-in best practices.

The stated principle is "creative on open decisions, consistent with your brief and repo" — meaning it improvises where nothing is decided yet, and conforms where your codebase already has an answer.

How the workflow is structured

Canvas-based iteration

You try different ideas on a canvas before anything touches production code. From there you can:

• Run parallel agents in one or many canvases
• Edit text, styles, and layout of any element precisely
• Generate targeted variations or complete redesigns with AI
• Work with live HTML, states, and animations

Following what's already decided

Kombai reads design and code decisions from your repo, Figma, Storybook, or websites, and carries them forward. Two mechanisms do this:

Model flexibility

You're not locked to one model. The interface lists options including Anthropic Opus, Anthropic, xAI's Grok, Moonshot AI's Kimi, and OpenAI's image model, plus an "Auto" setting. Kombai states its approach works "even with lower-cost models," so model choice is a cost/quality dial rather than a hard dependency.

Who it's for

Kombai fits you if:

• You need to design a website or product UI and ship the frontend, not just produce mockups
• You work in a large repo where consistency with existing components, tokens, and hooks matters more than novelty
• You want to explore several design directions in parallel before committing to one
• You use VS Code or Cursor as your primary editor

It's a weaker fit if you only need static design files with no code output, or if you're working outside a codebase with established patterns to conform to.

What to check before adopting

• Pricing and plan limits aren't covered here — see the pricing page for current terms.
• Platform support is broad (macOS, Windows, Linux, VS Code, Cursor), but confirm your specific editor and OS combination.
• Repo integration is central to the value proposition, so the practical test is whether it correctly picks up your components and tokens on a real task, not a demo one.

The fastest way to judge it is to point it at one real feature in your own repo and see whether the output reuses your existing patterns or invents new ones.