agentleFS
hiteshbandhuhiteshbandhu/skills-i-use/skills/ste100/SKILL.md

ste100

Skill1 starsChanged 5 months agoMITView on GitHub

Write explanations, documents and diagrams in ASD-STE100 Simplified Technical English (the aerospace controlled language, Issue 9, 2025), shaped to the document type and the reader's intent, and draw diagrams to engineering standards (IDEF0, ISO 5807, IEC 61082, S1000D-style callouts) in Hairline or Blueprint-minimalism style. Covers reports, PDFs, research papers, technical reports, internal memos, decision memos, status updates, PRDs, design docs/RFCs, ADRs, postmortems, runbooks/SOPs, guides/READMEs, executive briefs and release notes. Use when the user says "STE", "ASD-STE100", "simplified technical English", "80% STE", "plain technical English", "explain it like a maintenance manual", asks for a clearer or more readable explanation, or asks for any of those documents or a technical diagram that must be easy to follow — also together with the pdf or research-report skills when they produce the final file.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    One word, one meaning. One thing, one name: If you call it a "job", do not call it a "task" later.

    line 42
  2. Distinctive:

    Do not drop small words: Keep articles and "that": "Make sure that the port is open."

    line 45
  3. Distinctive:

    Lists for complex text: When a sentence has three or more parallel items or steps, use a vertical list.

    line 48
  4. Distinctive:

    Technical nouns and verbs are permitted: when they are terms in your subject field (rules 1.5, 1.12).

    line 55
  5. Distinctive:

    Do not use a technical noun as a verb ("to cache the value" → "to keep the value in the cache") unless the verb is also a standard …

    line 56
  6. Distinctive:

    Use American English spelling.

    line 57
  7. Distinctive:

    Decide the terms: Write a short term list first.

    line 97
  8. Very specific:

    Use --mode procedure for step lists.

    line 104
  9. Distinctive:

    Read it once as the reader: If a sentence can have two meanings, rewrite it.

    line 105
  10. Distinctive:

    Start the test suite.

    line 149
  11. Distinctive:

    Make sure that no test failure occurs.

    line 150

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ASD-STE100 Simplified Technical English

STE is a controlled language from aerospace maintenance. It has 53 writing rules and a dictionary of approved words. Each approved word has one meaning and one part of speech. The result is text that a tired, non-native reader can follow with no misunderstanding.

Source: ASD-STE100 Issue 9 (2025-01-15), free from https://www.asd-ste100.org. The full rules with examples are in references/rules.md. Document types, intent and structure are in references/documents.md. Diagram standards are in references/diagrams.md. Visual styles (Hairline and Blueprint minimalism) are in references/styles.md.

Pick a level

The full spec is strict. Pick the level from the request. When the request does not say, use standard.

LevelWhenWhat applies
strict"pure STE", safety text, text for translationAll rules. Only dictionary words plus technical nouns and verbs. Run the checker.
standard ("80% STE")Default. Explanations, runbooks, docsAll sentence, verb, procedure and structure rules. Prefer approved words, but use a normal word when the approved swap makes the text worse.
lightChat answers, quick notesShort sentences, active voice, one idea per sentence, commands for steps, no idioms.

The core rules (memorize these)

These rules give most of the value. They apply at every level.

  1. One idea in each sentence. Procedures: max 20 words. Descriptions: max 25 words.
  2. One instruction in each step. Two actions go in one step only when they occur at the same time.
  3. Steps use the command form. "Restart the worker." Not "The worker should be restarted."
  4. Active voice. Say who does the action: "The scheduler sends the job." Passive only in descriptions, and only when the agent is unknown.
  5. Simple tenses only. Present, past, future, and commands. No "has been", "is being", "would have".
  6. A verb for the action, not a noun. "Examine the logs." Not "Perform an examination of the logs."
  7. One word, one meaning. One thing, one name. If you call it a "job", do not call it a "task" later.
  8. No phrasal verbs. "set up" → "configure", "find out" → "find", "carry out" → "do".
  9. No contractions, no semicolons, no Latin ("e.g." → "for example", "i.e." → "that is", "etc." → "and other").
  10. Do not drop small words. Keep articles and "that": "Make sure that the port is open."
  11. Max 3 words in a noun cluster. "Cache invalidation retry policy timeout" → "the timeout of the retry policy for cache invalidation".
  12. Paragraphs: one topic, max 6 sentences. Give information gradually. Put the key point first.
  13. Lists for complex text. When a sentence has three or more parallel items or steps, use a vertical list.
  14. Notes give information, not commands. A command never hides in a note.
  15. Warnings first. A WARNING (risk to people) or CAUTION (risk to equipment or data) comes before the step. It starts with a command or condition, then gives the risk.

Words

  • Approved words have one meaning only. Example: "fall" means "move down by gravity", not "decrease". "Close" is a verb, not "near".
  • Technical nouns and verbs are permitted when they are terms in your subject field (rules 1.5, 1.12). In software this includes: database, endpoint, cache, commit, container, deploy, debug, install, reboot, download, upload, encrypt, scroll, click. Use the term your team uses, and use it consistently.
  • Do not use a technical noun as a verb ("to cache the value" → "to keep the value in the cache") unless the verb is also a standard technical verb.
  • Use American English spelling.

Common swaps (from the STE dictionary):

Do not useUse
ensure, verify, check (that)make sure (that)
check (look at)examine
utilizeuse
perform, accomplishdo
requirenecessary, must
shouldmust (a rule), or rewrite as a command
maycan, possibly
about (as "approximately")approximately
prior to / subsequent tobefore / after
due tobecause of
acceptablepermitted, satisfactory
obtain, acquireget
locatefind
indicateshow
commence, initiatestart
terminatestop
enoughsufficient
allow, enable (as "let")let
facilitatehelp
additionalmore
viathrough
whetherif
such asfor example
simultaneouslyat the same time
run (a test)do (or a technical verb your team defines)
failfailure (noun): "a failure occurs"
oldexpired, used, remaining

For any other word, check dictionary/unapproved.txt (after you build it, see below).

Workflow

  1. For a document (report, PDF, paper, memo, PRD, design doc, postmortem, guide), read references/documents.md first. Find the reader, the action they must take, the document type, and the trajectory (the section order that gets the reader to the action). The type also sets the STE level: procedures strict, papers light to standard, most others standard. The answer always comes first.
  2. Find the text type. Procedure (steps the reader does) or description (how something is or works). Most explanations are description plus a short procedure.
  3. Decide the terms. Write a short term list first. One name for each thing. Keep it for the full answer.
  4. Draft by the rules. Description: say what the thing is, then what it does, then how. Procedure: numbered steps, one command each, warnings before the step.
  5. Add a diagram when the text has more than three parts that connect. Follow references/diagrams.md for the structure and references/styles.md for the look (Hairline for one idea, Blueprint for parts and numbers). Draw only when a picture carries more than the text. Text refers to diagram items by number in parentheses, for example "the queue (3)".
  6. Check. For strict and standard level, run the checker on the draft and fix every error:
    python3 ~/.claude/skills/ste100/scripts/ste_check.py draft.md --mode descriptive --level standard
    Use --mode procedure for step lists. Word flags (info) are hints only. A flagged word can be a valid technical noun.
  7. Read it once as the reader. If a sentence can have two meanings, rewrite it.

Output shapes

Explanation of a system (descriptive):

## <Thing>
<Thing> is a <category> that <main function>.        ← one sentence, the key point

### Parts
- <Part A> (1): <function, one sentence>.
- <Part B> (2): <function, one sentence>.

### How it operates
1-6 short paragraphs. Each paragraph has one topic. Use the same names as the parts list.

[diagram with callouts (1), (2) …]

Procedure / runbook:

## <Task as a verb phrase: "Rotate the API keys">
Before you start: <conditions, tools, access>.

CAUTION: DO NOT ROTATE THE KEYS DURING A DEPLOY. THE SERVICE CAN STOP.

1. Open the secrets console.
2. Select the production project.
3. If the key expires in less than 30 days, click "Rotate".
   NOTE: The previous key stays active for 24 hours.
4. Make sure that the health check shows "OK".

Examples

Non-STE: "Once the cache has been warmed up, requests should be routed through the edge, which drastically reduces latency; however, stale entries may need to be purged manually."

STE (standard): "First, fill the cache. Then send the requests through the edge servers. This decreases the latency by a large quantity. The cache can keep expired entries. Remove these entries manually."

Non-STE: "To deploy, you'll want to make sure the tests pass and then tag the release, after which CI will pick it up."

STE procedure:

  1. Start the test suite.
  2. Make sure that no test failure occurs.
  3. Tag the release. NOTE: The CI system starts the deploy when it finds the new tag.

Dictionary setup (once)

The STE dictionary is copyrighted by ASD. It is free to download, but this skill does not include a copy. Build the local word lists from the official PDF:

python3 ~/.claude/skills/ste100/scripts/build_dictionary.py

This downloads Issue 9 and writes dictionary/approved.txt (about 730 headwords with verb forms) and dictionary/unapproved.txt (about 1,200 words with their approved alternatives). Do not redistribute these files. Grep them when you are not sure about a word:

grep -i "^ensure " ~/.claude/skills/ste100/dictionary/unapproved.txt

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.