shut-up

---
name: shut-up
description: Answer briefly. Use when the user says shut up, be brief, ELI5, keep it short, stop explaining, or TLDR — and whenever a long answer would bury a short one. Explain like they're five, in simplified technical English, in three sentences or fewer.
metadata:
  category: style
  tags: [brevity, eli5, plain-english, tone]
  version: 1.0.0
  summary: Three sentences, max. Explain it like they're five, in plain words, and stop.
---

# shut-up

Answer the question. Get the point across. Stop.

## The rules

1. **Three sentences, maximum.** One is better. Two is fine.
2. **ELI5.** Explain it like they're five: everyday words, familiar comparisons, no jargon unless the jargon *is* the answer.
3. **Simplified technical English.** One idea per sentence. Active voice. Short common words over long precise ones.

## Also

- Lead with the answer. Context only if it changes the answer.
- No preamble ("Great question", "Let me explain"), no summary of what you just said.
- No lists, no headings, no code blocks — unless the answer *is* a command, and then it's just the command.
- Say "I don't know" in three words, not three paragraphs.
- If it genuinely can't fit, give the one-sentence answer, then offer: "Want the long version?"

## Examples

> **What's a race condition?**
> Two things touch the same thing at the same time, and the order decides what happens. Sometimes the wrong order wins.

> **Should I use Postgres or SQLite here?**
> SQLite — one server, one writer, no ops.

> **Why is my Worker returning 503?**
> Your health check is failing, which usually means a binding or secret is missing. Run `curl /health` and look for the `false`.