Recommended by Andrej Karpathy (2026)|80% ASD-STE100 Standard

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.”

AK
Andrej Karpathy
Former Director of AI at Tesla / OpenAI Co-founder (Oct 2026)
Official Spec Issue 9
Aerospace Zero Ambiguity

Strict controlled vocabulary: one word, one meaning, one part of speech. Eliminate deceptive polysemic conjunctions like as/since.

Atomic Short Sentences

Procedures ≤20 words, descriptions ≤25 words. One physical action per sentence prevents cognitive memory overload.

Ready-to-Use Prompts

Pre-tuned system prompts for Claude, GPT-4o, Cursor, and DeepSeek. Copy and paste instantly.

Interactive Online Linter

Client-side real-time grammar scanning, passive voice detection, unapproved word replacements, and one-click purification.

Real-Time STE Diagnostics

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.

Load Preset Scenario:
16
STE Compliance
Low Pass
Total Words
48
Sentences
1
Max Sentence
48
Detected Rule Violations
7
Draft Input:Max ≤25 words
Sentence Breakdown (1)
#1It is crucial to note that in order to seamlessly facilitate optimal performance across the distributed infrastructure, developers must utilize specialized caching mechanisms, due to the fact that excessive latency can adversely impact user experience subsequent to traffic spikes, which should be continuously monitored by the engineering team.
超长 (48词)禁用词: utilize → use禁用词: in order to → to禁用词: subsequent to → after禁用词: due to the fact that → because禁用词: facilitate → help / make easy禁用词: seamlessly → easily / without error
48 w
Detected Rule Violations (7)Action Required
句子字数 (48 词) 超出 STE 建议上限 (25 词)#1

STE: 建议将复合格局拆分为 2~3 个独立的短句,确保逻辑扁平透明。

未核准/冗余词汇: "utilize"#1

STE: 官方推荐替换为: "use"。理由: 学术/官僚虚伪浮夸词。STE 规定一律使用简单直接的 "use"。

未核准/冗余词汇: "in order to"#1

STE: 官方推荐替换为: "to"。理由: 冗长套话。三个单词仅表达不定式 "to" 的含义,增加阅读阻力。

未核准/冗余词汇: "subsequent to"#1

STE: 官方推荐替换为: "after"。理由: 拉长句子且含义单一,一律使用 "after"。

未核准/冗余词汇: "due to the fact that"#1

STE: 官方推荐替换为: "because"。理由: 极度啰嗦的 5 个单词,直接精简为 1 个词 "because"。

未核准/冗余词汇: "facilitate"#1

STE: 官方推荐替换为: "help / make easy"。理由: 典型 AI 废话高频动词,STE 一律替换为直白动词。

未核准/冗余词汇: "seamlessly"#1

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.

Cognitive Bandwidth & Hierarchy

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.

Level 1 → 5Select
Level 2High Signal Density (Optimal)

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.

Karpathy's Key Insight

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.

Core Advantages / Signal
  • ✓High signal-to-noise ratio, transparent logic
  • ✓Zero ambiguity, ideal for auditing and checklists
  • ✓Drastically reduces human cognitive load
Main Limitations / Noise
  • ✕Still requires linear reading
  • ✕Inferior to diagrams for complex spatial/temporal topologies
Recommended Prompt:
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...

International Standard Essentials

9 Golden Rules of ASD-STE100

The top 9 aerospace writing principles to eliminate ambiguity, cut bureaucratic fluff, and deliver mission-critical technical clarity.

STE-R1Rule #1

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.

Why this rule exists:Long sentences create convoluted clause hierarchies, causing short-term memory overload and misinterpretation during critical operations.
Violation (Non-STE):

"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.

Approved (STE Approved):

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.

STE-R2Rule #2

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.

Why this rule exists:Passive voice (e.g., "It must be checked") hides the responsible party, inviting errors or missed checks during maintenance.
STE-R3Rule #3

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.

Why this rule exists:Polysemy is a major pitfall in international translation. "Close the valve" invites ambiguity, whereas "Shut the valve" is unambiguous.
STE-R4Rule #4

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.

