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.

I ve been using Pencil.dev for a few days and honestly it s a big paradigm shift for how fast you can explore UI. I'm loving it!!

One thing I bumped into: I still need to move some screens into Figma to polish details, collaborate, and keep everything in the same place as the rest of our design work.

Hey Product Hunters!

When my wife Noa and I heard that MTV was officially shutting down, it felt like the end of an era. As 90s kids, we missed that specific "linear" experience the joy of just turning on the TV and being surprised by a music video without an algorithm getting in the way.

When I first set up OpenClaw, I ran into a big problem immediately.

I spent $250 on my first day doing what felt like harmless testing.

Nothing production. No customers. Just me trying things like:

• Summarize this Slack thread

• Give me a morning digest

• Explain this error log

• Pull action items from the last N messages

• A couple Telegram alerts

Over the last year, I ve been experimenting more with local-first patterns , apps that prioritize offline functionality and sync later instead of depending on constant server calls.

What used to feel experimental now feels surprisingly stable. Faster UI, fewer loading states, and a smoother user experience overall.

I rebuilt a small side project recently with a local-first approach, and the difference in responsiveness was noticeable. But it also introduced new challenges around conflict resolution and state consistency.

It makes me wonder:

Hi ProductHunt community,

This term has been coined by someone and there are already more than 80 products that you could put in this category. Looking at the numbers, it's growing pretty fast.

I didn t build our internal compliance tracking tool the traditional way.

I vibecoded it.

Instead of long PRDs, heavy sprint planning, and weeks of back-and-forth, I stayed close to the problem and built in tight feedback loops shipping small, observing behavior, and iterating fast.

The flow was simple:

As a data engineer who has little experience in full-stack software development, I ve been experimenting with vibe coding tools to move fast in the early stages.

My flow looked like this:

Prototyped the main UI in V0 (after 300+ iterations/conversations back and forth)