Skip to content

urmzd/dotfiles / dot_agents/skills/asd-ste100

asd-ste100

Verified

Write or rewrite text in ASD-STE100 Simplified Technical English (STE): the approved-word dictionary discipline, controlled verb forms, sentence and paragraph limits, procedural vs descriptive rules, and safety-instruction structure. Use when the user asks for Simplified Technical English, STE, ASD-STE100, controlled language, or aerospace-style technical writing, or when authoring procedures, maintenance instructions, or safety warnings that must be unambiguous. Do NOT use for general documentation cleanup (use clean-docs), README structure (use write-readme), or ordinary prose style.

Simplified Technical English (ASD-STE100)

Apply the ASD-STE100 specification (Issue 8) when writing or rewriting technical text. STE is a controlled language: a restricted dictionary plus writing rules that remove ambiguity for readers whose first language is not English and for machine parsing.

When to Use

  • The user invokes /asd-ste100 or asks for STE, Simplified Technical English, or controlled language.
  • The user asks to write or review procedures, work instructions, maintenance steps, or safety warnings that must be unambiguous.
  • The user asks to "simplify" documentation explicitly to a controlled standard, not just tidy it.

Core Principles

  1. One word, one meaning. Each approved word has exactly one meaning and one part of speech. If a word is approved as a noun, do not use it as a verb.
  2. Approved words only. General vocabulary comes from the STE dictionary (about 900 words). Everything else must qualify as a Technical Name or a Technical Verb.
  3. Short, direct, active. Short sentences, active voice, one instruction per sentence.

Vocabulary Rules

RuleStandard
Approved meaning onlyUse a dictionary word only in its approved meaning. Example: "fall" means only "to move down by the force of gravity", never "decrease" or "autumn".
Approved part of speech"test" is approved as a noun only: write "Do a test of the system", not "Test the system".
Prefer the approved alternative"start" replaces "begin, commence, initiate". "do" replaces "carry out, perform". "before" replaces "prior to".
Technical NamesNouns specific to the domain (part names, tools, materials, system names) are allowed even if not in the dictionary. Use them consistently and only as nouns.
Technical VerbsDomain-specific actions (e.g. "to calibrate", "to drill") are allowed as verbs when no approved verb exists.
No slang or idiomsRemove figurative language, phrasal padding, and Latin abbreviations (write "for example", not "e.g.").

Grammar Rules

RuleStandard
Verb formsUse only: infinitive, imperative, simple present, simple past, future with "will", and past participle as an adjective.
No -ing verb formsDo not use gerunds or present participles ("Removing the cover..." becomes "When you remove the cover..."). An -ing form is allowed only inside a Technical Name.
Active voiceUse active voice in procedures always. In descriptive text, use passive only when the agent is unknown or unimportant.
Articles requiredDo not drop articles or demonstratives: "Install the panel", not "Install panel".
Noun clustersMaximum three nouns in a cluster. Break longer clusters with prepositions: "the fan of the cooling system", not "cooling system fan assembly housing".
Consistent namingUse the same name for the same thing everywhere. No elegant variation.

Sentence and Paragraph Rules

RuleStandard
Procedural sentence lengthMaximum 20 words.
Descriptive sentence lengthMaximum 25 words.
Paragraph lengthMaximum 6 sentences. One topic per paragraph.
One instruction per sentenceSplit compound instructions. Only closely related actions may share a sentence.
Commands start instructionsProcedures begin with the imperative verb: "Remove the bolts", not "The bolts should be removed".
Vertical listsUse a list when a sentence would hold more than three connected items.

Warnings, Cautions, and Notes

  • Warning: risk of injury or death. Caution: risk of equipment damage. Note: helpful information only. Never put an instruction in a note.
  • Put the warning or caution before the step it applies to.
  • Start with a clear and simple command, then give the condition or reason: "WARNING: Do not touch the terminal. The terminal has a dangerous voltage."

Rewriting Workflow

  1. Classify the text. Procedural (instructions) or descriptive (explanations). The sentence limits and voice rules differ.
  2. Split and shorten. Break sentences over the word limit. One instruction per sentence, one topic per paragraph.
  3. Convert the verbs. Imperatives for steps, simple present for description, remove -ing forms and passives.
  4. Substitute vocabulary. Replace unapproved general words with approved alternatives. Keep Technical Names and Technical Verbs, used consistently.
  5. Restructure safety text. Move warnings and cautions before their steps, command first.
  6. Verify. Recheck sentence lengths, noun clusters, articles, and that no word is used outside its approved meaning.

Example

Before:

Prior to commencing disassembly, ensuring the power has been disconnected is essential, as failure to do so may result in serious injury being sustained by maintenance personnel.

After:

WARNING: Disconnect the power before you disassemble the unit. If you do not disconnect the power, injury can occur.

Gotchas

  • Do not apply STE to marketing copy, READMEs, or conversational docs unless asked. STE prose reads as terse and repetitive by design.
  • Do not invent approved words. When unsure whether a general word is in the dictionary, prefer a simpler common alternative ("use", "make", "get", "do", "start", "stop").
  • "May" is not approved for permission or possibility; use "can" for possibility.
  • Keep required legal or certified text verbatim; STE rewrites must not alter regulatory wording.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall