I'm spending $200/month on Claude Code. Normal, or am I nuts? How much are you really spending? What tool is worth every penny, and what's way overrated?

Poll: How much are you spending per month on vibe coding tools? Options: $0 $50, $51 $100, $101 $200, $201+

I m curious! How do you document the different iterations of your app so you can revisit them later for enhancements or debugging?

Do you stick to traditional docs, use wikis, or something more creative?

As a solo dev, my app is getting bigger and more complex with multiple automations and moving parts, and I often struggle to remember all the implementation details. Do you also save the prompts you used to develop certain features, or have your own system for keeping track?

I ve built two marketplaces before:

• One for chatbot templates in 2018 that was used by 700+ marketing agencies.

• Another in 2020 for job seekers in the U.S., which reached 5.5M users.

So let s suppose I have some experience. You can read about me on Bootstrappers, TechCrunch, Dev to.

Now I m considering building a marketplace where creators can list their vibe-coded projects along with the code, a live demo link, etc. The idea is to target:

Hello everyone, I am dabbling in "Vibe Coding" and wanted to know if anyone has any advice or best practices?
I have used Cursor for a while, but have just started to use Claude Code to take a more hands-off approach. I am liking it so far for getting the general layout and functionality, and then I go in to clean up and finish the work. I have also used some MCPs, but I am looking for more!
All advice is appreciated. Thanks in advance!

I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team?
My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product.
I'm curious what you all think, would you hire a vibe coder?

I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team?
My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product.
I'm curious what you all think, would you hire a vibe coder?

Hey folks,

Sumit here from my little Himalayan village. I recorded this as I created my website nocodo.com and made it live. The content work has not started. This is only the basic layout/structure of the website for my AI/vibe coding related content.

Video: Vibe Coding: Create a Static Website with Astro, Tailwind and Markdown for Content

In the 20 minutes video, I go through:

Hey everyone, I have started a video series (on YouTube) on vibe coding. I just published the third video: https://youtu.be/Y-BHIeOe7cE
The series will have hands-on videos where I build a product through the series or they will be on topics important to vibe coding. In the video linked above, I talk about the learning (engineering) mindset needed for vibe coding. The series is aimed at everyone who is interested in creating software without knowing how to code but it needs self-learning some key concepts, downloading tools, testing software, etc.
The aim is to create production software without knowing how to code. Please share your thoughts and struggles, I am happy to help.
Thanks, Sumit

Hi ProductHunters,

What's in your opinion the best part of chatting with an AI while coding?
I start first:

The best part? Analyzing ideas, questioning architecture, and brainstorming concepts.

Being able to talk through your thoughts with someone (or something) while shaping your idea it s not just cool, it s incredibly useful.

StackOverflow was fun when someone had your exact problem.

But it never gave you feedback on the bigger picture.

Curious to hear your take!

Every time I vibe code there is always this huge lift that I constantly have to go through. Authentication, billing, password resets, emails, signup, waitlist, landing page and when it s all said done and the app is ready then comes the marketing, the blogging, the social media automation, the product hunt launch etc etc etc . So much repetitive crap that I have to do just to get a simple app up and running. How do you guys handle all this?

Since I am a coder and a hammer sees everything as a nail, I decided to create all this code as a template so I can jump into building an app right away. There is actually a lot more than what I mentioned above e.g customer support, chat, roadmap for building in public, email flows and more coming.

Hello everyone, Sumit here from the Himalayas. I hope everyone is having a relaxed weekend. My workflow with vibe coding has settled pretty well as I get more and more time out of desk while Claude Code builds the software.
I wanted to offer any assistance to fellow founders. I have been vibe coding full-time for a little over 4 weeks. Wrote about it here. Please share your tools, or workflow and in particular what is not working for you. What is frustrating you in building software with vibe coding?

