Vibe Coding for Dummies 📗 We collected the best tips on X for vibe coding, so you can build cool shit without getting stuck in a loop (bookmark this):
Use smarter models to plan and Claude Sonnet to vibe code. Tell Grok, GPT-4.5, or o1 Pro Mode to make a PRD for your "junior engineer," then copy-paste its plan to Claude Code/Cursor/Windsurf. This is super useful as your code grows more complex. https://t.co/OuqrnpKJlV
it's basically an open secret that software development has been entirely automated (and in GA) when you use grok or gpt4.5 as a planner and claude the tool using retard as the executor
— kache (@yacineMTB) March 4, 2025
When vibe coding, start over, often. You're not going to get it right the first time. So just go crazy. Accept everything Claude suggests. Get to a breaking point as fast as possible. Then take what you've learned and start over with your new learnings. https://t.co/G5DQsJIUTo
one thing I've learned w vibe coding is that, rather than building an app with layers upon layers, you build the whole app in an exploratory fashion and through that learn the spec and features
— Fred Stevens-Smith (@fredsters_s) March 11, 2025
and then you rebuild it with a new core prompt
over and over
Don't believe the hype with "100% coded by AI". The AI *will* get stuck, especially as your codebase grows. Be prepared to write some code by hand. https://t.co/o9TehMdzy0
When this happens I've had to resort to just fixing the bugs myself and rewriting stuff
— @levelsio (@levelsio) March 10, 2025
Nothing more frustrating than trying to make AI fix the bug and it just makes it worse every time
Sometimes happens! https://t.co/XlbxwJYPOs
If you're making a 3D game, tell Claude to use Three.js. It's the gold standard and can make beautiful games like this one from @NicolaManzini https://t.co/OpsigX9WSi
NEW GRAPHIC JUST DROPPED FOR MY SAILING GAME. pic.twitter.com/IhHtenMHHT
— Nicola (@NicolaManzini) March 3, 2025
If you're making a 2D game, avoid engines. Just tell the AI to write code without one. You don't need Pixi.js, Godot, etc., and your AI will hallucinate their APIs if you use them. https://t.co/Fuoqdxx30d
Dude I tried libraries and it fucking sucks.
— Danny Postma (@dannypostmaa) March 9, 2025
Told it to generate its own engine and boooooom
You can't one-shot everything with vibe coding. It's going to take you dozens if not hundreds of AI prompts to build a fully fleshed out app or game ready for other people to play. https://t.co/goNGWuVSJh
Currently vibe coded a full 3D game with threeJS thanks to Cursor and Sonnet 3.7. in approx 250 prompts https://t.co/Fm7wjtjoJw
— Nicolas Zullo (@NicolasZu) March 6, 2025
Tell Claude to vibe code using separate files. You don't want all your code in one massive file. It'll overwhelm Claude's context and make it slow. Ask for small, well-organized files. (In many cases it will do this automatically.) https://t.co/g2GmVWAc1W
Yesterday was GREAT
— @levelsio (@levelsio) February 23, 2025
But today I will be honest it's getting harder
The game is now 3000 lines long in a file called fly.html and Cursor starts getting into issues
To make one change, it has to go over the entire file and applying a change can take 15 seconds
Then over half… https://t.co/LCPRDQjzAB pic.twitter.com/I8zKWhEAue
Build in public when you're vibe coding. It doesn't matter if your tweets get 0 likes. Share every step. Tweet especially when you get stuck. When other people see, they're likely to chime in with helpful tips you didn't know about. https://t.co/xnSsUwsXVU
So @sw33tLie just blew my mind
— @levelsio (@levelsio) March 11, 2025
Apparently there's a ThreeJS world editor
Export your world in console with:
console.log(JSON.stringify(scene.toJSON()))
Copy that JSON blob, save it in a file, then go to https://t.co/0sZ2jLuiTf and press Import, then select that file
And… https://t.co/LO5YkBTYtU pic.twitter.com/yVpeUV0iwR
Expect vibing to go smoother with CRUD than with graphics. Claude struggles to get graphical APIs right, they struggle to draw vectors, and they struggle to know what looks good. The magic of vibe coding is not in getting things to look great. https://t.co/imqZAjWTP3
Damn LLMs are so much better at writing crud code for my backend compared to writing threejs. It's like they don't get vectors.
— Nicola (@NicolaManzini) March 9, 2025
Use smarter models for code review, not just planning. Reading all the code that Claude writes (esp. Sonnet 3.7) can take forever. So have Grok 3 or o1 pro mode do it for you. Just copy-paste the files Claude edited and tell them to review it. https://t.co/BuIKq9tCHG
I'm convinced the killer use case for o1 pro is vibe coding.
— Courtland Allen (@csallen) March 12, 2025
It's the bread in the vibe coding sandwich:
🍞🍞 o1 Pro Mode to plan 🍞🍞
🍅🧀 Sonnet 3.7 to code 🍖🥬
🍞🍞 o1 Pro Mode to review 🍞🍞
Here's the recipe:
1. Brainstorm with o1 pro. Copy-paste your…
Understanding context is key for vibe coding. Claude only knows what's in context, so you need to skillfully manage what's in context every time you make a request. Tips on that from @simonw:
Check out @NicolasZu's excellent guide to vibe coding: https://t.co/T601h3IkIb
I don't think the secret sauce is public yet. I can give you the fundamentals
— Nicolas Zullo (@NicolasZu) March 9, 2025
- Grok 3 to transform a game idea in a game design document
- Grok 3 to define the best stack: front & backend for your game and ambition (multiplayer? etc)
- Grok 3 to transform the game design…
Want more helpful research like this? Lots more to come. Follow @IndieHackers, @csallen, and @ChanningAllen for more. And don't forget to bookmark so you can reference for your next vibe coding project ✨