UXPin Forge - Generate UI from your design system, not around it
by•
AI that generates UI your design system would approve.
Forge works inside UXPin with your real components—MUI, shadcn/ui, Ant Design, or your own—so you can iterate fast and ship clean JSX. No rebuilding, no workarounds.
Replies
UXPin Merge
Congrats on the launch team, this looks like an unbelieve leap from the component creator.
@julia_prus1 thanks!!
UXPin Merge
@julia_prus1 Thanks! It's been a fun road
How does the URL-to-UI feature work? Can I paste any website?
@thomas_dupuy2 you sure can!
You can ask it to replicate the URL so you can have an editable UI to work with, or you can use a URL for inspiration for your own design.
UXPin Merge
@thomas_dupuy2 You can see it in action here: https://focusee.imobie.com/share/14013b5c6d15448698b2f7fe26ff0cca
@uxpinjack Awesome! Exactly what I was looking for
UXPin Merge
this is awesome team! Congrats on the launch
@sriya_vipin thanks Sriya!
Claude Design also creates a design system and much of the description. How is your product different / better?
@natalia_iankovych sorry for the late reply 😅 The difference is architectural.
Claude Design reads your codebase and creates a design system by extracting visual patterns - colours, typography, spacing. Then it generates new elements styled to match those patterns. That's approximation.
Forge takes the opposite approach. Your actual React component library syncs from Git into UXPin. Forge can only use components that exist in your library - real props, real variants, real states. It doesn't create a design system from your code. It uses the one you already built.
Three practical differences that show up immediately:
1. Drift. Claude Design users this week reported wrong fonts, incorrect colours, and inconsistent spacing. Forge can't drift because it can't generate outside your library.
2. Refinement cost. Every edit in Claude Design (including spacing tweaks) routes through the AI and burns tokens. In UXPin, manual edits are standard design tools. No credits.
3. Output. Claude Design exports to PDF, PPTX, or hands off to Claude Code for interpretation. Forge exports production-ready JSX referencing your actual component imports. Developers ship it directly.
Both are useful tools built for different problems. Claude Design is great for quick visuals when you don't have a design system. Forge is built for teams that already have one and need AI that respects it.
@andrew_uxpin Yes, that’s a big problem in Claude Design. But I’m sure they’ll solve it quickly to work with legacy projects. Aren’t you worried about that? ;)
mailX by mailwarm
I love the focus on real behavior instead of just screens. It feels like a step toward closing the design → dev gap. But I'm curious as to how teams are adopting it alongside tools like Figma?
Is there a free trial? How long do we get to test it?
@ethel_aranjuez there sure is. We have a free trial of 14 days which can be extended by a further 7 days by booking a demo with our team.
I’ve tried a bunch of AI UI tools and most of them break when you try to use them for real
@teri_morgan2 That's because most of them generate to their own conventions. The output looks great in the demo. Then you try to use it with your actual components and it falls apart.
We took the opposite approach wehn building Forge - it starts from your components. The AI is constrained to what exists in your synced library, so the output works from the first generation, not after hours of fixing.
Curious what broke for you specifically? Happy to show how Forge handles the same scenario.
Finally something that doesn’t just generate random UI
@jolina_teniedo That's the whole point! AI should be constrained to your system, not freestyling. Glad it landed, let us know how you get on with it.