Why this rule exists:Phrases like "overhead cabin air conditioning compressor control valve switch" force the reader to backtrack to find the head noun.
STE-R5Rule #5

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.

Why this rule exists:In "Since the pump stopped...", does "since" mean "ever since" (time) or "because" (reason)? The ambiguity can cause fatal delays.
STE-R6Rule #6

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.

Why this rule exists:Maintenance personnel check off items step-by-step. Combining actions in one sentence risks skipping subsequent steps.
STE-R7Rule #7

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.

Why this rule exists:The suffix "-ing" can function as participle, gerund, or adjective, frequently creating dangling modifiers whose subject is unclear.
STE-R8Rule #8

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.

Why this rule exists:Synonym swapping in technical writing causes confusion. Using "utilize", "apply", "employ" interchangeably creates doubt.
STE-R9Rule #9

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.

Why this rule exists:If a warning is placed after the command, a technician might perform the hazardous action before reading the warning.
Controlled Vocabulary Lookup

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.

utilizeuseVerb

Pretentious jargon. STE mandates the simple and direct verb "use".

✕ Utilize this tool to adjust the screw.
✓ Use this tool to adjust the screw.
in order totoConjunction Phrase

Verbose filler. Three words that mean nothing more than the infinitive marker "to".

✕ Press the button in order to initiate testing.
✓ Push the button to start the test.
terminatestop / end / cancel / disconnectVerb

Ambiguous with harsh connotations. Use "stop" or "end" for processes; "disconnect" for electrical lines.

✕ Terminate the ongoing background process.
✓ Stop the background process.
ensuremake certain / verifyVerb

Carries unenforceable guarantee liability in aerospace law. STE standardizes on "make certain" or "verify".

✕ Ensure that the valve is closed.
✓ Make certain that the valve is shut.
make suremake certainVerb Phrase

Colloquial idiom. The approved STE expression is "make certain".

✕ Make sure the indicator is green.
✓ Make certain that the indicator light is green.
prior tobeforePreposition

Stilted formal preposition. STE standardizes on "before".

✕ Disconnect the power prior to opening the box.
✓ Disconnect the power before you open the box.
subsequent toafterPreposition

Bureaucratic padding. Use "after".

✕ Subsequent to the test, clean the unit.
✓ After the test, clean the unit.
as well asandConjunction

容易导致主谓一致混乱和从属主次偏见,直接使用 "and"。

✕ Inspect the valve as well as the seal.
✓ Inspect the valve and the seal.
approximatelyabout / almostAdverb

音节过长,STE 官方核准基础词为 "about" 或明确数值区间。

✕ Wait for approximately 5 minutes.
✓ Wait for about 5 minutes.
close (as verb)shutVerb

STE 规定 "close" 只能作形容词(如 close to the engine),关闭动作必须使用 "shut"。

✕ Close the inspection door securely.
✓ Shut the access door.
accomplishdo / completeVerb

空泛复杂的动词,执行指令用 "do",完成任务用 "complete"。

✕ Accomplish the maintenance task.
✓ Do the maintenance task.
as soon as possible (ASAP)immediately / at onceAdverb Phrase

语义极其含糊。什么是“尽可能快”?STE 强调明确时间或使用 "immediately"。

✕ Report the oil leakage as soon as possible.
✓ Report the oil leak immediately.
as (conjunction for cause)becauseConjunction

"as" 既表示“当……时”又表示“因为”,极易产生时间/因果歧义。表示原因只能用 "because"。

✕ Do not touch the pipe as it is hot.
✓ Do not touch the pipe because it is hot.
since (conjunction for cause)becauseConjunction

"since" 既表示“自……以来”又表示“因为”,表示原因一律强制使用 "because"。

✕ Turn off the pump since pressure is high.
✓ Stop the pump because the pressure is high.
following (as preposition)afterPreposition

“following”在 STE 中只核准为形容词(the following items),引出后续事件必须用 "after"。

