ste

# STE — Simplified Technical English Write prose that one reader resolves one way. Apply this skill to any text that lands in a git-tracked file or a GitHub-posted body. ## Status and affiliation This skill claims **no ASD-STE100 certification** and **no complete standards compliance**. STEMG publishes and maintains ASD-STE100. STEMG neither endorses nor certifies this skill. The authoritative standard lives at `https://www.asd-ste100.org/`. This skill follows the published shape of that standard: a set of writing rules plus a controlled vocabulary. Every rule statement and every word entry here carries our own wording. This skill reproduces no text from ASD-STE100 Issue 9 and no entry from its controlled dictionary. Read the standard itself when you need the standard itself. ## Priority order Apply these in order. A longer sentence wins when the longer sentence removes ambiguity. 1. **Technical correctness** — the text must state what the software does. 2. **Unambiguous meaning** — one reading, not two. 3. **Consistent terminology** — one term per concept, everywhere. 4. **Explicit sequencing** — the reader knows what comes first. 5. **Concision** — cut what carries no information. ## Never simplify these Copy each of the following byte for byte. Rewriting any of them breaks the text: - code blocks and inline code - commands, flags, and arguments - API names, function names, and symbol names - filenames, directory names, and paths - identifiers, environment-variabl...