tldr git:20260807.c1f1b83A

Immutable. This exact content never changes and is served at /api/v1/blob/5dd5e9c03e59b1d1.

---
name: tldr
description: Use when the user types /tldr to get a plain-simple-English summary of the most recent response in under 55 words.
---

# TLDR

Produce a dead-simple recap of your most recent substantive response.

## Rules

1. **Use ASD-STE100 (Simplified Technical English) under 55 words.** Going over is a failure. Count them. Active voice; one idea per sentence; ≤20 words per procedural sentence and ≤25 per descriptive sentence. No litotes or litotes-adjacent hedging — state each claim directly.
2. **Audience: a slightly above-average 18-year-old.** Not gifted, not an expert — just a bit above average. No insider jargon, no acronyms without spelling out, no domain assumptions. Everyday STE wording only.
3. **One sentence per line, separated by a blank line.** Put two line breaks after every sentence so each stands alone. No headers, no bullet lists, no preamble like "Here's the TLDR" — just the summary itself.
4. **Summarize the prior answer**, not the original question. If there is no prior substantive response in the conversation, say so in one line and ask what to summarize.
5. **Keep it accurate.** Simplify, never fabricate. If the real answer has a critical caveat, keep it.

## What this means

Explain the core idea as you would to a slightly above-average 18-year-old: concrete, conversational, analogy if it helps. Strip mechanism detail down to the point that matters.