| name | simplified-technical-english |
| description | Write user-facing and reviewer-facing technical text in ASD-STE100 Simplified Technical English style. Use when drafting PR descriptions, commit message bodies, UI copy, docs, error messages, procedures, onboarding text, or any product wording that must stay clear for non-native readers. |
Simplified Technical English (ASD-STE100)
Write clear, unambiguous technical English. Prefer STE writing rules over clever
or idiomatic phrasing.
This skill applies STE writing rules (grammar and style). It does not
embed the copyrighted STE dictionary (~900 approved words). Use simple words
with one clear meaning; use SuperPlane technical nouns/verbs for product
terms. For full dictionary compliance, consult the official standard:
ASD-STE100.
Source: ASD-STE100 Issue 9 (January 2025), Standard for technical documentation.
ASD owns the STE trademark and standard; this skill is an operational distillation
for agents, not a substitute for the official document.
When this applies
| Text | STE mode |
|---|
| PR description Summary and Test plan | Descriptive + procedural |
| Commit message body | Descriptive |
| UI labels, buttons, helper text, empty states, errors, confirmations | Procedural / short descriptive |
| Docs, runbooks, onboarding steps | Procedural and/or descriptive |
Exceptions (do not rewrite these into STE):
- Conventional Commits type prefixes (
feat:, fix:, …)
- Code identifiers, API paths, proto names, log lines, and quoted error codes
- Proper nouns and product names (
SuperPlane, , )
