/prettymsg — a pretty, skimmable overview, in the chat

Take whatever was just figured out / discussed / produced in this chat and re-render it as a pretty, bullet-style overview the user can read at a glance — output directly in the chat reply. Nothing is written to a file, copied to a clipboard, or posted anywhere. This is the lightest of the overview skills: it's just a beautifully-formatted answer.

Markdown renders in the Claude Code terminal. **bold**, ##/### headers, - bullets, and plain emoji all display. So "you can't format in chat" is a myth — lean into it.

Who it's for (this sets the tone)

The reader was in this chat — so it's a recap for them, not an explainer for an outsider (that's /discordmsg). Assume they know the context; the job is to make the current state / answer instantly scannable: what's the headline, what matters, what's next. No journey, no dead-ends, no re-teaching.

The format (the rules of the output)

• Lead with a one-line TL;DR. Bold it. One sentence, the headline. They should get the gist from that line alone.
• Then 2–5 bold mini-headers, each with tight bullets under it. Overview first, detail only if it earns its place.
• A few emojis — tasteful, as section anchors / status flags, not confetti. One per header at most, plus the odd inline status flag. Useful set: ✅ done · 🐛 bug · 🔧 fix · ⚠️ caveat · 🚀 shipped · 📊 numbers · 🎯 next · ⛔ blocker · 💸 cost · ❓ unknown. Plain unicode only (exotic ones can render as tofu boxes in some terminals).
• Bullets are short. Fragment > sentence. One idea per bullet. Bold the key term at the front of a bullet when it helps the eye land (**Login:** blocked on …).
• End with a 🎯 Next line (1–3 bullets) when there's a decision or action pending — that's usually what the reader is scanning for.
• Use `code` / file:line for anything they'd click or grep. Keep real numbers exact.

Keep it TIGHT — that's the win

Length is the cost, not emojis (a plain emoji is negligible; use them freely within taste). So the discipline is brevity: a crisp ~8–16 bullet overview, never a wall. If the underlying thing is big, summarize and offer "want the full detail / /prettyhtml it?" — don't dump it. A pretty overview that doesn't fit on one screen has failed at being an overview.

Faithful, not inflated

Summarize only what's actually in the chat. Don't invent status, don't upgrade "unvalidated" to "done", don't bury a ⛔ blocker to make it look tidier. Pretty ≠ rosy. If state is messy, the overview says so — clearly and prettily.

How it differs from its siblings (don't duplicate them)

• /prettymsg → in-chat pretty overview. No file, no clipboard, no send. ← this one.
• /discordmsg → paste-ready Discord message for an outsider, copied to clipboard (+ .txt).
• /discordembed → richer Discord embed-style writeup (bigger budget, bold headers), copied.
• /prettyhtml → writes a polished HTML file and opens it in your browser.

If the user actually wants it shared/saved, point them at the right sibling — don't silently do it here.

Execution steps

1. Read $ARGUMENTS → pick the subject (the named focus, or the latest substantive result/state in the chat) and honor any tone/length the args request ("just next steps", "super short").
2. Compose: TL;DR line → bold mini-headers with tight bullets → 🎯 Next. Emojis as anchors, bullets short, numbers exact, file:line where useful.
3. Output it directly in the chat reply — no tool calls, no file, no clipboard, no posting.
4. Keep it tight; if there's important overflow, offer /prettyhtml or /discordmsg rather than inlining a wall.