Create a Technical Writing Style Guide

Without a style guide, every writer punctuates lists differently and argues about title case. This produces one for your company: voice and tone with do and don't examples, punctuation rules, heading conventions, number formatting, UI naming and a banned-words list. Tell it your products and your writers, get a guide they can actually use.

Generate a concise technical writing style guide for {COMPANY_NAME}, whose products serve {CUSTOMER_SEGMENT}. The guide will be used by {WRITER_ROLES}.

Cover: voice and tone (with three do/don't examples), punctuation rules for lists and code references, how to write headings (sentence case vs title case decision included), number and unit formatting, UI element naming conventions, and a banned-words list of at least ten jargon or filler terms to avoid.

For each section, include a concrete before-and-after example. Keep the whole guide scannable: use tables and short rules rather than paragraphs. End with a one-page quick-reference card that the writer can pin above their desk.