Gabe Perez

Vibe coding process - do we jump in or plan it out?

byโ€ข

I'm super curious how everyone starts to vibe code? In the beginning I would simply jump into @bolt.new or @Cursor and just do a prompt and continue refining with the AI. I quickly realized this created a lot of issues as I didn't think about the structure, tech stack, and how I wanted the features to interact with each other and how the way I was building things would impact the user experience. I now do the following:

  • Write down a simple problem statement: "what am I trying to solve?"

  • Write down a simple solution statement: "what does the thing I'm building do (to solve the problem)"

  • Share the above with @ChatGPT by OpenAI and word vomit my thoughts, ideas, how I want the user to interact with my app, etc and ASK ChatGPT to turn everything I said and want into an easy to understand directive and instructions for an Engineer.

  • I then take the Engineer instructions and give it to a new chat in ChatGPT and ask it to turn those instructions into a prompt for an AI engineer and to break up the project into sections so that each time we focus on a section the app is shippable and keeps things easy to work on.

  • I take the output and paste it into my notes. I then give it to Cursor.

  • Once in Cursor, I create a new project folder and got at it!

Curious what everyone else does and if you've experience any things to avoid or must do

960 views

Add a comment

Replies

Best
Richa Sharma

Hi Gabe,
Love this breakdown โ€” it really resonates!

I used to jump straight into prompting too and ended up in this messy loop of rework and confusion. What changed the game for me was switching to a workflow tool that mirrors the exact structure you're describing โ€” it's called Vybcoder.

It simplifies the "plan โ†’ prompt โ†’ build" cycle into 3 clean steps:

๐Ÿ”น PLAN: I define the problem + goal in plain English, select only the files/folders that matter, and Vybcoder helps convert this into a precise AI prompt.

๐Ÿ”น GENERATE: I run that prompt on my preferred AI (GPT-4o, Claude, Geminiโ€”youโ€™re not locked in), and the responses are way sharper thanks to better planning.

๐Ÿ”น APPLY: Vybcoder parses the AI output and updates multiple files instantly, safely, and locally. No manual edits. Just apply and move forward.

Itโ€™s great because I stay in control while getting consistent structure. Plus, itโ€™s repo-native, cross-platform, and doesnโ€™t force me to change how I code โ€” just enhances it.

Curious to know if anyone else here has tried structured prompting with file context? Itโ€™s been a game-changer for me.
https://www.producthunt.com/products/vybcoder?utm_source=other&utm_medium=social
Itโ€™s built for devs, indie builders, and anyone who wants to move fast without losing control of their code.

Would love your thoughts, feedback, or questions!

๐Ÿ”— https://vybcoder.com