github-docslisted

# GitHub docs Help developers complete a product workflow with accurate, approachable guidance. ## Establish the contract - Preserve commands, UI labels, permissions, plan or product availability, code, versions, and security consequences. - Do not claim a feature exists for a plan, host, or version without evidence. - Distinguish a supported workflow from a workaround or community convention. - Surface missing facts as review questions. ## Design the page 1. Name the reader's goal in the title and opening. 2. State prerequisites, permissions, supported environments, and risks before the reader reaches a dependent action. 3. Give only enough concept to make the action understandable and safe. 4. Present the shortest supported path first. Place alternatives in separate sections. 5. Close the loop with verification, troubleshooting, or a useful next step. ## Write for developers - Address the reader as `you` and keep the tone calm and collaborative. - Use active voice and concrete verbs. Name the component that performs an automatic action. - Define product-specific terms on first use and keep terminology stable. - Put the most important qualifier near the claim it limits. - Explain why a step matters when the reason affects security, data, or the choice between alternatives. - Use inclusive language and examples that do not assume geography, identity, or a single development environment. - Separate normative instructions from optional suggestions. ## Write pro