Wherever you code (online, CLI, or IDE), everyone has some love, hate or horror vibe coding stories, from building a prod-ready app in minutes to the whole repo got wiped. Would love to hear your story.

Building my app with AI tools, zero coding background. The magic part - I can ship features in hours. The scary part - I have no idea if the code is actually good.

Right now my "QA process" is:

- Does it work when I tap around?

- Did anything break that worked before?

Hey PH family.

Been part of this community for years now, and if there's one place to talk with builders, this is it.

AI dev tools are evolving crazy fast , every few weeks there s a new must-try for vibe coders.

Some people are building full products with @ChatGPT by OpenAI and @Replit , others swear by @Cursor and @Claude by Anthropic , and a few are mixing @Lovable + @v0 by Vercel + @bolt.new to ship apps in record time.

I ve been refining my own vibe stack lately, trying to find that sweet spot between speed, control, and creativity.
It made me wonder ,what does your setup look like right now?

I've been thinking about something.
We've gotten really good at using AI to generate working code, but we're not treating it like production code in terms of documentation.

Traditional developers spend significant time documenting their code because they know future them (or their teammates) will need to understand, modify, or debug it later. But with AI-generated code, we often just copy-paste and move on.

The problem:

You generate a perfect solution today.

Curious what's your preference: @bolt.new @Lovable @Replit @v0 by Vercel? or else?

On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit

I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.