asd-ste100

Solid

Use when writing technical procedures, instructions, warnings, maintenance manuals, or any text where every reader including non-native English speakers must understand exactly one meaning.

AI & Automation 33 stars 1 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
51
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# ASD-STE100 Simplified Technical English Control vocabulary and syntax to eliminate ambiguity in technical documentation. ## The core rule **One word, one meaning. Imperative voice for instructions. Maximum 20 words per sentence.** Workflow: `choose approved STE vocabulary` → `write imperative command` → `restrict sentence length to 20 words max` → `verify zero ambiguity`. ## Mechanics 1. **Approved vocabulary.** Use only words from the ASD-STE100 dictionary or approved technical nouns. 2. **Imperative commands.** Start steps with an action verb ("Remove the bolt", not "You should remove the bolt"). 3. **Word count limits.** Maximum 20 words for procedural sentences; maximum 25 words for descriptive sentences. 4. **No noun clusters.** Maximum of 3 nouns in a sequence (e.g. use "valve control switch" instead of "engine fuel system valve control switch"). 5. **Present tense.** Describe current states in present tense; avoid future tense ("The light is on" not "The light will turn on"). 6. **No gerunds in titles.** Use simple nouns or infinitives for headings. 7. **Explicit conditions.** Place conditional clauses at the beginning of the sentence ("If the pressure is low, replace the filter"). 8. **Approved modifiers.** Avoid vague adjectives like "extreme", "rapid", or "normal" unless quantified. ## Verify - Sentences do not exceed 20 words for procedures - Every instruction starts with an active imperative verb - No noun clusters exceeding 3 words - All technical terms...

Details

Author
surendranb
Repository
surendranb/writing-skills
Created
4 weeks ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

simplified-technical-english

Use when writing, revising, or checking procedures, maintenance instructions, safety notices, product documentation, or technical explanations under ASD-STE100 for international readers.

2 Updated 1 weeks ago
rookslog
Code & Development Listed

ste100

Apply ASD-STE100 Simplified Technical English (STE) — the aerospace and defense controlled-language standard — to technical writing: procedures, descriptions, maintenance records, and safety warnings. Use when Shane says: "apply STE100 to this", "apply STE to this", "simplified technical english", "make this STE-compliant", "review for ASD-STE100", "STE check this", "rewrite this as a procedure in STE". Also invoke proactively when reviewing step-by-step instructions, work cards, or safety-critical warnings that must be unambiguous for a non-native-English reader.

0 Updated 1 months ago
slogsdon
Data & Documents Listed

simple-english

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.

1 Updated 3 weeks ago
ryvn-dev