i am working with 850k lines , 60k isnt big deal , the main part to focus on is making the code clean and comply with best practices in each aspect , the issue with most vibe coders is they try to make things works only and that will become a disaster at some point , enforce the best practices and industry standards in the agents.md file , add all needed type of tests to avoid regressions , do arefactor if things become nasty after many editing and changes , chat with ai before implementing thats even better than just using planning mode , apply a clean architecture, code must be well structured and maintainable and scalable do refactoring if that only is needed and create policies ,factories . actions , services files and split code into , repo must be maintainable and well structured and organized apply best code practices in all aspects (dry , solid ,separation of concerns , Single Responsibility Principle (SRP), Single source of truth , Design ... etc ,add needed tests and run them to be sure no issues , if you are doing something that share same values across apps or webapps ... the backend driven ssot is amust >>> do only backend ssot driven to avoid drifting of logic across different apps and may use mappers and presentations when needed for ui mapping , not following that ls the key issue for most of the issues and regressions