In the re: domain
re:voice — Reply with a voice note (spoken audio).re:show — Answer visually instead of in prose.re:recap — Catch me up: state, decisions, what's open.re:steps — A numbered procedure, one action per step.re:list — Present the material as an enumerated set — items on their own lines, each one complete; the form for a set, where steps is the form for a sequence.re:cite — Show this reply's sources, inline with its claims.What it does
The reply's substance is a visual the agent picks to fit the content — a chart for numbers, a diagram for how something works, a map for places.
The registry's own words: Answer visually instead of in prose; the agent picks the medium that fits — diagram (how it works), chart (numbers), map (places), generated image (seeing a thing). Minimal labeling text may accompany; an essay with a picture attached is a failed re:show.
Fire it — usage examples
“How do the two providers compare on price?
re:show”→ a chart of the two prices, with at most a one-line takeaway under it.
Quote a text explanation of a process and reply
re:sh→ the explanation returns as a diagram.
Said aloud: “Lingo, reply show — the two quotes, side by side.”
→ the comparison arrives as a chart, not a paragraph.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “reply show”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent selects the medium that fits the content and renders it — the visual carries the answer. An essay with a picture attached is a failed re:show; numbers inside the visual are the real numbers from the answer, never decoration.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-re-show ↗.
When the host can't
No fitting visual possible: say so plainly and give the closest visual form (for example a structured table). Never silently fall back to prose.
Conformance — “done when”
The reply's substance is the visual (or the disclosed closest structured form), with at most minimal labeling text.
Persistence class: none. Execution report in the reply: not required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.