Vibecoding
p/vibecodingBuild for the vibe, debug later
trending
Meir Davidov

7mo ago

Just quoted a client $43k to fix what AI built in 3 hours

Had a fascinating discovery call yesterday. Founder showed me their SaaS - built entirely with Cursor in one weekend. Stripe payments, auth, admin panel. Actually works great, they're at $11k MRR.

Then they opened the codebase.

Sean Hwang

11mo ago

Who here has fully vibecoded a profitable product?

On social media, we're constantly hearing about individuals who never knew how to code and were able to vibecode a product within a short period of time.

Whenever I come across these posts, I always wonder if their product is truly marketable and profitable. Or, they are just selling the dream.

Share your vibe coding stories

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.

Anyone else here using Pencil.dev?

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.

Vibe-analytics - is it a real thing?

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.

Syotoshi

2mo ago

How to go from an idea to a full-stack hosted website

For the past couple weeks I've been on my #indiehacking coding grind

All the tools out there to go from just vibecoding to actually launching can be quite overwhelming when just starting out

Slava Kochubey

2mo ago

Designer + Cursor + real problem = live SaaS. First time posting, excited to be here👋

I'm a UX designer and Product strategist. Not a fullstack developer.
And I just shipped a full SaaS product.
Here's how I did it.
I work as a UX and Product SaaS strategist and also run a remote digital agency Koylabs.
I always had product ideas but never the engineering background to build them myself. That changed this year when I started seriously experimenting with AI tools and vibe coding.
I picked a real problem I kept seeing with clients they wanted Google reviews on their website and every existing solution was clunky, complex and a bit dated. Simple problem. Clear market. So I decided to build the solution myself.
The stack:
Next.js + Supabase for the backend
Stripe for payments and subscriptions
Cursor as my AI coding environment
Vercel for hosting
What surprised me:
AI is incredible at boilerplate and repetitive logic
The hard parts were still hard embed systems, iframe height communication, Stripe webhook edge cases
Product thinking was my biggest advantage.
Knowing exactly what to build and what to leave out saved weeks
Vibe coding is real but you still need to understand what you're building
What I actually shipped:
Full auth and multi-tenant architecture
Stripe subscriptions with trials, webhooks and billing portal
A custom iframe embed system that works on Framer, Webflow, WordPress and any platform
Automated review sync
Four widget layouts
Start to launch: a few weeks.
The result is Review OS a simple clean way to show your Google reviews on your website. One embed code, done in under a minute. Only $9/month.
If you or someone you know needs this try it free for 7 days at www.reviewos.co 7 day free trial
And if you're thinking about building your own project follow along.
Give this tool a try and share your thoughts I'm looking forward to your feedback.
My next post will be a full playbook on how I did it, tools, process, mistakes and all.
What are you currently working on? Drop a comment would love to know.
Launching on Product Hunt this Wednesday would love your support

Sidra Arif

25d ago

Claude source code leak just showed how AI products really work… surprising or expected?

Came across the recent Claude Code leak from Anthropic, and what stood out wasn t the leak itself, but what it revealed about how these systems actually work.

  • A source map file accidentally exposed ~500k lines of TypeScript

  • Turns out Claude Code is basically a multi-step prompt orchestration system, not some mysterious black box

  • Includes things like:

    • layered prompt pipelines ( prompt sandwich )

    • fake tools to prevent model distillation

    • simple frustration detection (regex for rage prompts )

  • Even hints at future features like background agents and persistent memory systems

What s interesting is this:

It kind of confirms that the real product layer in AI isn t just the model it s everything wrapped around it.

Which raises a few questions:

Advice for going open source

Planning to open source Voiden (https://voiden.md/) soon.

This isn t a maybe someday idea anymore, it s a deliberate step we want to take in the coming weeks.

Ludovic Bostral

2mo ago

Has anyone built their own CRM instead of using one?

I'm a freelance consultant. Tried Folk, Attio, HubSpot free, Google Sheets. Never stuck with any of them. The problem wasn't the features, it was that I never went back to the tool.

So I built a CRM inside my AI assistant (Claude + MCP server + Supabase). Six contact lists, email drafting, a Chrome extension that scrapes LinkedIn profiles at $0.001 each. Total cost: $10.

The whole thing lives where I already work. That's why I actually use it.

First
Previous
•••
8910
•••
Next
Last