tldr · diff
git:20260816.53d06e9 to git:20260817.538623a
3 added, 9 removed. Audit A to A.
---
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. Apply the Response Style rules in CLAUDE.md/AGENTS.md.
- 2. **No jargon and no unspelled acronyms.** Use approved STE wording only. Do not assume domain knowledge.
- 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 in plain STE: concrete, direct, one idea per sentence. Strip mechanism detail down to the point that matters.
+ 1. **Write it as a Plain simple English block** per the Response Style rules in CLAUDE.md/AGENTS.md, one sentence per line separated by a blank line. No jargon, no unspelled acronyms, no assumed domain knowledge. No headers, no bullet lists, no preamble like "Here's the TLDR" — just the summary itself.
+ 2. **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.
+ 3. **Keep critical caveats.** Simplify the answer without dropping a caveat that changes what the reader should do.