the way mistakes can compound make this a dangerous proposition. This all worked with my small project, but a bigger one, with more dependencies or more complex project structures, would likely flummox the models. And reviewing changes across a more complex codebase becomes at once more difficult and more critical as the project size increases.
compounding mistakes. esp in bigger / more complex projects. a neg ratchet This to me points back to vibe assistance in components, less in the overall project. creating libraries of functions above always from scratch. Keeping tech choices clear.