Vibe coding isn’t just fun and games.
It’s a skill—and here’s how to get it right 🧵
It’s a skill—and here’s how to get it right 🧵
Comments
For web apps: use Next.js and React
Avoid niche frameworks → they don’t have enough AI training data
⚠️ Use the wrong stack and be prepared for edge cases
Before you prompt → know what you want
Break it down into mini prompts: “Add feature A”, “Fix error B”, “Refactor C”
⚠️ Skip this and your code will be a spaghetti mess
Track changes with Git
Commit often, especially after working with AI
⚠️ Without versioning, one wrong AI output can delete your working code
Drop links to documentation (preferably /llms.txt endpoints)
Share working reference code for any library you use
⚠️ Or waste hours debugging “why it won’t compile”
Switch to a stronger model
Share previous context: what broke, what you tried, the logs
⚠️ Don’t expect AI to fix vague problems without details
Even when vibe coding, fundamentals matter.
You’ll need them when AI hits a wall—and a human has to fix it.
👉 These rules aren’t to make vibe coding less fun.
They make sure it actually works.