No links to share, by my approach is to create rich, up-to-date documentation that is structured positively for LLM prompt usage but also serves as breadcrumbs

No links to share, by my approach is to create rich, up-to-date documentation that is structured positively for LLM prompt usage but also serves as breadcrumbs to the mental model of the product. When things change, have the LLM update the docs. Think of this as "document-driven development" in the vein of "test-driven development". The goal is to never lose the big or mid-level picture of things and allow the LLMs to careful adjust those, then implement the details as it sees fit.