11d • General discussion
The seven rules of vibe coding
If you’re vibe coding and your app keeps breaking, you don’t need more prompts.
You need 7 rules.
✅ Rule 1: Start with ONE sentence
What the app does, who it’s for, and what “done” means.
✅ Rule 2: Ask for a plan before code
“Give me the steps, file structure, and data model first.”
✅ Rule 3: Build the smallest working version
One screen. One action. One result. Then expand.
✅ Rule 4: Lock decisions early
Stack, routes, database, auth.
Changing these mid-build is how projects die.
✅ Rule 5: Give constraints, not vibes
Examples: TypeScript only. No new libraries. Validate inputs. Keep functions pure.
✅ Rule 6: Test as you go
After every change: run it, click it, break it. Don’t pile up edits.
✅ Rule 7: When it bugs out, report like an engineer
Not “it doesn’t work.”
Say: error + what you expected + what happened + the file.
Vibe coding works when you drive and the AI copilots.
What tools do you currently use for vibe coding?
6
2 comments
The seven rules of vibe coding
powered by
skool.com/thisaitooldoesthat-8281
Most people feel behind on AI. I help them catch up and leap ahead.
Suggested communities
Powered by