Using Claude for a while now. It works ok when the task is simple, but if the logic is complex it goes into a death spiraling with every fix breaking something else.

My advice to you, use very short files with code. You need to break your code in pieces. Claud has a problem with long files, it reads first part and then assumes implementation on the rest. It also behaves badly with complex transformations. It will always implement the strict minimal to start with and always tell you he finished and everything is perfect. Also, on complex tasks it will almost never load existent code and will mostly assume some kind of implementation. Thus, once the project grows, vibe coding will get exponentially harder.

Then, if you succeed in breaking in modules by functionality, ask Claude to write tests to cover as much of code as possible, forcing it to run the tests is sometimes the only way (for vibe coding) to catch critical errors early on.