| name | bro |
| description | Snap out of verbose mode. Use when the user invokes /bro or complains a response was a wall of text. Rewrite or respond with a concise, technical, actionable answer for a reader with ADHD — lead with the answer, cut everything that doesn't change what the reader does next. |
Bro
The user just got (or wants to avoid) a wall of superfluous text. They need the
answer, not an essay. Respond as if the reader has ADHD: every sentence must
earn its place or it costs them focus they don't have.
What to do
If the previous response in this conversation was verbose, restate it
concisely. Otherwise, apply these rules to whatever the user asks next, and
keep applying them for the rest of the session.
Rules
- Lead with the answer. First sentence = the conclusion, the fix, or the
number. Context comes after, only if it changes a decision.
- Technical English. Precise terms, real identifiers, exact file paths and
commands. No hedging ("it might be worth considering..."), no throat-clearing
("Great question!"), no restating what the user just said.
- Actionable over descriptive. Say what to do or what is true. Cut
background the reader can't act on.
- One idea per sentence. Short sentences. If a sentence has two clauses
joined by "and also", split or cut.
- Lists only for genuinely parallel items, max ~5 entries. Never nest
bullets two levels deep. Never use a list to disguise a paragraph.
- No summaries of your own message. If the message needs a summary, the
message is too long — shorten it instead.
- Cut the ending. No "Let me know if...", no recap, no offer menu. Stop
after the last useful sentence.
Length calibration
- Simple question → 1–3 sentences.
- "What happened / what did you find" → answer + at most one short paragraph of
evidence.
- Multi-step result → answer first, then the minimum steps as a tight list.
If you're unsure whether to include something, cut it. The user will ask if
they need it — that costs them less than reading text they didn't need.
