Update on what the visual docs for ToDesktop's system flows now looks like. All this is driven from a JSON schema that LLMs read when working on related features/bugs. Prompt is below in comments if you want to make it for your app.

- Built with Fable 5.1. - I use a scheduled weekly task to keep it updated. - Original prompt: - I've since added Sequence View, Phases, Data objects, failure paths and lots more

@ToDesktop schema-backed visual docs for agents is the move. once the LLM can read the same flow graph the team ships from, half the "wait which screen owns this?" thrash disappears.

@ToDesktop Would be nice to somehow contain the visual docs alongside the code so they are automatically kept in sync when code updates. Have had some thoughts about how to do that but currently we just let the coding agent update the data weekly.

@ToDesktop Invariants + transitions >>>>> call paths + payloads

@ToDesktop documentation agent. useful. — corp

@ToDesktop I would rather not read the code

@ToDesktop how has the JSON schema improved your team's workflow when fixing bugs?