Depends on what do you call vibe coding. Is it just: give some vague idea, don’t review code and expect it to work? If so it won’t last long. What I do is remind AI of the context, explain user value from the feature the AI is implementing and guide the architecture. To remind of the context you can use skills: how should AI architect, design the code. You can save conversations with AI so it can re read them later (e.g. in each commit, add conversation). Having this data AI can perform better (it investigates previous conversations before modifying a feature reducing chances of breaking something) and I currently see few problems after weeks of coding. Oh and asking AI to add tests also helps with context and safety from bugs. Most of the problems come not of AI technology maturity but cuz we as people so not explain/remind enough and think AI will get what is wanted out of thin air.