I would never call myself a real coder. Most of what I know comes from tinkering with the Linux terminal, copying and pasting Python, and long-forgotten coding classes that I started – and quickly abandoned – years ago. I wouldn’t even say I know enough to be dangerous, but probably enough to break something if I’m lucky. And that’s exactly why vibe coding interests me so much.
I created web applications for event calendars and a horror movie showcase galleryand I spent way too much time recreating some of my favorite childhood PC gamesall by talking to an AI chatbot using (mostly) natural language. Vibrational coding can, in essence, make coders non-coders. All you have to do is have an idea, communicate it to the AI, and refine the idea to create what you want. Well, that’s what vibrational coding is in theory.
There are things you’ll learn when mood coding, and having the right mindset will be very helpful when creating an app with just words. In fact, mindset can make the difference between a good or bad experience.
Whichever chatbot you choose, whether it is GeminiChatGPT, Claude or another option, each will have its own features and quirks that you will need to recognize and resolve. Below I’ve detailed a few things I’ve learned along the way that I think might help anyone getting into mood coding, regardless of the specific chatbot you’re using.
Featured Offer
Know your chatbot
The chatbot you use is important, although the type of template may matter more than who created it.
By trying to create the same application Using both Gemini 2.5 Flash and Gemini 3 Pro, it became clear that a different approach was needed with the former to achieve a similar result to the more advanced Pro model. This means more specific intention and instructions with the prompts and, in my experience, more manual work.
Since I’ve been coding with Gemini 2.5 Flash, it has often made the process more convenient, which is something I wasn’t looking for. When refining the application, it would only provide the code for the modified section, leaving me to swap the code manually or follow another prompt to provide the entire code. On the other hand, using Gemini 3 Pro, it would automatically provide the entire body of the code.
Your mileage may vary, but if you’re deciding between using a “quick” or “thoughtful” model for your vibe coding project, you may need more skills and training to work with a quick model. If all you have is a quick or less advanced model and it asks you to make code changes that you’re not comfortable with, you can ask the chatbot to provide the entire code again (or set a rule to provide the entire body of code with the changes after each change).
From my experience using several (but not all) chatbots: If you don’t mind getting your hands dirty with a little code, you’ll probably be successful with most models as long as you provide clear and specific prompts. Non-coders: Stick to more advanced “reasoning” or “thinking” models if you can. I found that thoughtful models will do the heavier work for you.
Knowing your chatbot, its limitations and capabilities comes from experience, so it’s best to use it generally and ask questions.
Be specific with your prompts
If you have a detailed idea of the type of project you want to rock the code on, specificity is key.
Vibrational coding begins with what is in your mind. If you have a very clear idea, you can and should include everything you want to see in your project in your initial prompt. Make it comprehensive. The chatbot will create what it can and hopefully you will see your idea take shape.
On the other hand, you could just have a very vague idea of what you want the app to be and give the AI more leeway to control how the app works or how it accomplishes something you asked it to do in a different way.
Iteration is the longest part
Your dream app probably won’t come in the first or second prompt you send to the chatbot. You’ll probably spend more time asking for improvements than anything else.
Ask your chatbot for suggestions. If you’re stuck on any part of the web application, whether it’s how it works or its style, just ask the chatbot. It will provide you with just about as many suggestions as you want. And since vibe coding is a very iterative process, asking it to suggest five ways to improve your app could really make a difference.
Sweat the technical stuff, just a little
Non-coders will need to understand certain technical elements for an application or project to work properly. The good news is that you can use the chatbot as a resource.
Here are a few things you’ll want to understand:
Format: For most simple web applications, outputting the code to HTML is ideal for non-coders. And if you don’t want to manage multiple files and folders, you can request a single HTML page. This can introduce limitations and potential “memory issues” with the chatbot pop-up if the file becomes large, but it is one of the easiest methods to send the output code to your browser for testing. If you are unsure, ask the chatbot what the best format should be for your project and the app launch process.
Ladder: If you’re not sure about the chatbot’s capabilities, just ask it. It’ll tell you it won’t be able to create a new social network for you, but if you want an audio visualizer that channels the old days of Winamp, you’re in luck. If your request is beyond the capabilities of a chatbot, ask it for alternative approaches.
Check for bugs: Sometimes the chatbot will deliver faulty code, so you will have to test it again and again. It’s even more important that you communicate what’s not working or how exactly you want something to work. If you provide a vague prompt, don’t be surprised to receive a vague result. Telling the chatbot “this doesn’t work” is significantly less effective than detailing the specific bugs you encounter during testing. The more specific your feedback, the more accurate the AI’s response will be, making the overall experience more efficient and enjoyable.
Have an open mind
Unless you have a very specific and rigid goal with your mood coding project, keeping an open mind is essential. If you don’t know anything about coding, you probably don’t know all the features available to you. If you’re unsure of your limits, it’s just as easy to underestimate as it is to overestimate what you can do.
In a perfect world, everything you code will work smoothly, but errors are likely to occur. Whether it’s an oversight in the chatbot’s memory, a technical limitation, or something in between, some things will break. If you’re lucky, the chatbot will recognize and resolve the problem, but sometimes it won’t, and that’s where having an open mind helps. Ask for alternative approaches: You may find an approach you like more than your original idea. You will never know what you don’t know unless you ask.
Don’t be afraid to start again
As with other creative processes, sometimes it’s best to start again. If you’ve gone through countless iterations and your app is nowhere near where you want it to be, consider starting over. This can be started entirely from scratch or by taking the code from the first conversation and using it as a baseline for the new conversation you’re starting.
Although you can ask the chatbot to start from scratch in the original chat, a clean slate might be necessary moving forward. Try again in a new discussion so the AI doesn’t confuse things with your previous project. You may have identified certain prompts that may have set your project back that you can avoid using this time, allowing you to stay focused on what worked, rather than keeping what didn’t work in the chatbot’s memory for reference.
A fresh start is not only about the chatbot “getting it right” this time, but also about you being able to reset your creative flow.
