I’ve learned the hard way that vibe coding products is hard when you start with a simple idea and bolt on more and more functionalities to it as you go. As you probably know, the more complexity you add later on will almost always lead to lots of bugs, duplication, basically just code spaghetti, which really sucked the joy out of vibe coding.
The solution sounds pretty simple. Just think your product through from the start, start with the foundation and start building it iteratively. However, thinking this through from a product, business and technical mindset can be challenging, and on top of that, it takes a lot of time. So I decided to leverage my experience as a Principal Product Manager to make this process easier for everyone. That’s why I built Vibewriter, which basically helps you clarify your idea and generate a complete build plan for whatever you would like to achieve (eg. an MVP, POC, full fledged app), that you can import into any of your favorite vibe coding tools.
And that’s basically it. This will give your tools all the context and guidance it needs, to start with a solid foundation and iteratively build more complex features on top of. Tell it to start working on task 1.1, review when done and move on to the next one.
You can check it out here. Open to feedback, and would love to hear your experiences!