Milan Admin

Milan Admin

Hello, is it me you looking for?
7 points

Badges

Tastemaker
Tastemaker
Veteran
Veteran
Gone streaking
Gone streaking

Maker History

  • BuzzForce
    BuzzForce
    Help Your Team Create Buzz on Social Media
    Apr 2025
  • Unanimous Bets
    Unanimous Bets
    Bet With Others - Find High Consensus Bets
    Nov 2024
  • 🎉
    Joined Product HuntFebruary 23rd, 2019

Forums

Gabe Perez

2mo ago

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

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

Gabe Perez

2mo ago

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

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

View more