I don't know if this is the correct way but it is the pattern I have fallen into.
Written code is the new compiled code. You never look at it, not even once. Documentation is the new written code.
Every repo has a /docs folder that holds the full specification of the code. Full architectural block diagrams, edge case behavior, style, problem statement, etc. I closely review these docs and make sure that the agent follows these specs and ensures the specs are updated after every code change. In theory an agent could fully rebuild the system from scratch using this documentation.
Maybe this is just pearl clutching, but it helps for when people ask architecture questions and I can answer and pretend I know what's going on.
Written code is the new compiled code. You never look at it, not even once. Documentation is the new written code.
Every repo has a /docs folder that holds the full specification of the code. Full architectural block diagrams, edge case behavior, style, problem statement, etc. I closely review these docs and make sure that the agent follows these specs and ensures the specs are updated after every code change. In theory an agent could fully rebuild the system from scratch using this documentation.
Maybe this is just pearl clutching, but it helps for when people ask architecture questions and I can answer and pretend I know what's going on.