What this prompt does
This prompt turns a model into a presentation designer that produces a complete, internally consistent slide deck spec rather than a pile of loose slides. You hand it a [presentation_topic], an [audience], and a target [slide_count], and it builds the system from the ground up: a slide master with [layout_count] named layout templates, an opening sequence, content rules, data-viz slides, transitions, speaker notes, and a closing sequence. Because it defines the grid and reusable layouts first, every later slide inherits a coherent structure instead of being styled ad hoc.
The variables are what keep the output disciplined. [presentation_style], [brand_colors], and [font_pairing] lock the visual identity so nothing drifts from slide to slide. [max_bullets] and [words_per_bullet] enforce a "one idea per slide" rule that fights the usual wall-of-text problem, pushing the model toward visual emphasis instead of dense lists. [chart_count] and [seconds_per_slide] shape pacing and how much data work the deck carries, while [title_treatment] and [hook_statement] decide how strong the opening lands. Because the layouts are defined before any individual slide, the whole deck reads as one designed system rather than a collection of mismatched pages.
When to use it
- Preparing a conference or meetup talk and you want a reusable layout system, not one-off slides.
- Turning a dense technical topic into something a room can follow without losing the thread.
- Standardizing decks across a team so they share a master, fonts, and color encoding.
- Building a data-heavy talk where charts need consistent annotation and progressive reveals.
- Rehearsing pacing, since the speaker notes include timing at
[seconds_per_slide]per slide. - Refreshing an existing deck that has grown inconsistent over many edits.
- Designing a strong opening sequence where the title, agenda, and hook slides carry the first impression.
Example output
You get a structured design brief: a numbered breakdown of the [layout_count] layouts with their grids and image zones, slide-by-slide direction for the opening and closing sequences, content-slide rules tied to [max_bullets] and [words_per_bullet], specs for each of the [chart_count] data visualizations (chart type, color encoding, build-up animation), section transition motifs, and speaker notes with timing. It is a blueprint to hand to a slide tool, not finished rendered slides.
Pro tips
- Make
[presentation_topic]specific and outcome-driven; a vague topic produces generic layouts. - Set
[brand_colors]as real hex values and a clear accent so the color encoding on charts is unambiguous. - Keep
[max_bullets]low (3-4) and[words_per_bullet]tight; loosening these is the fastest way back to cluttered slides. - Align
[slide_count]with[seconds_per_slide]against your actual time slot before trusting the pacing. - If charts feel flat, raise
[chart_count]modestly and ask for the progressive-reveal sequence per chart so they build during the talk. - Tune
[hook_statement]and[title_treatment]together; the opening three slides carry most of the first impression. - Reuse the section-divider motif from the transitions step to signal topic changes, so the audience always knows where they are in the deck.
