tldr · diff
git:20261005.c2522fa to git:20261006.4c6da76
1 added, 1 removed. Audit A to A.
---
name: tldr
description: Use when the user types /tldr to get a plain-simple-English summary, written in ASD-STE100, of the most recent response, aiming for under 30 words and never over 55.
---
# TLDR
Produce a dead-simple recap of your most recent substantive response.
## Rules
- 1. **Write it as a Plain simple English block in ASD-STE100 (Simplified Technical English)** per the Response Style rules in CLAUDE.md/AGENTS.md: one short paragraph. Aim for under 30 words. If 30 words would cut critical information (a caveat, a decision, or a required action), use more, up to a hard maximum of 55 words. No headers, no preamble like "Here's the TLDR" — just the summary itself.
+ 1. **Write it as a Plain simple English block in ASD-STE100 (Simplified Technical English)** per the Response Style rules in CLAUDE.md/AGENTS.md. Aim for under 30 words. If 30 words would cut critical information (a caveat, a decision, or a required action), use more, up to a hard maximum of 55 words. No headers.
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.