Vibe Coding Patterns

Fast AI-assisted coding works when speed is paired with tight feedback. The goal is not to make the agent guess more; it is to shorten the loop between intent, code, and verification.

Productive Loop

1. State the user-facing behavior.
2. Ask the agent to inspect the relevant code first.
3. Let it implement a narrow slice.
4. Run the focused check.
5. Review the diff before widening scope.

Repeat the loop instead of asking for a giant speculative change.

Prompt Patterns

Good:

Add English locale support for the selected handbook only.
Do not let unsupported books fall back to Korean.
Update route filtering, sitemap, and E2E coverage.

Risky:

Internationalize everything.

The first prompt contains constraints and testable behavior. The second prompt invites accidental scope expansion.

Keep Control

• Ask for file references when the agent makes claims.
• Require tests or a reason tests cannot run.
• Keep unrelated refactors out of feature work.
• Use worktrees when exploring competing approaches.
• Stop and inspect when the agent starts editing broad shared surfaces.

Anti-patterns

• Accepting code without reading the diff.
• Letting the agent invent product copy for regulated domains.
• Mixing feature work with formatting churn.
• Running package upgrades as part of unrelated fixes.
• Treating a green build as proof that UX is correct.