# Simplified Technical Language > Write, rewrite, or review technical text using the ASD-STE100 Simplified Technical English rules - controlled vocabulary, short sentences, active voice, one instruction per sentence. Use for manuals, procedures, work instructions, README steps, onboarding guides, UI help text, safety warnings, or when the user mentions STE, Simplified Technical English, ASD-STE100, controlled language, or writing for non-native readers. - Skill: `n0an/simplified-technical-language` (Agent Skill, multi-file: 8 files) - Install (CLI): `npx skillmds@latest add n0an/simplified-technical-language` - Raw SKILL.md: https://api.skillmd.com/api/skills/n0an/simplified-technical-language/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - License: MIT - Author: n0an (https://skillmd.com/u/n0an) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/n0an/simplified-technical-language --- # Simplified Technical Language Apply ASD-STE100 Simplified Technical English (STE), the international standard for clear technical documentation. STE was created for aviation maintenance, where a misread instruction can cause an accident, and is now used far beyond aviation. It has two parts: 1. **Writing rules** - 53 rules in 9 sections (words, noun phrases, verbs, sentences, procedures, descriptive writing, safety instructions, punctuation and word counts, writing practices). 1. **Dictionary** - about 900 approved general words, enough to write any technical sentence. Each approved word has one meaning and one approved part of speech. About 1,200 unapproved words are listed with approved alternatives. The current version is Issue 9 (January 2025), published free of charge at asd-ste100.org. The user provided: $ARGUMENTS ## Modes - pick one and read the listed references | Mode | When the request is | Read first | |---|---|---| | Rewrite | Convert existing text to STE | `references/rewriting-workflow.md`, then the reference for each problem class you find | | Write | Produce new instructions, procedures, or descriptions in STE | `references/procedures-and-safety.md` for procedures, `references/sentences-and-layout.md` for descriptions, plus `references/words.md` | | Review | Audit text for STE compliance and report violations without rewriting everything | All references, then use the Output Format below | If the request is small (one sentence, one warning), apply the core rules below directly and load only the reference you need. ## Core Instructions - First classify every part of the text as **procedural** (tells the reader to do something) or **descriptive** (gives information). The limits differ. - Keep procedural sentences to a maximum of 20 words. - Keep descriptive sentences to a maximum of 25 words. - Write one instruction per sentence. Combine instructions only when the reader must do them at the same time. - Use the imperative for instructions: "Remove the pump", not "The pump should be removed". - Use the active voice. It is mandatory in procedures and strongly preferred in descriptions. - Use only the approved verb forms: infinitive, imperative, simple present, simple past, simple future, and past participle as an adjective. No perfect or continuous tenses, no verb clusters like "should have been removed". - No -ing verb forms. An -ing word is acceptable only when it is itself a dictionary word ("during", "opening") or part of a technical name ("landing gear"). - Use one word for one meaning, and one meaning for one word. Use the same name for the same thing through the whole text. - Prefer short, common words: "start" not "commence", "use" not "utilize", "do" not "perform". See `references/substitutions.md`. - Keep noun clusters to a maximum of 3 nouns. Break longer clusters with prepositions or hyphens. - Never drop articles to save space: "Remove the pump", not "Remove pump". - Put the condition before the command: "If the pressure decreases, stop the test." - Keep paragraphs to a maximum of 6 sentences and one topic. Start each paragraph with the topic sentence. - Start warnings and cautions with a clear command. A note gives information only and must not contain a command. - Never change the technical meaning. If the source text is ambiguous, flag the ambiguity instead of guessing. - Technical names (part names, system names, tool names, units, error codes, API names, UI labels) and technical verbs (domain processes, computer operations like "click" or "download") are allowed even when they are not dictionary words. ## Output Format Never add an attribution line to the result - no "Written with Simplified Technical English", no mention of STE, ASD-STE100, or this skill. Return the text only. For a **rewrite**, return the rewritten text in chat. Keep the original structure (headings, step numbers, lists) unless it breaks an STE rule. If the input was a file, edit the file only when the user asks for that; otherwise show the result in chat. After the rewrite, list the significant changes in one short bullet list (rule area, what changed). For a **review**, organize findings by rule area, most severe first: 1. `Sentence and structure` - sentences over the limit, multiple instructions in one sentence, paragraphs over 6 sentences. 1. `Voice and verb forms` - passive voice in procedures, -ing forms, complex tenses, "should/shall". 1. `Words` - unapproved words with their approved alternatives, one term used with two meanings, two terms used for one thing. 1. `Noun phrases and articles` - clusters over 3 nouns, dropped articles. 1. `Safety instructions` - warnings that do not start with a command, notes that contain commands. For each finding give: the quoted text, why it breaks STE, and the STE rewrite. End with a fully corrected version of the worst passage as a sample. For **write** mode, produce the text directly in STE and say which template you used (procedure, description, or safety instruction). Example rewrite: Before: > Prior to commencing the installation procedure, it should be verified that all of the required mounting hardware components have been received and are undamaged. After: > Before you start the installation, make sure that you have all the mounting hardware. Make sure that the parts are not damaged. Changes: split one 24-word passive sentence into two active instructions, "prior to commencing" became "before you start", "verified" became "make sure", the 4-noun cluster "mounting hardware components" became "mounting hardware". End of example. ## References - `references/words.md` - the approved-word system: one word one meaning, part-of-speech control, technical names and technical verbs, consistency. - `references/substitutions.md` - common unapproved words and phrases with their approved alternatives. - `references/grammar.md` - approved verb forms, tenses, voice, noun clusters, articles, pronouns. - `references/sentences-and-layout.md` - sentence length limits, paragraphs, vertical lists, punctuation, word counting. - `references/procedures-and-safety.md` - writing instructions, step structure, warnings, cautions, and notes. - `references/rewriting-workflow.md` - the step-by-step conversion process, compliance checklist, and worked examples.