Igga Fitzsimons

Weekends are for side projects!

Share what you're going to be building or an idea you're kicking around.

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

Hey everyone

I ve been building products for a long time (15+ years), and I recently tried using v0.dev for the first time. Honestly didn t expect much, but I was surprised how quickly I got something real off the ground - not just a playground UI, but a fully working fitness app with protected routes, dashboards, flow logic, the works.

It s called The HIIT PIT and it s live, but that s not why I m posting.

I m more curious to hear from other devs and indie makers: