Eliminate AI Slop. Use ASD-STE100 for Extreme Clarity
The international Controlled Natural Language standard from the Aerospace and Defence Industries Association of Europe (ASD). Enforce atomic syntax, single-meaning vocabulary, and zero ambiguity to turn verbose LLM outputs into industrial-grade technical documentation.
“I often use a ladder of output formats from simple to advanced to constrain LLMs. Default unconstrained text is typically full of verbose, hand-wavy AI slop. When you prompt the model to aim for ASD-STE100 or ~80% of the way to ASD-STE100, the output immediately becomes crisp, compact, and auditable, drastically reducing human cognitive load.”
Strict controlled vocabulary: one word, one meaning, one part of speech. Eliminate deceptive polysemic conjunctions like as/since.
Procedures ≤20 words, descriptions ≤25 words. One physical action per sentence prevents cognitive memory overload.
Pre-tuned system prompts for Claude, GPT-4o, Cursor, and DeepSeek. Copy and paste instantly.
Client-side real-time grammar scanning, passive voice detection, unapproved word replacements, and one-click purification.
Online ASD-STE100 Linter & Purifier Studio
Type or paste English technical drafts to detect sentence length violations, passive voice, unapproved words, and AI fluff. Apply atomic rewrites in one click.
STE: 建议将复合格局拆分为 2~3 个独立的短句,确保逻辑扁平透明。
STE: 官方推荐替换为: "use"。理由: 学术/官僚虚伪浮夸词。STE 规定一律使用简单直接的 "use"。
STE: 官方推荐替换为: "to"。理由: 冗长套话。三个单词仅表达不定式 "to" 的含义,增加阅读阻力。
STE: 官方推荐替换为: "after"。理由: 拉长句子且含义单一,一律使用 "after"。
STE: 官方推荐替换为: "because"。理由: 极度啰嗦的 5 个单词,直接精简为 1 个词 "because"。
STE: 官方推荐替换为: "help / make easy"。理由: 典型 AI 废话高频动词,STE 一律替换为直白动词。
STE: 官方推荐替换为: "easily / without error"。理由: 营销虚词无度量标准,技术文档禁止使用主观修饰语。
Karpathy Tip: Aim for ~80% compliance in daily LLM prompts (active voice, ≤25 words, no AI slop) to enjoy massive reading gains.
Andrej Karpathy's Output Format Cognitive Ladder
Karpathy highlighted that human work is transitioning from information production to oversight and auditing. Choose the right format ladder to minimize cognitive drain.
Constrained Text (ASD-STE100)
Aerospace-grade controlled English: strictly limited sentence lengths (≤20/25 words), active voice, single-meaning words. Karpathy recommends "~80% of the way to ASD-STE100" as the practical sweet spot.
LLMs are actually exceptionally good at ASD-STE100. Constraining them to this standard makes text instantly crisp, clean, and directly usable as an operational checklist.
- ✓High signal-to-noise ratio, transparent logic
- ✓Zero ambiguity, ideal for auditing and checklists
- ✓Drastically reduces human cognitive load
- ✕Still requires linear reading
- ✕Inferior to diagrams for complex spatial/temporal topologies
Explain database indexing using 80% ASD-STE100 style.Expected Output Format: A database index is a data structure. It points to rows in a table. It helps the database find data quickly without reading the entire table...
9 Golden Rules of ASD-STE100
The top 9 aerospace writing principles to eliminate ambiguity, cut bureaucratic fluff, and deliver mission-critical technical clarity.
Sentence Length Limit: Procedures ≤20 Words, Descriptions ≤25 Words
Sentence Length Limitation (Max 20/25 Words)
Procedural steps must not exceed 20 words per sentence; descriptive explanations must not exceed 25 words per sentence.
"Before you begin the disassembly procedure of the hydraulic pump housing assembly, ensure that all residual system pressure has been completely relieved by turning the bleed valve counterclockwise until the pressure gauge indicator needle rests firmly at zero."
Diagnosis: Sentence contains 41 words with multiple subordinate clauses and gerunds, obscuring the primary pressure-release command.
Turn the bleed valve counterclockwise to release all hydraulic pressure. Make certain that the pressure gauge reads zero. Then remove the pump housing.
Improvement: Split into three atomic sentences (11, 9, and 5 words). The execution path is immediately clear.
Use the Active Voice Exclusively; Never Use Ambiguous Passive Voice
Use the Active Voice Exclusively
Procedural steps must be imperative (beginning with an uninflected verb). Descriptions must specify who performs the action.
One Word, One Meaning, One Part of Speech; Avoid Polysemic Confusion
One Word, One Meaning, One Part of Speech
Each approved word retains only one official meaning and part of speech. For instance, "close" is an adjective only; use "shut" as the verb.
Limit Noun Clusters: Maximum 3 Consecutive Nouns
Noun Clusters Limited to Maximum 3 Words
Do not string 4 or more nouns together. Unpack them with prepositions (of, for, in) to clarify relationships.
Disambiguate Conjunctions: If for Condition, When for Time, Because for Cause
Clear Conjunctions: If vs When, Because vs Since/As
Never use "as" or "since" to denote cause. Use "if" for conditions, "when" for time, and "because" for causality.
Atomic Instructions: One Command per Sentence
One Instruction per Sentence
Never chain multiple operational steps with "and". Each distinct physical action must have its own separate sentence.
Avoid Ambiguous -ing Participles and Complex Tenses
Avoid Ambiguous -ing Participles and Complex Tenses
Avoid dangling participles and progressive/perfect tenses. STE allows only simple present, past, and future.
Mandatory Controlled Vocabulary and Technical Name (TN) Guidelines
Controlled Vocabulary and Technical Terms
All unapproved verbs and adjectives must be replaced with approved STE vocabulary. Technical Names must remain standardized.
Safety Warnings Precede Steps (WARNING & CAUTION Placement)
Strict Safety Hierarchy: WARNING vs CAUTION vs NOTE
Place WARNING (injury/death) and CAUTION (equipment damage) notices immediately before the procedural step, never after.
ASD-STE100 Controlled Dictionary Quick Reference
STE strictly mandates one word, one meaning, one part of speech. Quickly look up forbidden words (utilize, prior to, ensure...) and their approved replacements.
Pretentious jargon. STE mandates the simple and direct verb "use".
Verbose filler. Three words that mean nothing more than the infinitive marker "to".
Ambiguous with harsh connotations. Use "stop" or "end" for processes; "disconnect" for electrical lines.
Carries unenforceable guarantee liability in aerospace law. STE standardizes on "make certain" or "verify".
Colloquial idiom. The approved STE expression is "make certain".
Stilted formal preposition. STE standardizes on "before".
Bureaucratic padding. Use "after".
容易导致主谓一致混乱和从属主次偏见,直接使用 "and"。
音节过长,STE 官方核准基础词为 "about" 或明确数值区间。
STE 规定 "close" 只能作形容词(如 close to the engine),关闭动作必须使用 "shut"。
空泛复杂的动词,执行指令用 "do",完成任务用 "complete"。
语义极其含糊。什么是“尽可能快”?STE 强调明确时间或使用 "immediately"。
"as" 既表示“当……时”又表示“因为”,极易产生时间/因果歧义。表示原因只能用 "because"。
"since" 既表示“自……以来”又表示“因为”,表示原因一律强制使用 "because"。
“following”在 STE 中只核准为形容词(the following items),引出后续事件必须用 "after"。
Extreme wordiness. Use "because".
官僚化动词,执行检查用 "do the inspection",进行测试用 "do the test"。
不必要的生僻大词,直接使用通用词 "start"。
虚无主语与被动语态,逃避建议发起者主体。
修改、变更统一使用受控动词 "change"。
多音节大词,一律用 "enough"。
典型 AI 废话高频动词,STE 一律替换为直白动词。
商业黑话 / AI 幻觉高频词,动词一律用 "use"。
Subjective marketing buzzword. Omit completely in technical documentation.
夸张的情感修饰词,STE 统一使用客观的 "important" 或 "necessary"。
AI Slop Defense: Prompt Engineering Templates
Pre-tuned Controlled Natural Language prompts for LLMs. Copy directly into Claude, ChatGPT, Cursor, or Multi-Agent pipelines.
Karpathy「80% STE」General Anti-Slop Prompt
The optimal balance between rigorous clarity and natural flow. Cuts out conversational filler, corporate fluff, and circular explanations.
Write your response aiming for ~80% of the way to ASD-STE100 (Simplified Technical English): 1. Keep procedural sentences under 20 words and descriptive sentences under 25 words. 2. Use active voice and direct imperative verbs for instructions (e.g., "Run the script", not "The script should be executed"). 3. Avoid generic AI filler words and fluffy qualifiers (e.g., cut out "delve into", "crucial", "seamlessly", "it is important to remember that", "in order to"). 4. One clear action or concept per sentence. 5. Prefer direct, simple words over bureaucratic vocabulary (use "use" instead of "utilize", "before" instead of "prior to", "stop" instead of "terminate"). 6. Maintain technical accuracy without unnecessary academic jargon.
Strict 100% Industrial ASD-STE100 Compliance Prompt
Strict adherence to official ASD-STE100 Issue 9 rules. Mandatory approved vocabulary, no passive voice, strict sentence length bounds, and safety alerts.
You are an expert technical writer certified in ASD-STE100 (Simplified Technical English, Issue 9). Rewrite the given text to achieve strict 100% compliance with the ASD-STE100 specification: - SENTENCE LENGTH: Procedural sentences must not exceed 20 words. Descriptive sentences must not exceed 25 words. - VOICE: Active voice only. Procedural steps must be imperative. No passive voice allowed in procedures. - VOCABULARY: Use ONLY approved words from the ASD-STE100 General Dictionary or valid Technical Names (TN) / Manufacturing Processes (MP). - ONE WORD ONE MEANING: Respect approved parts of speech (e.g., "close" is only an adjective; use "shut" as the verb; "following" is only an adjective; use "after" as preposition). - NOUN CLUSTERS: Maximum 3 consecutive nouns. Break larger clusters using prepositions. - CONJUNCTIONS: Use "if" for conditions, "when" for time, and "because" for cause. Do not use "as" or "since" to indicate reason. - STRUCTURE: One instruction per sentence. Separate combined steps into individual sequential items. - SAFETY: Format safety warnings as WARNING (personal injury/death) or CAUTION (damage to equipment) before the step.
Cursor / Claude Code Developer Docs & Comment Standard
Designed for READMEs, API specifications, and docstrings across software codebases to maintain high signal density.
You are writing technical software documentation following ASD-STE100 principles:
- Write short, declarative docstrings and API explanations.
- For functions and methods: Start with an active verb ("Calculate hash", "Send request", "Parse JSON payload").
- Eliminate redundant introductory explanations like "This function is responsible for...".
- Bullet points must be atomic: one prerequisite or action per line.
- When describing errors, use: "If [condition occurs], the system returns [error code] because [root cause]."
- Keep code comments crisp, factual, and devoid of subjective adjectives.Multi-Agent Clean Exit Filter
Placed at the final output boundary of a Multi-Agent System to strip verbose chain-of-thought and politeness before executive human review.
You are the Final Communication Filter for an autonomous multi-agent pipeline.
Your task is to take the complex intermediate reasoning and synthesis from prior agents and rewrite the final output for executive human review:
1. Strip all conversational pleasantries ("Sure! I would be happy to help with that", "Hope this helps!").
2. Convert rambling narrative into a high-density, ASD-STE100 structured action summary.
3. Highlight:
- WHAT changed (Facts only)
- WHY it was required (Root cause)
- ACTION required from human (Clear verification steps)
4. Enforce strict sentence limits (<=20 words per bullet).Before vs After: From AI Slop to Industrial Precision
Examine real-world engineering comparisons to see how ASD-STE100 dramatically boosts clarity, brevity, and auditability.
Removing AI Slop from Microservices & Service Mesh Explanations
When prompted to explain microservices, default LLM outputs drown in bloated passive constructions and corporate jargon.
"In the contemporary paradigm of distributed systems, it is of paramount importance to recognize that microservices architecture fundamentally leverages containerization in order to facilitate agile deployment methodologies, whilst service meshes are subsequently utilized to seamlessly orchestrate inter-service communication and mitigate latency bottlenecks that might otherwise be inadvertently introduced."
Microservices divide a software application into small independent services. Each service runs in its own container. A service mesh manages the network traffic between these services. It monitors data flow, prevents service failure, and keeps response times fast.
Key Takeaways
FAQ & Domain Errata Notes
Everything you need to know about ASD-STE100 and the story behind asd-std100.top.
This addresses a classic typographical and phonetic confusion! The official international standard is ASD-STE100 (Simplified Technical English), hosted at asd-ste100.top. However, many beginners inadvertently search for "ASD-STD100" by confusing "Standard" (STD) with "STE". To ensure developers and aerospace engineers find the accurate standard immediately, we route both domains here to provide comprehensive errata guidance and the most practical interactive STE lab!
ASD-STE100 STEMG Committee Official Portal
Apply for the official Issue 9 specification manual, change logs, and international certification updates.