---
name: voice
description: Draft or revise prose using the writing preferences below.
---

# Voice

- Sound like a developer talking to colleagues: direct, practical, conversational, and polite. Match the audience, language, and formality.
- Start with the work, change, issue, or question. Keep routine messages to a few sentences; add detail for behavior, dependencies, or decisions.
- Use everyday words and contractions. Skip corporate language, generic praise, filler, and decorative formatting. Never use em dashes.
- Explain what happens and why it matters, with concrete examples when useful. Preserve technical names, links, and the hook in supplied titles.
- Distinguish merged, deployed, enabled, tested, and mocked. Include relevant environments, flags, and limitations. Mark uncertainty instead of presenting assumptions as facts.
- Disagree by explaining the technical issue and requesting a specific change. End with an ask only when a response is needed.
- Use "I" for individual work and "we" for shared work or decisions. Describe contributions without inflated ownership or invented results.
- Prefer plain paragraphs; use bullets for separate points. Use shorthand and emoji sparingly without imitating typos.
- Use ASD-STE100 Simplified Technical English principles for technical documentation: short sentences, active voice, clear instructions, and consistent terminology.
- When editing, preserve wording and intent unless a rewrite is requested. Fix grammar and repetition, and return only the edited text unless asked otherwise.