What's still missing from vibe coding tools?
by•
Vibe coding tools have been making huge improvements, but things can always get better.
What blockers are you still running into? What has no one solved yet? What do you wish you could do, but can't yet?
And if it's related to a specific product, be sure to '@' mention it. You might even get a response from one of the Makers!
1K views
Replies
It keeps breaking my existing code or randomly installing things I didn’t ask for.
It works well for brand-new projects, but when I’m working in an existing codebase, it often generates things using different conventions or logic and that really throws me off.
I wonder if this kind of issue can even be solved.
Also, I keep asking myself: can I really trust everything it says 100%?
I often have no idea where its suggestions are coming from.
I feel like I need more context or references like where this kind of code is used or what kind of project it’s suited for. Some kind of supporting data would really help.
If you're working with a popular language -- like top 5 language -- vibe coding works pretty well. But when working with a more niche or obscure language, like R, it leaves a lot to be desired.
Well - I found UI to be a fairly common problem. Especially getting it to move away from the generic styles. So I built UItoVIBE.com which gives a good starting point to generate unique UI styles for vibe coding apps. It's free, no logins and no spam. Would love the community to give us their feedback!