Technical WritingCurated
Style Guide Drafter
Before multiple writers make the docs feel like different products.
The prompt
Draft a documentation style guide for [team/product]. Cover: voice, structure conventions, terminology, formatting, and code samples. Give before/after examples.
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.