AI dev tools are moving stupid fast. Every few weeks, there s a new must-use. Some stick. Most don t.

Some vibe coders are developing full products with @ChatGPT by OpenAI+ @Replit. Others swear by @Cursor + @Claude by Anthropic . A few are mixing @Lovable , @v0 by Vercel , and @bolt.new . New and shipping way faster than expected.

I ve been refining my own vibe stack lately.
Building with @Google Antigravity at the core. It keeps the flow clean when things get messy.

Share your current Vibe Stack:

Hey everyone,

I don't actually like using the term "vibe coding". We've been software developers for over a decade ,are not one-shotting features, and have a very opinionated and strict dev process.

Hey PH family.

Been part of this community for years now, and if there's one place to talk with builders, this is it.

AI dev tools are evolving crazy fast , every few weeks there s a new must-try for vibe coders.

Some people are building full products with @ChatGPT by OpenAI and @Replit , others swear by @Cursor and @Claude by Anthropic , and a few are mixing @Lovable + @v0 by Vercel + @bolt.new to ship apps in record time.

I ve been refining my own vibe stack lately, trying to find that sweet spot between speed, control, and creativity.
It made me wonder ,what does your setup look like right now?

The @v0 by Vercel team recently dug into industry trends to publish the first State of Vibe Coding report.

My key takeaways:

1. Everyone can build: 63% of vibe coding users are non-developers, generating UIs (44%), full-stack apps (20%), and personal software (11%).

2. Adoption is everywhere, with significant adoption rates in APAC (40.7%), Europe (18.1%), North America (13.9%), and LATAM (13.8%).

3. 92% of US developers use AI coding tools every day

4. 30% of new code at @Google is generated by AI

5. 25% of @Y Combinator startups rely on AI-generated code

6. Rapid expansion has a cost. Vibe coding apps keep hitting vulnerabilities: exposing secrets, access misconfigurations, hardcoded credentials.

7. The future: going mainstream or hitting its sweet spot in working MVPs, the vibe coding trend is here to stay, and it's happening now.

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!

Vibe coding tools have been making huge improvements, but things can always get better.

What blockers are you still running into? What has no one solved yet? What do you wish you could do, but can't yet?

Hi, I m an app developer who s shipped many projects the old-school way (hand-coding) for over a decade. Recently AI tools have exploded - speeding up my production like crazy.

What s happening:

- Idea to MVP: Creators focus on ideas while AI writes most of the code.

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

Every time I vibe code there is always this huge lift that I constantly have to go through. Authentication, billing, password resets, emails, signup, waitlist, landing page and when it s all said done and the app is ready then comes the marketing, the blogging, the social media automation, the product hunt launch etc etc etc . So much repetitive crap that I have to do just to get a simple app up and running. How do you guys handle all this?

Since I am a coder and a hammer sees everything as a nail, I decided to create all this code as a template so I can jump into building an app right away. There is actually a lot more than what I mentioned above e.g customer support, chat, roadmap for building in public, email flows and more coming.

I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team?
My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product.
I'm curious what you all think, would you hire a vibe coder?

I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team?
My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product.
I'm curious what you all think, would you hire a vibe coder?

Wanted to show (not tell) what's being built with vibe coding tools so here's the official collection of some of the best vibe coded projects across Replit, Bolt, Lovable, v0, Cursor etc.

http://vibecodingshowcase.com/

about to Launch a product for creators after building for a few weeks to months.
Started as a way to get into vibe coding and just got real useful real quick lol.
But the goal is still that - mix my skills and knowledge as an engineer with the good parts of AI coding.
So i learned a few of what to need and have

• Claude.md file

• best coding practices section

• pretty heavy compartmentalization & file structure separation

• certain ways to prompt

• ask for implementation plan before telling it to code

But i feel like all i learned is about directing prompts - im wondering...

what are you guys finding are the best .md or deeper ai vibe coding tricks that are helping you save time? be more efficient? debug ai less or help it get it right the first time? whats your vibe code tips and tricks?

Hey all,

Just wanted to share my 1st fully vibe coded app: https://fileforge.in/

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

Plan > Prototype > Production > Publish

Hey PH!

Plan > Prototype > Production > Publish

Hey PH!

As a data engineer who has little experience in full-stack software development, I ve been experimenting with vibe coding tools to move fast in the early stages.

My flow looked like this:

Prototyped the main UI in V0 (after 300+ iterations/conversations back and forth)

Hello everyone, Sumit here from the Himalayas. I hope everyone is having a relaxed weekend. My workflow with vibe coding has settled pretty well as I get more and more time out of desk while Claude Code builds the software.
I wanted to offer any assistance to fellow founders. I have been vibe coding full-time for a little over 4 weeks. Wrote about it here. Please share your tools, or workflow and in particular what is not working for you. What is frustrating you in building software with vibe coding?