There is something interesting I tried yesterday. I restarted my software project - I am building a smart web crawler. In software projects, a full restart is not an easy option even when we know we have learned from our current project and the project now has many layers of code that make it hard to sometimes navigate it. The crawler project was not quite so hard but I kept think the cost to restart maybe zero and I may get to focus on my successful experiments a lot better .
A leaner project helps sometimes but when software development costs human $/hour, we hesitate to restart. With vibe coding, I felt I should restart to see if I get a cleaner project. And it worked! In one day, I was able to restart with fresh GitHub issues, and then passing them on to Claude Code. I could get back to a working state, with tests and (in my opinion) better state of software flow than what I had built over the last 3-4 weeks.
Here are some takeaways I have till now (Claude Code based):

• A project management workflow with tickets/issues works really well, just like usual software development process

• Use Git branching to experiment on ideas and merge or not (if you want to throw an experiment)

• Use git worktrees if you want to work on multiple tasks in parallel - more advanced, I do not use this

• Use Claude.me to document your software workflow, code formatting, linting standards, etc.

• Ask Claude to follow Claude.md when tackling tasks - Claude Code can access GitHub issues, manage branches, etc.

• With enough clarity, if you feel the project has many remnants of experiments, do no hesitate to restart parts or all of it

Happy building!

I have been vibe-coding exclusively for about a month now. I am a senior software engineer and I have always been interested in the "no coding" approach to software development. I want software development to be easier, more accessible to everyone. So I switched to vibe-coding daily and writing less code directly or with AI assistance. When I read about other's experience, I feel there is this notion that vibe coding means the computer will think through all the details of the software and deliver an error-free product. This is not true and sets us up for frustration.
Vibe coding can be immensely powerful if we are willing to do some ground research. Start with Claude Code best practices. You do not have to understand all the technical concepts right away; just an overview may help a lot. And many of the points can apply if you are using tools other than Claude Code.

Majority of software for our general use has a UI layer and a data + controller layer. The UI layer is what we typically call "frontend" and the data + controller layer "backend". The UI layer loads in our browsers, desktop or mobile. We can even have native mobile apps for it. The backend layer stays on a computer connected to the Internet that we access from our frontend. We call the Internet connected computer (that serves the data for frontend) a "server". The backend and frontend communicate using an API (application programming interface). When we combine a software with all three parts and the tools needed to put everything in their place, we generally call it "full-stack software".
With these basic terms (frontend, backend, API) we can build simple, usable software much more easily than we may think. We can use OpenAI, Claude, Gemini or any of the top open source LLMs (large language model) to help us break down our software into parts that then can be coded by Claude Code or a similar code generation tool.
There will be obstacles, there will be confusing steps and frustration. That happens when we send our software ideas to developers too. What I want to encourage is to try. Learn about the topics a little, some basics of a software development workflow, how GitHub manages software development, what does DigitalOcean or Amazon Web Services provide, etc. It is OK if we do not get a fully working, bug-free software launched in one go. If we can learn how to use these new tools, so many more people can build the software they need.

I recently came across what the majority calls "vibe coding" and I am addicted. As I am a marketing guy, I couldn't resist in creating not one, not two, but 8 apps, which are basically systems to solve my own problems and frustrations.

However, I couldn't help but notice that all these tools are far from perfect. Lovable, Replit (which I use extensively now) say they did something, but in reality, they made only the surface.

Hey PH community,

I ve been noticing a shift more and more products these days are AI-powered, AI-enhanced, or just... AI everything.

While the possibilities are exciting, I sometimes wonder:

• Are we moving too fast without fully thinking through the problems we re solving?

• Are we relying on AI because it s trendy or because it genuinely improves the product?

I'm a full-time dev working on a clipboard manager, but instead of spending a week building a pixel-perfect landing page, I decided to see what would happen if I just vibe-coded it with AI.
I used Replit s AI agent and honestly? 95% of the site came together with minimal edits. It was one of the smoothest dev experiences I ve had in a long time and I didn t touch Figma once.
I m curious how many of you have done the same:
Have you ever let AI handle your site or UI?
Which tools gave you the best results (or worst headaches)?
Did you actually ship it or rewrite everything later?
Would love to hear what you ve built, what surprised you, and what went totally off the rails. Happy to share what I learned too!
Let s talk AI-assisted dev (and vibe-coding disasters/successes).