What it does. Write plain English that a smart reader outside your field understands on one read. The rules come from ASD-STE100, the controlled language aerospace uses so a tired mechanic cannot misread an instruction. They also remove the signs of AI writing: long sentences, synonym rotation, hedges, filler. Each sentence must survive one read.
- Select the mode (Plain or Strict, the table that follows). In Strict mode, read
references/strict-vocabulary.md
before you draft. 2. Classify each passage as procedural or descriptive. Every other rule depends on this. 3. Fix your vocabulary before you draft. Use make sure that
for check/verify/confirm/validate/ensure as verbs, and configuration
for config/settings/options. Use no other word for these concepts in the whole document. 4. Define a technical term at its first use when a reader outside the field needs it: concept words, not product names or the tool the document is about. 5. Apply the catalog that follows. For replies and explanations for outsiders, apply the Plain English rules first. 6. Do the self-check before you deliver. This step is not optional. 7. Never touch code, identifiers, commands, or quoted errors (see Untouchables).
When to use it. Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: one idea per sentence, controlled vocabulary, no ambiguity.
Install
npx skills add AminBlg/SimpleEnglish --skill simple-english
Or copy the skill folder manually:
git clone https://github.com/AminBlg/SimpleEnglish.git
cp -r SimpleEnglish/skills/simple-english/ ~/.claude/skills/simple-english
Source: AminBlg/SimpleEnglish — 3,118 stars, MIT, last pushed 2026-09-02.
