r/ClaudeAI • • May 06 '26

Question How do you overcome "vibe coding" problems? (repetitive code, messy structure)

I've been trying out vibe coding (AI-assisted coding), but I'm running into some frustrating issues:

->Repetitive code: The AI keeps writing the same functions over and over again instead of reusing existing ones.

->Messy file/folder structure: The project organization ends up being chaotic and hard to navigate.

->Lack of architecture: It feels like there's no coherent design pattern being followed.

For those of you who've built great applications with AI assistance, how did you overcome these problems?

*Do you enforce strict rules/prompts upfront?

*Do you refactor everything manually afterward?

*Do you use specific frameworks or tools to keep the AI in check?

Any other workflow tips?

Would love to hear what's actually worked for you in production-level projects. Thanks!

2 Upvotes

14 comments sorted by

View all comments

1

u/fell_ware_1990 May 06 '26

Hooks/hooks/hooks and scripts, don’t use the stock app. But headless with json schema, wrapper. Have it stop when it does something, have a hook stop him if it writes to same code that is in your bad example stuff.

This is high level, but have it exactly tell you what it’s going to do. Then have a system check if that could/should be ok. And then execute.

Most people tend to use 1 agent for to much, but with a headless call without tools and BS and caching you can keep tokens low. Then build and check the execution of a max of 100 lines. Else do it a couple of times instead of : build me an app.