About
Hello! Super excited to finally join the product hunt community. i love the vibe here. A little about me: I am a serial entrepreneur. One big win. One big loss. A lot of false starts along the way. Currently thinking a lot about Agentic Technologies & AI Coding. Right now i am building tools to help other AI coders learn and build really cool stuff.
Work
Indie maker
Links
Maker History
Forums
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
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
#vibecoding: What are your favorite Cursor pro-tips?
Recently stumbled across this Cursor pro-tip from Ian Nuttall on X:
"1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below: