asd-ste100

ASD-STE100: Simplified Technical English & 80% Karpathy Mode

Claude Code Plugin · Mod · Agent Skill · Linter & CLI
Controlled technical English specification to minimize cognitive load, eliminate ambiguity, and optimize LLM reasoning and human oversight.

---

📌 Background & Motivation

As AI coding and autonomous agents perform more legwork, human engineers spend significantly more time reviewing, understanding, and validating LLM outputs.

Former OpenAI Chief Scientist and Tesla AI Director Andrej Karpathy highlighted this paradigm shift:

"Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for '80% of the way to ASD-STE100' because the spec is quite stringent...

In summary:

• As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
• Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before." — Andrej Karpathy on X

This repository packages ASD-STE100 into a complete ecosystem:

1. Claude Code Mod (hooks/register.js): An internal Claude Code extension that adds /asd commands, UI status indicators, the STE pane, and STE rules in the system prompt.
2. Claude Code Plugin (.claude-plugin/plugin.json): Installable plugin compliant with the new Claude Code plugin architecture.
3. Agent Skill (skills/asd-ste100/SKILL.md): A rich skill loaded by Claude Code, Google Antigravity, and other coding assistants.
4. Core Rule Engine & Linter (lib/ste-engine.js): Checks sentence and paragraph length, passive voice (with the Issue 9 descriptive-text exception), verb forms, multi-word nouns, unapproved words, phrasal verbs, semicolons, contractions, and Latin abbreviations. It uses lightweight heuristics (no part-of-speech tagging) and a curated word list, not the official ~900-word dictionary.
5. Standalone CLI (bin/ste.js): Lint text files or format system prompts directly from your terminal.

---

🚀 Quick Start

1. Install as a Claude Code Plugin

Requirements: Claude Code v2.1.287 or later for the mod (/asd command, tools, STE pane, system prompt rules, spinner indicator). Run claude --version to check. The skill works on any version that supports plugins.

This repository is its own plugin marketplace. One plugin install gives you both the skill and the mod (the /asd command and the STE pane). Install it from GitHub:

claude plugin marketplace add JAICHANGPARK/ASD-STE100
claude plugin install asd-ste100@asd-ste100

Or, inside a Claude Code session:

/plugin marketplace add JAICHANGPARK/ASD-STE100
/plugin install asd-ste100@asd-ste100
/reload-plugins

To try it for one session without installing (for example, from a local clone):

claude --plugin-dir /path/to/ASD-STE100

To update later, run claude plugin update asd-ste100@asd-ste100.

Older Claude Code (v2.1.286 and earlier): mods were early access. The skill loads, but the mod prints hooks module not loaded and /asd does not exist. Update Claude Code, or start it with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1. Remove that variable after you update.

To see what the mod hooks and calls before you install it, run claude plugin validate . in a clone.

2. Use the /asd Command (Mod)

Type / to see the /asd command:

/asd on             # Activate automatic STE prompt enhancement
/asd 80             # Use Karpathy's 80% Pragmatic Mode (recommended); changes only the mode
/asd strict         # Use 100% Strict ASD-STE100 Mode; changes only the mode
/asd pane           # Show the last answer as an STE document in a side pane
/asd auto [on|off]  # Rewrite each answer as an STE document in the pane (default on)
/asd session [lite] # Write an STE record of the whole session in the pane (on request only)
/asd check <text>   # Lint and score a sentence or paragraph
/asd rewrite <text> # Rewrite any text into clean STE format
/asd status         # Display active mode and status
/asd off            # Deactivate STE mode

The mod keeps Claude's answer as Claude wrote it. After each answer, the STE pane opens and shows that answer converted into an ASD-STE100 document. You do not need /asd on for the pane. Use /asd on only when you want Claude to write the answer itself in STE (the same effect as the skill). Use /asd off to go back.

/asd 80 and /asd strict change only the mode that the pane and STE mode use. Only /asd on makes the answer itself STE. /asd on, /asd 80, /asd strict, and /asd off save the state machine-wide. The saved state applies to every project and overrides the defaultMode and autoInject plugin options.

STE session record

/asd session writes a record of the whole Claude Code session as an ASD-STE100 document, in the STE pane (key s). The record has the sections Purpose, Decisions, Completed work (numbered steps in time order), and Open items, in the language of the conversation.

• /asd session asks the session's own model once, over the conversation that it already has in its prompt cache. This gives the most accurate record.
• /asd session lite sends the conversation text to a small model (haiku). It costs less. The mod also uses it when the full way fails.
• The record uses tokens, so the mod makes it only when you ask: with /asd session, or with g on the pane's session tab. It never runs by itself.

STE pane

After each answer, the STE pane opens beside the transcript. A small model (haiku) rewrites the answer as an ASD-STE100 document, and the pane shows that STE version as a page of a maintenance manual:

┌───────────────────────────────────────┬──────────────────┐
│ ASD-STE100  STE MAINTENANCE MANUAL    │ TASK 00-01-03    │
│ FLUTTER WIDGETS                       │ PAGE BLOCK 201   │
├───────────────────────────────────────┴──────────────────┤
│ MAINTENANCE PRACTICES                                    │
├───────────────────┬─────────────┬────────┬───────────────┤
│ EFFECTIVITY ALL   │ MODE 80% STE│ REV 1  │ DATE 2026-10-02│
└───────────────────┴─────────────┴────────┴───────────────┘
STE version

 1. GENERAL
    A. In Flutter, everything on the screen is a widget.
 2. PROCEDURE
    (1) Run the app in debug mode.
 ┌──────────────── WARNING ────────────────┐
 │ Do not put a large tree in one build(). │
 └─────────────────────────────────────────┘

Original → STE: avg words 19 → 7 · too long 3 → 0
┌──────────────────┬──────────────────┬────────────────────┐
│ ASD-STE100 ISSUE 9│ SCORE 97/100     │ 00-01-03  PAGE 201 │
└──────────────────┴──────────────────┴────────────────────┘

• A header block, as in an aircraft maintenance manual: the task number, the title, the page block (001 description and operation, 201 maintenance practices when the text has steps), effectivity, mode, revision and date.
• Sections numbered 1., sentences A., procedure steps (1), list items (a). One idea in each sentence.
• WARNING, CAUTION, and NOTE as boxes with the signal word in the middl