I cannot answer your main question, but i can give you recommendations wrt what you are gonna try to do. Very likely there will be a lot of parts of the app yo

I cannot answer your main question, but i can give you recommendations wrt what you are gonna try to do. Very likely there will be a lot of parts of the app you are not going to understand, those will be the main problems so help claude help itself. Make it add diagnostic/event-logs to every part of the stack and potentially even design implementations around traceability (eg avoid batch background processes that touch many flows if possible). so that claude can check whether runtime behaviour matches expectations. also store historical data to help debug regressions. Treat implementations as cattle not pets, once a feature is done consider scapping it and turning it into a design doc, then ask claude to reimplement interactively with you step by step explaining to you what is going to do, why it matters, etc. this is a very good way to minimize the black boxes you don't understand in the app. if the app is web make it work very well with playwright for e2e ux tests. finally i like the architecture given in https://www.youtube.com/watch?v=4KvbVq3Eg5w https://www.youtube.com/watch?v=4KvbVq3Eg5w (use ui composition to define feature) but this has little to do with claude