Writing Simplified Technical English

作者 PostHog469d1773e9cb无许可证收录于 2026年10月8日更新于 2026年10月8日

Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and prompts. Also use it on request, with triggers like "simplify this", "make this readable", "too dense", "rewrite in STE", "simplified technical english", "ASD-STE100".

仅含说明Writing & Content
AI 生成的概览

应用 ASD-STE100 简化技术英语规则,让智能体撰写的文字含义明确、便于执行。

功能
提供一套清晰英语写作规则:一词一义、主动语态、简单时态、一句一个意思、句子简短。它包含改写流程、自查清单,以及详细规则和改写前后示例的参考文件。规则在写作过程中应用,而不是先写草稿再清理。
适用场景
适用于需要由人或另一个智能体据此行动的文字,例如报告、结论、PR 描述、提交信息、指令、工具描述、错误信息和提示词。也可按请求使用,触发语如“simplify this”或“rewrite in STE”。不适用于营销文案、博客文章等以语气和说服力为目的的写作。
运行要求
无需脚本或工具,仅为指令。它引用两个随附的 Markdown 文件,用于详细规则和示例。

Writing simplified technical English

ASD-STE100 is a controlled-language standard. The aerospace and defense industry wrote it so that a technician cannot misread a maintenance instruction. It removes the two biggest sources of misreading: words that carry more than one meaning, and sentences that support more than one structure.

The same discipline fixes the usual failure of agent-written prose. Agent output is often correct and unreadable: long sentences, stacked hedges, passive voice, and a synonym rotation that makes one action look like three. The reader has no author to ask, so ambiguity costs them a re-read at best and a wrong action at worst.

Apply the rules below as you write. Do not write a dense draft and clean it up afterward.

When to use this

Use it for text that a person or another agent must act on:

  • Reports, findings, and summaries.
  • PR descriptions, commit messages, and code comments.
  • Instructions passed to another agent, and prompts.
  • Tool descriptions, error messages, empty states, and log lines.

Do not use it where voice is the point: marketing copy, blog posts, or anything persuasive. STE is deliberately flat. Also leave quoted text alone. If you quote a user, a log, or a document, quote it as it is.

The rules

RuleDoDo not
One meaning per wordPick one verb per action and reuse it every timeRotate "check", "verify", and "confirm" for the same action
One part of speech per word"Apply oil to the valve""Oil the valve"
Active voice"The worker deletes the file.""The file is deleted."
Simple tenses"We received the report.""We have received the report."
One idea per sentence"Open the file. Read line 3.""Open the file and read line 3, then check it matches."
Sentence length20 words or fewer for instructions, 25 or fewer for descriptionsChains of subordinate clauses
Noun clusters3 words or fewer ("fuel pump valve")"high pressure fuel pump inlet valve assembly"
No missing wordsKeep the subject, the verb, and the article, even if it reads longer"Files not backed up will be lost", which hides which files
One hedge, at most"The client version is probably out of date.""An error may have occurred which could be caused by..."
ParagraphsOne topic, 6 sentences or fewerMulti-topic paragraphs
ListsUse a list for 3 or more steps or conditionsA sequence buried in one sentence
JargonKeep the technical term you need, and define it onceUse an internal name the reader has never seen

PostHog house style sits on top of these rules and wins where the two disagree. We use American English, sentence case, and the Oxford comma. We do not use the em-dash.

How to rewrite

  1. Read the text once for meaning. Do not start rewriting before you know what it must still say.
  2. Go sentence by sentence. Name the rule each sentence breaks.
  3. Rewrite the sentence to fix that break. Keep every fact, number, condition, and qualifier.
  4. Check the result against the rules again. A rewrite often introduces a new long sentence.

Precision beats brevity. If a shorter sentence would drop a safety condition, a scope qualifier, or a number, keep the longer sentence and say why.

If the text already follows the rules, say so. Do not change compliant text.

Self-check

Before you send the text, read it once and ask:

  • Does any sentence run past 25 words?
  • Does any sentence carry two instructions?
  • Does the same action appear under two different verbs?
  • Can a passive sentence name its actor?
  • Would a reader who joins here, with no context, know what to do next?

References

  • references/writing-rules.md: the detail behind the table, plus sources.
  • references/before-after.md: worked examples of the rewrite, including agent output.

来源与署名

来源:PostHog/ai-plugin位于skills/writing-simplified-technical-english提交469d177

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 PostHog/ai-plugin 的技能

Working With Task Comments

PostHog

通过 PostHog MCP exec 调度器读取并解读 PostHog 任务、产物和画布上的评论。

Productivity & Workflow2026年10月8日

Working With Skills

PostHog

指导智能体使用 PostHog 的 skill-* MCP 工具来发现、读取、创建、更新和重构技能。

AI & Agents2026年10月8日

Working With Scouts

PostHog

关于如何把监控任务委派给 PostHog Signals 侦察代理、处理其报告并长期调校整个代理集群的操作手册。

AI & Agents2026年10月8日

Validating And Publishing Canvases

PostHog

Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 version_conflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build returns diagnostics or a conflict, or a task needs to understand canvas version history.

待分类2026年10月8日

Understanding Billing Usage

PostHog

Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.

待分类2026年10月8日

Turning Engineering Analytics Into Insights

PostHog

将工程分析数据转化为已保存的 PostHog SQL 洞察、仪表盘和订阅,并提供 HogQL 指导。

Data & Analytics2026年10月8日