← ClaudeAtlas

asd-ste100listed

Explain or rewrite technical text in clear, STE-inspired English. Use for ASD-STE100, Simplified Technical English, '80% STE', 'strict STE', 'Karpathy-style', or a plain explanation of code, a diff, or a system. Supports diagrams, interactive HTML, and explainer videos when requested. Not for creative or marketing copy.
prithivrajmu/asd-ste100 · ★ 18 · AI & Automation · score 82
Install: claude install-skill prithivrajmu/asd-ste100
# ASD-STE100 for readable output Make the reader's work easier. Use **80% STE** by default: short sentences and plain words, with normal technical vocabulary. This is a writing aid, not a compliance checker. Do not assume that model knowledge proves compliance with ASD-STE100. ## Choose the task and level 1. Identify the task: **rewrite**, **explain**, or **summarize**. - Rewrite: preserve all facts, conditions, exceptions, and scope limits. - Explain: use the supplied evidence. Check relevant code or documentation when tools are available. Label assumptions and unknowns. - Summarize: select the important facts. Keep the conditions and uncertainty that affect their meaning. 2. Use the user's requested language, length, and output format. 3. Use 80% STE unless the user asks for "strict", "100%", or "full STE". 4. For strict STE, read [the strict-mode notes](references/strict.md). Apply the supplied standard and dictionary when available. Do not claim verified compliance without a check against them. 5. If essential source material is missing, ask one focused question. Otherwise, proceed without a questionnaire. For a procedure, use short numbered steps at either level. Safety-related text needs qualified review, not an automatic claim of strict compliance. For other languages, use the same clarity principles. Do not claim ASD-STE100 compliance for a non-English result. ## Preserve meaning first These rules take priority over sentence length and style: - **Keep