Vibe coding with reusable components to reduce hallucinations?

Question

Idea: Instead of pure &ldquo;vibe coding&rdquo; (just letting ideas flow into code), what if we first vibe code a bunch of reusable components with well-defined, predictable APIs between them? Then we ask AI to vibe code using only these components.The hope: by constraining the building blocks, we reduce unpredictable hallucinations that often happen when vibe coding an entire monolithic codebase from scratch.Has anyone tried this? Does it work in practice?

phren0logy · Accepted Answer

Sure, it works pretty well. Work on one part at a time, then generate clear documentation for each part. Keep the api simple. Probably all of this is a good idea with our without LLMs.