I built a small web studio that generates kinetic color compositions, inspired by Felipe Pantone s Chromadynamica. I used GPT-5 to help shape the algorithm and Lovable to assemble the generator and the UI. It is code based, seeded, and limited to 10,000 outputs.
A few months ago I launched lovableprompts.app, a tool that helps makers and designers turn messy product ideas into optimized prompts for Lovable (and other vibe coding tools). It was meant to be just a small experiment to make the blank page problem less painful.
I might be missing some but I've been pretty much in love with @Lovable, @Cursor, @bolt.new and have been trying to use @Replit more and I honestly haven't touched @BASE44 too much but have heard good things. @chrismessina has nudged me to use @Windsurf for whenever I build another Raycast Extension! Currently I use: - @bolt.new / @Lovable - @Cursor - @Warp Curious what everyone thinks is the top one so far!
A couple of months ago I launched lovableprompts.app, a tool that turns rough product ideas into optimized prompts for Lovable or others vibe coding platforms (Bolt, Cursor, Replit...)
It started as a fun side experiment. Now it s used by 10k+ users, has generated thousands of products, and is slowly becoming a core part of many makers workflows.
A few months ago, I kept hitting the same wall. Every time I wanted to start a new project in @Lovable, I found myself stuck on the first prompt. I had the idea in my head, but turning it into something structured and usable always felt harder than it should.
So I built a small tool for myself. Something simple to turn messy thoughts into clear prompts that actually worked. I called it Lovableprompts.app, and once I shared it, more people started using it than I ever expected.
Since then, over 5,000 people have given it a try. A few nocode and vibe coding agencies and freelancers have even added it to their workflow, which honestly still blows my mind.
I m one of the devs who are writing less code now and doing more Prompting , damn I hate all of these fancy new buzzwords. Anyway, I m bored and don t want to write long prompts all the time. Anyone know a good tool (should work with Cursor)? If nobody knows one, I will need to do one :(
On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit
I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.
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
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
Velada Genius is an AI-powered personal dining assistant, combining expert curation with customized LLMs to deliver hyper-personalized restaurant recommendations. It's like having your best foodie friend at your side to help you discover the perfect restaurant
