Video wird geladen...
Video konnte nicht geladen werden
We designed a UI kit for founders vibe-coding AI products. It sits on shadcn/ui, a solid foundation most of these tools already reach for. We've added our own visual direction and the UX patterns AI products need. Copy one prompt into Claude Code or Cursor and your prototype picks... show more
19,105 Aufrufe • vor 7 Tagen •via X (Twitter)
18 Kommentare

It's in beta. We'll keep adding patterns as studio work surfaces them. If you try it, we'd like to see the result. Send us what it did to your screens, good or bad.

the demo UI is bad even in the after view.

Its great A small thing I noticed is that AI chat section where the container width is more than the AI input box which feels a bit off. Why because in most AI apps the messaging container is of the same width as input box. I might be wrong but I think you should look into it.

Love this!

Thanks Phil! still a wip

I'm giving it a try right now on one of my projects...

i’ve found the handoff is the real test: a prompt that generates a nice screen still needs someone to walk the live path and catch where the next click becomes guesswork.

UI kits for AI products are becoming the default. shadcn base plus patterns agents actually need beats another pretty Figma dump.

Great work!

the focus on UX patterns for AI products is key, but founders need more than just visuals

Clean!

using shadcn/ui is a good choice, but it might limit unique branding for founders

the “one prompt” handoff is useful, but what happens when the prototype needs a pattern your kit doesn’t cover? i’d be curious to see which ai-specific ux decisions mattered most beyond shadcn’s defaults.

The kit is the moat. Most vibe-coded apps die on the last ten percent that looks off.

Great job! Love this and will definitely try it out

using shadcn/ui as a base is smart, it’s great for rapid prototyping

cool!

ok real question tho - if it sits on shadcn how much of the "visual direction" is actually yours vs just default shadcn styling
