Whoa! You're this kind of Vibe Coder:

Test‑Driven Detective

Aim tests at the money paths first: unit tests for critical branches, one integration test per key journey. Model domain failures explicitly—don’t hide them behind random exceptions. Track cost and latency for your top spenders so you are never surprised by a bill or a timeout. Curiosity plus coverage beats guesswork.