- VibeCoding.sh
- Posts
- Vibe Coding Issue #8:
Vibe Coding Issue #8:
The ultimate guide to making AI games in Cursor, 12 rules of vibe coding, and more
Hello, happy Thursday and welcome to the issue #8 of VibeCoding.sh. This issue is going out an hour after my first first edition of the Vibe++ newsletter, a new tier that features 2x the number of articles and focused on people who really want to hone their vibe coding skills.
Of course, that doesn’t mean free subscribers aren’t getting plenty of love, there’s still lots of great stuff in my newsletter for you, and the free tier is not going anywhere! In this issue I have some really good nuggets that I think will really help supercharge your vibe coding journey.
A lot has been going on in the vibe coding world with Levels.io’s vibe coding game jam finishing, and the Hytopia vibe coding game jam starting just a few days later. If you want to dive into a vibe coding game jam yourself, there’s still just under two weeks left to get into this one.
HYTOPIA GAME JAM 2: Where Vibe Coding Meets The Future of Games
📢Calling ALL creators, coders, and chaos-makers!
HYTOPIA Game Jam 2 is here to push boundaries. Build web-based mini-games using our SDK + AI-powered 'vibe coding' to turn wild ideas into playable reality.
No
— HYTOPIA (@HYTOPIAgg)
5:00 PM • Mar 31, 2025
What’s neat about Hytopia is they have a really well-structured workflow specifically for vibe coders so it’s an easy way to get started vibe coding games. I’m in the game jam though so you’ll have some competition 😉
Over the last week I crossed the 200 subscriber mark so I also wanted to take a moment to thank each and every one of you for subscribing. I didn’t know how this little newsletter would do so its exciting to see such a positive response!
And with that, let’s get to the good stuff.
The ultimate guide to making AI games in Cursor
The last issue of my newsletter was focused on the impact vibe coding is having in the game dev space. Since that issue I’ve had feedback that more of you want to learn how to build your own games, in the most vibe-tastic way of course. So I’ll always have at least one or two nuggets in here about how to go from idea to game.
And you’re in luck this week because one of the best threads I’ve ever read about vibe coding game dev dropped on March 25th.
I shared the first part of this thread because it shares a technique that I think is so important when you’re vibe coding anything, and that is - start with vibe project management.
This is also where model selection comes into play. While 3.7 Sonnet or o3-mini might be your go-to for coding, if you want to put together a project plan, you’ll want to use something like Grok 3 or o1-pro that are better at this specific task.
And for those of you who are too lazy to read the whole thread, I will tell you - if you haven’t played around with AmmoJS, take it for a spin, it will definitely help you take the physics in your game to the next level.
Also note, ThreeJS and AmmosJS aren’t some new phenomenon, they’ve been out for a long time, so there’s a ton of info out there about how to use the two together. If you’re looking for a good starting point, here ya’ go ⬇️
The 12 rules of Vibe Coding
I thought this was a clever list that Peter Yang shared on X, and yes - there’s a good chance you’re following some of these, but let’s by honest, you’re definitely not following all of them.

Two that really stand out to me that I think a lot of people likely miss are #4 and #7. And yes, #4 might seem counter-intuitive since you are “vibe coding” so the AI should be doing the coding right? Well, yes, sometimes, but you also want to use the AI to help you plan, think through decisions, put together logic processes and put deeper thought into what it’s doing, before it does it.
#7, this one I’m guessing only half of you are doing and honestly, it’s a game changer what you start doing it. Seriously, use images more, LLMs can pull a crazy amount of context from an image, the old adage a picture is worth a thousand words could not be more true here!
Massive thanks to Peter for putting this together, such a good list that I honestly wish I saw last year!
Turn your PRDs into a local task management system for Cursor

Okay, this one is pretty wild and I think it’s going to become insanely popular, and hopefully I’m helping expose more people to this awesome tool. I first found out about TaskMaster AI in this post on X from Eyal Toledano ⬇️
Like Eyal says, TaskMaster AI can help you vibe code much bigger projects without overloading Cursor and landing yourself in AI coding spaghetti. This solution breaks down PRDs into discrete and clear tasks so that Cursor knows what to do, and can execute on each task successfully without creating a huge complex mess, as can happen with any AI coding tool if you give it too much too fast.
I think this is freakin’ brilliant, hats off to Eyal for bringing this to life!
Clone any website with Cursor and Firecrawl
Okay, this is just wild, and it’s a vibe coding task that even those of you who are completely brand new to vibe coding can do right away.
By leveraging the Firecrawl MCP, and combining it with the super powers of Claude 3.5 Sonnet you can drop any website into Cursor composer and let the agent go to town. In many ways this is even easier than vibe coding because you’re really just writing one single prompt and poof - you’ve cloned a site.
Now one word to the wise. I don’t think this means you should go and rip off designs from people who have worked hard to build beautiful, clean, well-designed sites. Instead, use them as inspiration if you want, but just as a starting point. Don’t just one shot someone’s site and then change the text and logos and call it your own.
Take the elements you like and start vibe coding away building something different but with the skeleton of the key elements that you liked.
Vibe Coding Guide for Non-Coders
I know I have a wide range of readers, some of you have been coding for years, others haven’t written a single line of code, and might even be too intimidated to dive in and start vibe coding.
And as I was thinking about key topics to cover in this issue I realized - I don’t think I’ve ever shared anything specifically for non-coders who want to get into vibe coding. So it’s time to change that.
I spend some time trying to find the person piece of content for all the non-coders out there who might be coming up with excuses in their head why they can’t possibly vibe code and have to sit on the sidelines…well, I’m sad to say, you’re out of excuses because this is the one tutorial to rule them all.
Okay, and that’s a wrap, thanks for reading and I’ll see you again in a couple of weeks! And of course, if you want 2x the content, join Vibe++, it costs about the same amount as one latte from Starbucks, but offers a LOT more value IMHO, but I’m biased.
Have a great week!
