50 Do’s and Don’ts for Vibe Coders

Do

• 1 · Write a one-page spec before you build
• 2 · Name the single most important user action
• 3 · Pick popular tools with strong documentation
• 4 · Keep the first version small
• 5 · Put project rules in CLAUDE.md or AGENTS.md

Don’t

• 6 · Kick off with a vague one-line prompt
• 7 · Build every feature at the same time
• 8 · Choose obscure frameworks
• 9 · Ignore who will actually use the app
• 10 · Rewrite the plan every hour

Do

• 11 · Ask for a plan before any code is written
• 12 · Build one feature at a time
• 13 · Share exact errors and screenshots when something breaks
• 14 · Ask the AI to explain any change you do not follow
• 15 · Open a fresh session for each new task

Don’t

• 16 · Accept changes you have not reviewed
• 17 · Paste the same error ten times with no new context
• 18 · Let the AI rewrite working code without a reason
• 19 · Cram unrelated requests into one prompt
• 20 · Run a session so long it forgets the rules

Do

• 21 · Store secrets in environment variables
• 22 · Rely on a proven sign-in service
• 23 · Set database access rules so each user sees only their own data
• 24 · Validate every input on the server side
• 25 · Request a security review before launch

Don’t

• 26 · Paste API keys into prompts or code
• 27 · Commit .env files to Git
• 28 · Rely on the browser to enforce permissions
• 29 · Collect data you have no use for
• 30 · Ship payments or health features without an expert review

Do

• 31 · Use Git and commit after each working step
• 32 · Ask for automated tests on core features
• 33 · Test on an actual phone
• 34 · Enter wrong inputs on purpose
• 35 · Add error monitoring after launch

Don’t

• 36 · Ship code you have never actually run
• 37 · Deploy straight to production with no preview
• 38 · Skip backups of real user data
• 39 · Ignore console warnings
• 40 · Assume it works because the AI says it does

Do

• 41 · Leave the agent’s sandbox and approvals switched on
• 42 · Review every diff before you merge
• 43 · Have a second model review important changes
• 44 · Install only the plugins and MCP servers you trust
• 45 · Add each lesson to your rules file

Don’t

• 46 · Run always-approve modes on your main computer
• 47 · Let two agents edit the same files at the same time
• 48 · Hand agents access to your production database
• 49 · Treat website content as instructions to follow
• 50 · Stop learning how your own app works