/bro
Usage
/bro
No arguments. Fire it immediately after a reply that didn't land.
Description
D just typed /bro. Your last message didn't land — too dense, too jargon-heavy, or
too formal. Re-explain your own most recent message in a much simpler way, like
you're explaining it to a smart friend over a beer.
This is the counterweight to concise. Concise optimises for fewest words; /bro
optimises for impossible-to-misunderstand, and will happily spend more words to get
there.
Expected Output
Claude: The wrapper promotes versions/<N> into current/claude when the .version
stamp differs, so TCC's csreq revalidates against a stable path.
D: /bro
Claude: ok so — macOS remembers "this exact file is allowed to read your
Documents". Every update made a new file, so it forgot every time and
asked again.
Now there's one file that never moves: ~/.local/share/claude/current/claude.
Updates just swap what's inside it. Same file, so macOS stays happy.
Behavior
- Re-explain, don't re-answer. Never answer a new question, never add new
information, never use tools. You are only re-expressing what you already said.
- Simpler, not necessarily shorter. If the idea needs space to be clear, take
the space. The goal is "impossible to misunderstand", not "fewer words". Cut
preamble, hedging, and consultant-speak — keep whatever length real clarity needs.
- Facts survive verbatim. Every path, command, filename, number, URL, name, and
decision stays EXACTLY as it was. Simplify the explanation around the facts, never
the facts themselves.
- Light bro flavor. Casual and direct ("basically…", "the point is…", "ok so…").
A touch of personality is welcome — don't turn it into a meme.
- Same language. If the original message was in PT-BR, the simpler version is in
PT-BR too ("mano", "basicamente"…). English stays English.
- Flatten structure. Drop headers and ceremony. Tables become plain sentences.
Keep a short list only if the original genuinely had multiple parts.
- Edge case: if there's no previous assistant message in this conversation, just
say there's nothing to simplify yet, bro.
Notes
- Ported from luchasarie/bro-skill (MIT).
Rules 1–7 are upstream's, kept intact; only the file structure was adapted to this
repo's skill format.
- Rule 2 is deliberately at odds with the
concise output style. That is the point —
/bro is an on-demand escape hatch, not a default voice. Don't "fix" it by making
it terse.
- Related: [[eli5]] output style aims at the same problem from the other end — it
keeps every reply simple, where
/bro simplifies one reply on request.
1---2name: bro3description: Re-explain the previous assistant message in a much simpler way — for when the reply made you go "bro what". Use when D types /bro, or says "in plain English", "say that again simpler", "explain that like a normal person", "I didn't follow that".4license: MIT5metadata:6 category: communication7---89# /bro1011## Usage1213```bash14/bro15```1617No arguments. Fire it immediately after a reply that didn't land.1819## Description2021D just typed `/bro`. Your last message didn't land — too dense, too jargon-heavy, or22too formal. Re-explain **your own most recent message** in a much simpler way, like23you're explaining it to a smart friend over a beer.2425This is the counterweight to `concise`. Concise optimises for fewest words; `/bro`26optimises for impossible-to-misunderstand, and will happily spend more words to get27there.2829## Expected Output3031```text32Claude: The wrapper promotes versions/<N> into current/claude when the .version33 stamp differs, so TCC's csreq revalidates against a stable path.34D: /bro35Claude: ok so — macOS remembers "this exact file is allowed to read your36 Documents". Every update made a new file, so it forgot every time and37 asked again.3839 Now there's one file that never moves: ~/.local/share/claude/current/claude.40 Updates just swap what's inside it. Same file, so macOS stays happy.41```4243## Behavior44451. **Re-explain, don't re-answer.** Never answer a new question, never add new46 information, never use tools. You are only re-expressing what you already said.472. **Simpler, not necessarily shorter.** If the idea needs space to be clear, take48 the space. The goal is "impossible to misunderstand", not "fewer words". Cut49 preamble, hedging, and consultant-speak — keep whatever length real clarity needs.503. **Facts survive verbatim.** Every path, command, filename, number, URL, name, and51 decision stays EXACTLY as it was. Simplify the explanation around the facts, never52 the facts themselves.534. **Light bro flavor.** Casual and direct ("basically…", "the point is…", "ok so…").54 A touch of personality is welcome — don't turn it into a meme.555. **Same language.** If the original message was in PT-BR, the simpler version is in56 PT-BR too ("mano", "basicamente"…). English stays English.576. **Flatten structure.** Drop headers and ceremony. Tables become plain sentences.58 Keep a short list only if the original genuinely had multiple parts.597. **Edge case:** if there's no previous assistant message in this conversation, just60 say there's nothing to simplify yet, bro.6162## Notes6364- Ported from [luchasarie/bro-skill](https://github.com/luchasarie/bro-skill) (MIT).65 Rules 1–7 are upstream's, kept intact; only the file structure was adapted to this66 repo's skill format.67- Rule 2 is deliberately at odds with the `concise` output style. That is the point —68 `/bro` is an on-demand escape hatch, not a default voice. Don't "fix" it by making69 it terse.70- Related: [[eli5]] output style aims at the same problem from the other end — it71 keeps every reply simple, where `/bro` simplifies one reply on request.
damilola-elegbede-org