Plan slide visuals
Proposes the visual for each slide in an outline, whether a chart type, diagram, image or none, with layout notes and data needs, so a deck shows its points rather than telling them.
Slides that only repeat the speaker's words in bullets make the audience read instead of listen. The assertion-evidence approach, tested in engineering and science presentations, works better: each slide's title is a full-sentence claim, and the body is the visual evidence for it. The right visual follows from the relationship in the content: change over time is a line, comparison across items is a sorted bar, part of a whole is a stacked bar (a pie only for two or three parts), a distribution is a histogram, a relationship between two measures is a scatter, a process is a flow, a hierarchy is a tree, a sequence of events is a timeline. Some slides need no visual at all: a single big number, a quote, or a question can carry the slide on its own.
Plan the visuals for this deck.
Only if [BRAND_CONSTRAINTS] is given:
- If the outline has no clear message per slide, or the slides with data have no numbers, say which slides are affected; plan the rest and mark those slides as needing input rather than guessing.
- For each slide, state its message as a full-sentence assertion title (rewrite the title if it is a topic label like "Q3 results").
- Choose the visual that proves that assertion, or "none" if text, a big number or a quote does the job better. Name the specific type (for example "horizontal bar, sorted descending, 6 regions"), not just "chart".
- Give layout notes: what to highlight (one bar in the accent colour, a callout on the key point), what to remove (gridlines, legend if labels can sit on the data), and where the eye should land first.
- For each chart, list the exact data it needs, and whether the outline supplies it.
- Set a handful of rules for the whole deck so visuals stay consistent.
- One message per visual. If a slide is trying to show two things, propose splitting it.
- Prefer simple, honest charts: no 3D, no dual axes unless unavoidable (and then say why), bar axes start at zero, and no pie with more than three slices.
- Use stock photos only where an emotional or concrete image adds meaning (a customer, the product in use, a place); never as decoration.
- Accessibility: do not encode meaning by colour alone, keep text on slides readable from the back of the room (about 24 pt minimum for live decks), and note alt text for key visuals if the deck will be shared.
- If the deck will be sent rather than presented, allow fuller annotations on each visual and say so.
- Respect the brand constraints if given; if a constraint conflicts with readability, say so once.
- Use only numbers in the outline. Never invent data to fill a chart; mark gaps as
[NEEDED: …].
Visual plan
A table: # | Assertion title | Visual | Layout notes.
Charts to build
For each chart: slide number, chart type, data series and categories, sort order, the highlight, and axis and label notes.
Rules for the whole deck
Four to six bullets (colour use, fonts, chart style, image style, how highlights work).
Missing data
Bullets of [NEEDED: …] items, or "None".
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Presentations
- level
- Beginner
- made for
- Anyone, personal use, People manager, Founder / business owner, Consultant / freelancer
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install plan-slide-visuals --target claude-codenpx skills add hermes-hq/hodios-dist --skill plan-slide-visuals -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of PresentationsOutline a presentation
Outlines a story-driven presentation with assertion-style slide titles, using SCQA or the pyramid principle, sized to the time slot and aimed at a stated goal for a specific audience.
outline-presentationCritique a slide deck
Critiques a slide deck for storyline, one idea per slide, text density and visual clarity, and returns ranked slide-level fixes with rewritten titles. Use before presenting or sending a deck.
critique-slide-deckTurn a document into slides
Turns a document or report into a slide outline with one message per slide, action titles that tell the story, suggested visuals from the document's own data, and an appendix plan.
turn-document-into-slidesWrite speaker notes
Writes natural, speakable notes for each slide with a time budget, the one point to stress and a transition to the next slide, and checks the total fits the time slot.
write-speaker-notesPresentation track
Takes a presentation from audience and goal to storyline, slide content, speaker notes and a rehearsal with likely questions, pausing for approval between steps.
presentation-trackWrite a lightning talk
Writes a five-minute lightning talk or a timed PechaKucha or Ignite script around one idea, with slide-by-slide words, visuals and a closing line, for meetups and internal demos.
write-lightning-talk