✕ Following the installation, calibrate the sensor.
✓ After the installation, calibrate the sensor.
due to the fact thatbecauseConjunction Phrase

Extreme wordiness. Use "because".

✕ The engine stalled due to the fact that the filter was clogged.
✓ The engine stopped because the filter was dirty.
performdo / makeVerb

官僚化动词,执行检查用 "do the inspection",进行测试用 "do the test"。

✕ Perform the functional test.
✓ Do the functional test.
initiatestartVerb

不必要的生僻大词,直接使用通用词 "start"。

✕ Initiate the boot sequence.
✓ Start the computer.
it is recommended thatwe recommend that / you shouldPassive Phrase

虚无主语与被动语态,逃避建议发起者主体。

✕ It is recommended that masks be worn.
✓ You must wear a protective mask.
modifychangeVerb

修改、变更统一使用受控动词 "change"。

✕ Modify the configuration settings.
✓ Change the configuration.
sufficientenoughAdjective

多音节大词,一律用 "enough"。

✕ Check that there is sufficient clearance.
✓ Make certain that there is enough space.
facilitatehelp / make easyVerb

典型 AI 废话高频动词,STE 一律替换为直白动词。

✕ This handle facilitates quick removal.
✓ This handle helps you remove the panel quickly.
leverage (as verb)useVerb

商业黑话 / AI 幻觉高频词,动词一律用 "use"。

✕ Leverage the built-in diagnostic tool.
✓ Use the diagnostic tool.
seamlesslyeasily / without errorAdverb

Subjective marketing buzzword. Omit completely in technical documentation.

✕ The system seamlessly integrates with the database.
✓ The system connects to the database directly.
crucial / vital / pivotalimportant / necessaryAdjective

夸张的情感修饰词,STE 统一使用客观的 "important" 或 "necessary"。

✕ It is crucial to seal the pipe.
✓ You must seal the pipe.
Ready-to-Copy System Prompts

AI Slop Defense: Prompt Engineering Templates

Pre-tuned Controlled Natural Language prompts for LLMs. Copy directly into Claude, ChatGPT, Cursor, or Multi-Agent pipelines.

Recommended by KarpathyClaude 3.7 / GPT-4o / Gemini 2.5 / DeepSeek R1

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.
Implementation Tips: Ideal as a system prompt for coding assistance, architectural explanations, and technical decisions to maximize reading speed.
Aerospace & Industrial ComplianceClaude 3.5 Sonnet / GPT-4.5 / O3-Mini

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.
Implementation Tips: Essential for export machinery documentation, drone flight manuals, international avionics procedures, and medical device guidelines.
IDE & Agent System PromptCursor Rules (.cursorrules) / Claude Desktop / Copilot

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.
Implementation Tips: Copy directly into your project's .cursorrules or CLAUDE.md to enforce clean, concise documentation across your repository.
Recommended for Agent PipelinesLangGraph / AutoGen / CrewAI / Swarm 后置节点

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).
Implementation Tips: Attach to the final node of your agent workflow to ensure human reviewers grasp all key facts in under 10 seconds.
Industrial Domain Comparisons

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.

AI Architecture Explanation

Removing AI Slop from Microservices & Service Mesh Explanations

When prompted to explain microservices, default LLM outputs drown in bloated passive constructions and corporate jargon.

Before (Default LLM / Complex Text)52 words / 1 sent

"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."

Passives: 3Very High (78% Filler Words)
After (ASD-STE100 Compliant)39 words / 4 sent

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.

Passives: 00% (Pure Signal & Facts)

Key Takeaways

Word count cut by 25%, readability boosted by 300%
Completely eliminated "paramount importance", "fundamentally leverages", "in order to facilitate"
Unpacked a 52-word sentence into 4 atomic sentences, each under 15 words
Frequently Asked Questions

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!

📌 Key Note: ASD-STE100 (Simplified Technical English) vs. "STD100".

ASD-STE100 STEMG Committee Official Portal

Apply for the official Issue 9 specification manual, change logs, and international certification updates.

asd-ste100.org