← ClaudeAtlas

simplified-technical-englishlisted

Enforce ASD-STE100 Simplified Technical English (STE) in all technical documentation you write or edit. Use this skill whenever you draft, generate, or revise READMEs, specifications, design docs, architecture decision records (ADRs), runbooks, technical playbooks, API docs, configuration and setup guides, troubleshooting guides, release notes, inline code comments, or docstrings — any project documentation that describes technical aspects of a system. Apply it even when the user does not mention "STE", "controlled language", or "plain English". It keeps documentation short, active, and consistent so a global audience with basic English can read it correctly the first time. Do not apply it to marketing copy, casual chat replies, or narrative prose where a natural voice is wanted.
ebellefontaine/eric-ai-plugins · ★ 0 · AI & Automation · score 58
Install: claude install-skill ebellefontaine/eric-ai-plugins
# Simplified Technical English (ASD-STE100) ## What this is and why it matters ASD-STE100 Simplified Technical English (STE) is a controlled language for technical documentation. It exists because technical readers are often non-native English speakers, are under time pressure, or are acting on safety-critical steps. Ambiguous or complex writing causes misreading, and misreading a procedure has real cost. STE reduces that risk by limiting vocabulary and grammar to a small, consistent set. You write plainly, one idea at a time, so the reader does not have to decode the sentence before doing the work. STE is owned and trademarked by ASD (Brussels). The full standard (Issue 9, January 2025) has 53 writing rules and a dictionary of about 900 approved words. The dictionary is proprietary and is not reproduced here. This skill applies the public writing rules and general word-choice principles. When a project must formally certify against STE, use the official standard from https://www.asd-ste100.org/ as the authority. ## When to apply it Apply STE to the technical content you produce, including: - READMEs and getting-started guides - Specifications and requirements - Architecture decision records (ADRs) and design docs - Runbooks, operational playbooks, and troubleshooting guides - API documentation, configuration guides, and setup instructions - Release notes and changelogs - Inline code comments and docstrings Do not force STE on marketing copy, blog posts, casual messag