DocumentationCurated
Troubleshooting Doc Writer
For the doc users reach for when something breaks.
The prompt
Write a troubleshooting doc for [feature/error]. Structure: symptom, likely cause, steps to resolve, and when to escalate. Order by frequency, not severity.
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.