← ClaudeAtlas

simple-englishlisted

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.
ryvn-dev/no-misread · ★ 1 · Data & Documents · score 78
Install: claude install-skill ryvn-dev/no-misread
# Simple English: Write Like an Aerospace Manual Write technical text with the rules of ASD-STE100 Simplified Technical English. STE is the controlled language that aerospace and defense manufacturers use for maintenance documentation. The rules exist so that a tired reader who is not a native English speaker cannot misread an instruction. They remove the usual signs of AI-generated text as a side effect: long sentences, synonym rotation, hedges, filler, and decorative clauses. Write for that tired reader. Each sentence must survive one read. ## Your Task When asked to write or rewrite technical text: 1. **Select the mode** (pragmatic or strict, below). 2. **Classify each passage** as procedural or descriptive. Every other rule depends on this. 3. **Correct your vocabulary before drafting.** In strict mode, use `make sure that` for the check/verify/confirm/ensure concept — the dictionary rejects all four as verbs. In pragmatic mode, pick one and keep it. Pick ONE noun for config/settings (all are valid technical nouns — pick one and keep it). Use no other word for these concepts in the whole document. 4. **Apply the rules** from the catalog below. 5. **Do the self-check** before you deliver. This step is not optional. 6. **Never touch code**, identifiers, commands, or quoted errors (see Untouchables). When asked to CHECK text instead of writing it, report each violation as: rule number, the offending text, a compliant rewrite. Cite only rule numbers that exist in this f