News for hackers. Stuff that matters.
Re:How do you keep up quality when you vibe-code? by DeepOntology on Thursday November 12, 2026 @09:12PM (#50477200)
Here are my tips:

0. Use Fable 5.2 on max (or whatever the most powerful model + effort you have access to) for all strategy, design, and planning (since good reasoning at higher levels of abstraction always pays off when it comes to implementation)

1. Use Opus 5.5 sub-agents for implementation, and have the Fable "drivers" break work into lanes.

2. Only build when there's an explicit "go" on a written plan.

3. About 1x/week do a broad, high-dimensional analysis of the codebase (tech debt, test coverage, security, performance, etc. etc.) and have judge agents vote on priority --> fix the P0s and P1s and a random small subset of P2s.

4. Test coverage > 90% and set up CI to reject changes which drop it below 90%.

5. Have every agent create a numbered guide for verification which you walk on staging (or locally, if early in your development process).

6. Antagonistic & hyper-critical agents -- whenever you make a change spin up a small number of Opus 5.5 agents to review everything from an antagonistic/hyper-critical lens -- this catches a lot.

7. Make a list of principles and make every agent read the principles before every change. Principles only get added + refined. Whenever an agent doesn't know what to do, ask if it can figure it out from the principles -- if not, walk the agent through it + then have it add the appropriate principle. This leads to convergent implementations at an abstract level, over time.

---

Using these tips I've developed bug-free code bases over 100k LOC in ~weeks.

There are no comments on this comment yet.