simple-english
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE vocabulary compliance when the user names STE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, and explanations for readers outside the field. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "plain English", "layman's terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. The same rules govern the reply: answer first, five sentences or fewer.
AminBlg · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AminBlg/SimpleEnglish --skill simple-english技能说明
name: simple-english description: | Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before command, every technical term defined at first use, no AI slop. Default mode is Plain. Strict mode applies full STE vocabulary compliance when the user names STE, ASD-STE100, or compliance. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, and explanations for readers outside the field. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "plain English", "layman's terms", "explain it simply", "no jargon", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. The same rules govern the reply: answer first, five sentences or fewer. license: MIT compatibility: claude-code cursor codex gemini-cli opencode metadata: version: "2.0.0" standard: ASD-STE100 Issue 9 (2025-01-15)
Simple English: Plain Words, Aerospace Discipline
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.
Your Task
When asked to write or rewrite text:
- Select the mode (Plain or Strict, the table that follows). In Strict mode, read
references/strict-vocabulary.mdbefore you draft. - Classify each passage as procedural or descriptive. Every other rule depends on this.
- Fix your vocabulary before you draft. Use
make sure thatfor check/verify/confirm/validate/ensure as verbs, andconfigurationfor config/settings/options. Use no other word for these concepts in the whole document. - 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.
- Apply the catalog that follows. For replies and explanations for outsiders, apply the Plain English rules first.
- Do the self-check before you deliver. This step is not optional.
- 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 file, never from memory: invented rule numbers are a known failure.
Two Modes
| Mode | When | What you apply |
|---|---|---|
| Plain (default) | The user wants clear text: docs, READMEs, error messages, answers | Every structural rule in the catalog. Domain words stay ("idempotent", "webhook"). Replies and explanations for outsiders also get the Plain English rules. |
| Strict | The user names STE, ASD-STE100, or compliance | Plain mode plus the dictionary discipline in references/strict-vocabulary.md. Document only: the reply to the user stays Plain. |
Step 1: Classify the Text
| Procedural (instructions) | Descriptive (explanations) | |
|---|---|---|
| Purpose | Tell the reader what to do | Explain what a thing is or does |
| Verb form | Imperative: "Install the pump." | Simple present/past/future |
| Sentence limit | 20 words (Rule 5.1) | 25 words (Rule 6.3) |
| Unit rule | One instruction per sentence (5.2) | One topic per paragraph (6.5), max six sentences per paragraph (6.6) |
Do not mix the two in one passage. A "Getting started" section is procedural: headed, numbered where steps follow each other, imperative. An "Architecture" section is descriptive.
Plain English for Readers Outside the Field
Apply these six rules to your reply to the user and to explanations written for readers outside the field. Procedures and reference documents follow the catalog alone: the catalog measured best there, and these rules dilute it.
- Common word over jargon. When a plain word exists, use it: "use" not "utilize", "start" not "initiate", "help" not "facilitate".
references/word-swaps.mdhas the map. - Define a technical term at its first use when the reader needs it. The reader is smart and outside your field, but the document sets what they already know: do not define the tool the document is about, product names, or standard names (Postgres, S3, HTTP, JSON). Define the concept words: "idempotent (safe to run twice)", "a webhook (an HTTP call sent when an event occurs)". Keep a definition under ten words, at most one per sentence. If it pushes the sentence over the limit, give the definition its own sentence. Never use a synonym of a chosen term inside a definition (Rule 1.11).
- Address the reader as "you" and name the actor. Every sentence says who does what (Rule 3.6): "You run the migration. The database rebuilds the table."
- Lead with the point. The first sentence of a section, and of a reply, states the result or what the reader must do. Explanation follows.
- One idea per sentence, one topic per paragraph (Rules 5.2, 6.1, 6.5).
- Say what is true, not how important it is. "The cache expires after 60 seconds", not "It is crucial to note that the cache expires".
Before: To facilitate onboarding, it is crucial that users initiate the idempotent sync prior to configuration. After: Before you configure the client, start the sync. The sync is idempotent (you can run it again without side effects).
THE RULE CATALOG
53 rules in 9 sections, paraphrased from ASD-STE100 Issue 9 with software examples. Rules marked (S) are Strict mode only (see references/strict-vocabulary.md). The official wording is in the free standard at asd-ste100.org.
Section 1 — Words (Rules 1.1-1.14)
| Rule | Instruction |
|---|---|
| 1.1-1.4, 1.6 (S) | Use only approved words, as their l |