How does Kombai avoid generic AI design output?

Kombai avoids generic AI design by inserting a "taste agent" between the task and the output. Instead of letting the model fall back on statistical defaults, the taste agent identifies which design decisions actually matter for a given task — type scale, accent contrast, hero composition, hover behavior, scroll reveals — and makes deliberate choices for each one. The result is meant to be creative on open decisions while staying consistent with your brief and repo. This applies when you're generating websites or product UIs and want output that doesn't look like every other AI-generated page.

The mechanism: decide first, generate second

The core problem Kombai names is that AI outputs "repeat generic design choices across very different tasks." A landing page for a fintech product and one for a game studio tend to converge on the same layout, spacing, and color instincts because the model reaches for the most probable answer.

Kombai's approach is to break that pattern at the decision level:

• Identify the key decisions for the specific task rather than generating the whole page in one pass.
• Make a high-quality choice for each instead of accepting the AI default.
• Stay creative on open decisions — the parts your brief doesn't constrain.
• Stay consistent with your brief and repo — the parts that are already decided.

The page describes this as "Creative on open decisions. Consistent with your brief and repo." That split is the whole idea: freedom where nothing is fixed, discipline where something already is.

What the taste agent actually considers

Kombai states the taste agent weighs five dimensions when making those choices:

The page illustrates this with concrete decisions pulled from different sources — "Setting the type scale" from a design system, "Checking accent contrast" from WCAG, "Composing the hero section" from inspirations, "Tuning hover interactions" from the repo, "Choosing the scroll reveals" from inspirations. Each decision draws on the source that should govern it, rather than one blanket style.

Where the inspiration comes from

Kombai draws on 20k+ curated pages and sections for design inspiration. This is the counterweight to "AI defaults" — instead of regressing to the mean of its training data, it references a curated set of pages and sections when composing things like hero sections and scroll reveals.

Why this matters beyond aesthetics

The same page frames the problem as two-sided: AI outputs "repeat generic design choices across very different tasks, while missing the code patterns already decided in large repos." So generic output isn't only a visual problem — it's also a consistency problem. Kombai addresses the second half by reusing components, tokens, and hooks from your repo, npm package, or Storybook and carrying them into new work, and by understanding decisions already made in your repo, Figma, Storybook, or websites.

That's why the tagline is "Designed to stand out. Built to fit in." Standing out is the taste agent's job on open decisions; fitting in is the repo-context job on decided ones.

What this means in practice

If you're evaluating Kombai for this specific concern, the useful question isn't "does it produce good design" in the abstract — it's whether the decisions it treats as open match the ones you'd want varied, and whether the sources it pulls from (your design system, repo, Storybook, Figma) are ones you've actually set up. The taste agent can only be consistent with decisions that exist somewhere it can read.

Kombai is available for macOS, Windows, Linux, VS Code, and Cursor, with 600K+ installs reported on the page. Pricing details are listed at kombai.com/pricing.