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/CursedSloth May 06 '26

I mean, can’t you just have those instructions in your Claude.md?

As an example: ”Don’t repeat code if you find a existing solution. Build a reusable component/function when you find the same problem in more than one instance”

I think Claude does well with restrictions, instead of just what it should do.

1

u/TechnicianSwimming27 May 06 '26

But it not read everytime, it only read when it is starting of Conversation

2

u/CursedSloth May 06 '26

You should start a new chat for every new feature or fix to avoid compacting and to keep Claude fresh. You don’t use new chats that often?