LLMs can generate a lot of code quickly but the quality range is massive unless you force the work through guardrails.

So I don’t ask my agent for “an answer”.
I ask it to ship a solution through a playbook (built from ~20 years of patterns/practices I actually trust in production).

The key rule:
It must cite which playbook rules it applied and why, plus show verification evidence.

That turns “vibes” into something you can audit:

Best-practice rule applied
Refactor/design move explained
Tests/CI proof attached

Upcase has still been one of the best sources I’ve found for pragmatic refactoring/testing/OO thinking, especially anything with Joe Ferris.