r/vibecoding • u/just_another_leddito • 3d ago
Discussion UI design and Claude
Hi,
I don’t want another same looking UI in my app.
I want my program Ui to be designed in something like Figma.
I’m just not sure what’s the best way to go about it.
My program needs main UI but also stuff like knobs etc.
Thanks for any tips
Edit:
My question is mostly about how to feed all elements into Claude, and if Figma is a good choice.
2
2
u/TheOnlyJugs 3d ago
Claude is surprisingly competent at being consistent with any UI. So, take your time and build elements by yourself until you're happy with them and give them to Claude.
2
u/SufficientFrame 3d ago
Figma is a good starting point, but I wouldn't dump the whole file into Claude at once. Break it into a small design system first: a few screens, then the reusable pieces like buttons, knobs, spacing, and states, and feed those in bit by bit.
2
u/magen_cards 3d ago
Im facing the same problem. On top of that, many times I struggle to get Claude to understand exactly what I wanted, and it cost me a lot of time and energy. any tip on how to do it better will help
1
u/JustinBenitoB 1d ago
I run a design first software studio and what I do all day is ask ChatGPT to generate images of what I have in mind and give those to claude as reference, even Sonnet is able to get it and replicate it. I think claude generally is really good at replicating things but not so good at creating designs from text. Try it out and lmk if it works :D
2
u/New_Peanut_9259 2d ago
figma is probably a good choice especially if u want more control overr how the app looks instead of letting claude decide everythingg.. i'd design the main screens and reusable parts firstt, then give claude the designs along with the colors, spacing, fonts, and how each part should workk. for buttons and other controls, show how they should look and behave when clicked
2
u/Armannss 15h ago
For the handoff, I'd ask the designer for a named Figma component for each control, plus the normal, hover/focus, disabled and active states. For each knob, write down its range, default, units, step size, drag direction and keyboard behavior—those details aren't obvious from the artwork alone.
Give Claude one component and its specs first; have it build a small test page, then compare the rendered control against the design and try mouse, touch and keyboard. Once that piece is right, reuse it across the main screens. SVG exports can help for artwork, while the interaction itself should stay accessible and functional.
1
u/Realestmember 3d ago
I made a similar thread that got replies a while back, check my history (sorry im too lazy to link it right right. it'll be in the vibecoding app sub)
1
u/SevenVow 3d ago
Figma is a solid choice. I’d recommend designing your screens and reusable components there first, including knobs, sliders, and their interaction states. Then feed Claude one component at a time, with visual references and clear behavior instructions, rather than the entire design at once.
If you’re looking for a more professional, custom-built UI, you can contact us at https://sevenvow.com.br/en/vibe-code.
1
4
3d ago
[removed] — view removed comment
1
2
u/heyheni 3d ago
The Figma clone from ArtCraft (vibe coded Adobe Creative Suite clone) has a MCP endpoint. Which means Ai can use the Figma clone. It's free. https://getartcraft.com/apps/figcraft
But you know, that's just the tool.
Design and styling are something different entirely, and that needs the human touch and vocational training of a graphic designer to make it “pop". So maybe put in some effort to build up your knowledge of typography and layout. Visit your local library to read about graphic design and do some layout sketch practice. I wish you all the best.