Command Explorer › gen: — what the agent makes › deck
gen:deck
A presentation deck — one idea per slide, made for showing.
What it does
A presentation as the deliverable: a slide deck structured for showing — one idea per slide — produced as a deck, not as a document read silently.
The registry's own words: A presentation as a deliverable: a slide deck structured for showing — one idea per slide — produced as a deck, not as a document read silently.
Fire it — usage examples
“Turn the quarterly numbers into a deck for Friday.
gen:deck”→ a slide deck is produced and delivered — slides, in order, made to be shown.
“The safety briefing, as slides.
gen:de”→ the briefing becomes a deck: one idea per slide, not a handout document — that would be
gen:doc.
Said aloud: “Lingo, generate deck — the quarterly slides.”
→ the deck is produced and delivered.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “generate deck”. Dictated directives fire deliberately, never by accident.
What the agent actually does
The agent structures the designated material as slides — one idea per slide, titles that carry the point — produces the deck in a deck format, and delivers it as an artifact. An outline in prose is a plan for a deck, disclosed as such, never the deck.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-gen-deck ↗.
When the host can't
No generation capability for deck on this host: disclose it plainly, never fake a deck, and never silently substitute a document or an outline in prose for one. A description of the deck is not the deck.
Conformance — “done when”
A slide deck is delivered as an artifact, structured for showing, or the missing capability is disclosed.
Persistence class: content-write. Execution report in the reply: 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.