I am working on four big Github repos for the same project: backend repo, iOS app repo, Android repo, web repo. In all repos there is logic that handles various business logic for our apps’ subscription and subscription cancellations flows. We also use RevenueCat in all repos to handle these subscriptions. I also have some design documentation for business logic of the subscriptions. We have customer support tickets incoming about various scenarios that cause our users different problems regarding their subscriptions. Pinpointing such problems manually is very time consuming. I want to make good use of Claude Code for this aspect. The implementation that I have in mind is somewhere in these lines: Have Claude Code generate some sort of code navigation files of the subscription flows in each repo. It would be awesome if it could update itself upon code changes, or at least manually from time to time.
- These would serve both as some sort of diagram for us developers to more easily keep track of the current implementation.
- Also, these would also serve as context for Claude Code when trying to pinpoint different problems.
- I would also like to be able to make Claude Code detect any anomalies directly by comparing these code navigation files to the actual design documentation. The cause of the problems that customer support reports to us usually lives in the small details of the implementation. Do you have any recommendations on how to approach this challenge? submitted by /u/Majestic_Sky_727
Originally posted by u/Majestic_Sky_727 on r/ClaudeCode