✨

VIBE CODING

Cheatsheet

AI-directed development: define intent, constrain scope, verify hard, ship clean.

Director mindset Intent · Constraints · Proof
🎯

The Vibe Loop

1

Frame outcome

Define user result and acceptance checks

2

Scope change

Identify files, boundaries, non-goals

3

Generate

Single pass, minimal output

4

Review diff

Align with intent, reject drift

5

Verify

Tests, UX, edge cases, then commit

⚡

Core Principles

Director mindset You define outcomes and approve diffs
Small scopes Short prompts, tight diffs, faster review
Verify by default Tests + behavior checks beat vibes
State discipline Commit often, log prompts, keep rollback
📋

Prompt DNA

Goal Outcome + user impact Context Key files, naming, constraints Non-goals What must not change Checks Tests, UI steps, edge cases
🛠

The Vibe Stack

Explore Editor + browser agent Build Repo-aware CLI agent Verify Tests, lint, runtime checks Anchor Real files, real constraints
💻

Prompt Template

Goal: <what the user should be able to do>
Context: <files, constraints, stack>
Non-goals: <what to avoid, scope limits>
Checks: <tests, UI verification steps>

Ask for a plan first when risk is high.

🧭

Prompt Patterns

Plan first Outline approach before code
One feature Keep scope tight per prompt
Diff-first Ask for patches, not rewrites
Sample data Realistic inputs = accurate output
Force checks Require explicit success criteria
✅

Quality Gates

Diff review Verify files, scope, and intent
Run it Local test or manual UX pass
Edge checks Hit a non-happy path
Stop if Failing tests, unclear ownership, hidden scope
⚖️

When to Vibe vs Code

Great Fits

  • MVPs and demos
  • UI/content iteration
  • Internal tools
  • Docs scaffolding
  • Data cleanup scripts
  • Refactors with tests

Switch to Classic

  • Security-heavy flows
  • Perf-critical logic
  • Ambiguous scope
  • No tests or owners
  • Regulated systems
  • Large architecture

Higher blast radius = more design before generation.

⚠️

Drift Signals

✗ Spec expands mid-prompt or adds new features
✗ Renames or rewires files you did not touch
✗ Introduces new dependencies without approval
✗ Deletes tests or bypasses verification
🚫

Anti-Patterns

✗ Letting the model redefine goals
✗ Stacking changes before verification
✗ Accepting diffs without a local run
✗ Shipping without ownership or rollback
👥

Team & Safety

Roles

Owner sets scope · Builder runs loop · Reviewer verifies risk

Guardrails

No secrets in prompts · Pin dependencies · Audit changes · Keep rollback

📝

Release Checklist

Use every iteration