Vibe coding is real. 1 month later, Aura hits 15k MRR and 21.7k users.
I soloed this project from scratch and made a cursor for design. Our entire design team is using it daily and we don’t use Figma anymore. Here are a few tips for vibe coding your own app.
Don’t just vibe code, vibe design as well. Too many spend too little effort in design. AI likes to generate basic UIs, so make sure to provide templates, urls, images, figma, etc. Starting with a meh UI will permeate the rest of your app. That’s because AI uses the initial design as a blueprint. So, spend some time vibe designing components, styles, cards, buttons and use resources like 21st dev, tailwind, reactbits, uiverse, aura, etc.
Don’t just use Claude 4 Sonnet. 90% of my prompts are with Claude 4, but it’s not perfect. Sometimes, it gets blocked and repeat the same mistakes over and over. So I switch to Gemini 2.5 Pro or o3 for second opinions. I tried Opus but that didn’t solve harder problems, and the cost isn’t worth it.
Don’t expect to one-shot things. Those are the worst results because you won’t understand what the heck is going on. Instead, do incremental changes, read the logs and comments. Learn basic code and security. As your app gets more complex, this is even more crucial. Before you say that vibe coding apps are impossible when they’re big, Aura has 118k lines of code.
The context is in your brain. AI isn’t that good at knowing where things are. EVEN if you attach your entire codebase (costly!) or create rules, AI gets confused a lot. It doesn’t remember. 99% of the time, I prompt with a file or two attached. The best results I get are by starting with a simple file and let AI be the detective.
You gotta be creative at rephrasing/reframing your prompts. Most people quit at the first prompt. But often, you can only solve hard problems after the 3rd attempt. Know your vocabulary, seek alternatives, simplify your goals, make small jumps.