Vibe Coding Decision Framework

A decision tree, prompt level reference, tool selection matrix, and common pitfall fixes for vibe coding — covering when to vibe, which prompt level to use, which tool to choose, and how to diagnose common vibe coding problems.

Syntax

design-and-specify

Decision Tree: Should I vibe code this?
1. Will real users interact with this? No → Vibe code it. Yes → continue.
2. Does it involve security, payments, or sensitive data? Yes → Write a spec. No → continue.
3. Will multiple people work on this code? Yes → Write a spec. No → continue.
4. Is precise behavior critical (business logic, calculations)? Yes → Write a spec. No → continue.
5. Will you maintain this beyond 2 weeks? Yes → Level 3+ prompt minimum. No → Vibe code it.

Example

design-and-specify

# Prompt Level Reference
# ─────────────────────────────────────────────
Level 0 | Raw Vibe        | 0 min   | 30-50% | Exploring ideas
Level 1 | Vibe + Context  | 30 sec  | 40-60% | Quick experiments
Level 2 | Vibe + Features | 2 min   | 60-75% | Prototypes, demos
Level 3 | Structured      | 5 min   | 75-85% | Internal tools, MVPs
Level 4 | Spec Package    | 15 min  | 85-95% | Production features
Level 5 | Full SDD        | 30-60 min | 90-98% | Complex production

# Tool Selection Matrix
# ─────────────────────────────────────────────
Bolt.new      → Full-stack apps from scratch
v0.dev        → React UI components
Lovable       → SaaS apps with Supabase + auth
Replit Agent  → Browser-based experiments
Cursor        → Working in existing codebase (AI IDE)
Windsurf      → Multi-file agentic refactors
Copilot       → Inline code completion
Claude Code   → Spec-driven production coding

# Common Pitfalls + Fixes
# ─────────────────────────────────────────────
Problem: AI changes things you already approved
Fix: "DO NOT modify the header. Only change the pricing table."

Problem: Output doesn't match your vision
Fix: Level up your prompt — add layout description,
     reference screenshots, list specific data fields.

Problem: Can't reproduce the same result
Fix: Save your prompts. Write a spec. Reproducibility
     is exactly what specifications provide.

Problem: Project got too big for the AI to handle
Fix: Break into smaller features. Each feature gets
     its own prompt or spec.

Problem: Spent 3 hours iterating on a 30-minute task
Fix: You passed the vibe coding threshold. Stop,
     write a spec, start fresh.

Problem: Teammate can't understand what you built
Fix: Write a retroactive spec. Better late than never.