Before a docs rebuild or when the current structure buries common tasks.
Propose an information architecture for [product] docs. Group by audience (new user, admin, developer) vs by feature. Justify the choice and flag content that spans audiences.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.