← ClaudeAtlas

simple-englishlisted

Write or rewrite procedural technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. A procedure is an instruction, a step, a warning, or a safety note. Use for runbooks, setup and install steps, procedures, error messages, the steps in release notes, agent instructions, and the steps inside a README, a plan, a design document, an issue, or a code comment. An explanation (a design rationale, descriptive README text, a docstring, a commit body, a PR description, an issue body) follows guides/explanations.md of the writing plugin instead. For a commit message, a PR title, or a PR description, use the `writing:commit-message` skill. 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: a 20-word sentence limit for an instruction, one word one meaning, simple tenses, active voice, condit
rgant/claude-plugins · ★ 0 · Data & Documents · score 78
Install: claude install-skill rgant/claude-plugins
# Simple English: Write Like an Aerospace Manual This skill adapts the `simple-english` skill of [AminBlg/SimpleEnglish](https://github.com/AminBlg/SimpleEnglish), under the MIT license. [LICENSE-SimpleEnglish](../../LICENSE-SimpleEnglish) holds its copyright and permission notice. Write procedural 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. This skill covers the procedure register: an instruction, a step, a warning, or a safety note. An explanation says what a system does and why, and it follows `${CLAUDE_PLUGIN_ROOT}/guides/explanations.md`. A document often holds procedures and explanations, so classify each sentence or section, not the whole file. ## 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. **Fix your vocabulary before drafting.** Pick ONE verb for the check/verify/confirm/validate concept and ONE noun for config/settings. Use no other word for these concepts in