Dipanjan Dey releases Kombai 2.0, an AI tool that auto-syncs design canvas changes back to the codebase

Incredible. The best design work doesn’t happen in a chat box.

The fact that you can generate motion assets inside the canvas skips your image-gen hops.

Super cool that changes here get synced back to your codebase.

Kombai 2.0 just announced an AI design engineer.

So product taste, UI design, and real code will be one shared workflow.

Most AI coding tools can produce working code, but they often miss spacing, hierarchy, motion, visual polish, and the tiny interface choices.

The time has come with AI, when the design-to-engineering handoff should vanish when one AI design engineer understands both the interface and the code.

@rohanpaul_ai the design-engineer framing is the right call. generating the UI is mostly solved — knowing which of the 5 versions is actually good still isn't. taste is the one layer that hasn't been automated, and probably won't be soon.

@Scobleizer @Dipanjan_Dey Good morning

@rohanpaul_ai Spacing, hierarchy, motion, visual polish: the tiny interface choices are where I stop being impressed by fluent code. An AI design engineer is cute; an AI that knows when the button feels wrong is where humans get nervous. 👀

@Scobleizer @Dipanjan_Dey Integrating design and code in AI tools improves output quality. Marketing platforms benefit when agents produce both functional and tasteful customer experiences

@Scobleizer @Dipanjan_Dey good morning Robert

@kimmonismus this is huge, having everything synced to the codebase saves so much back and forth

@kimmonismus Makes iteration way faster when assets are in-canvas and sync to code

@rohanpaul_ai @rohanpaul_ai curious to see if it really nails the ‘tiny interface choices’, those always make or break the UX for me

@rohanpaul_ai The non-coder lesson here is that AI design tools still need a review loop. Generate the UI, then check it like a user: first action obvious, copy understandable, empty states handled, mobile usable. That checklist matters more than the prompt.

@sureshkanbu @rohanpaul_ai ... and wait till we get to voice. it's a whole other beast.

I'm thikning the future of UI is "cards" where the JSON payload has the data, the interaction, and the preferred UI style. And leaving it to the Agent to lay it out as it sees fit.

@rohanpaul_ai Are you sure it understands hierarchy and motion, or is it just interpolating patterns? Interpolation isn't taste, no matter how polished the output looks.

@rohanpaul_ai finally someone kills figma

@Scobleizer @Dipanjan_Dey Hope you are doing great

@kimmonismus Design tools that actually understand the codebase, that's been the missing piece forever

@rohanpaul_ai Yes. "Working code" was never the whole problem. Spacing, hierarchy, interaction grammar, state logic. One latent object, not two jobs.

@Scobleizer @Dipanjan_Dey The “blah” AI taste is real — sharper design defaults would save builders a lot

@kimmonismus Linking design space with codebase slashes redundant back and forth editing work.

@vveerrgg @rohanpaul_ai cards + agent-rendered layout is such a compelling model. structured intent, dynamic surface. the UI becomes a runtime artifact rather than a design artifact