PPT Generation Skill

The pain point of PPT is "it takes an hour to make one, but you redo it for every new project." Flowix's solution is to use an Agent to directly generate presentable Markdown outlines or HTML slides — write it, then present it.

Prerequisite — You already know how to write a minimal-structure prompt. See Prompts.

1. Two output formats

Format	Best for	Output file
Markdown outline	1-3 page lightweight shares, internal syncs, ad-hoc meetings	A `.md` snippet
HTML slides	8-15 page external talks, tech shares, with styling and animation	A single `.html` file, open in a browser

The inputs for both formats are basically the same; only the "output format" section of the prompt differs. Pick one first, then write the prompt.

2. Markdown outline version

Create a Prompts/ppt-outline.md:

# Prompt: Generate PPT outline

## Role
You are a senior presentation coach preparing a talk on .

## Input
Topic: 
Duration:  minutes
Audience: 
Core takeaway: 

## Output format
A Markdown outline with the following structure:

# 
> One-line subtitle (≤ 20 chars)

## Agenda
- Part 1: ...
- Part 2: ...

## Slide N: Subtitle
- 3 bullets, ≤ 20 chars each
- One-sentence conclusion

(Blank line between slides)

Requirements:
- Total slides = ceil(minutes / 2.5)
- First slide = agenda / cover, last slide = summary or CTA
- Don't use "Thank you" / "Q&A" as filler; write "Next steps" on the last slide if needed

How to invoke: In any Flowix document, press Cmd/Ctrl + L and type /ppt-outline. Flowix injects this entire prompt, then the Agent writes the outline back directly.

3. HTML slides version

If you need styling, have the Agent output a single HTML file.

Prompts/ppt-html.md:

# Prompt: Generate presentable HTML slides

## Input
Topic: 
Duration:  minutes
Audience: 
Core takeaway: 

## Output
**A complete HTML snippet** (from `<!DOCTYPE html>` to `</html>`). Requirements:

- Single file, all CSS / JS inlined, **no external resources**
- Use CSS `display:none` / `.active` class for paging, navigate with ← → Space
- Progress bar at the top: `Slide N / M`
- Each slide layout: small title in the top-left + bullets in the middle + logo placeholder at the bottom
- Font sizes: title 64px, bullets 36px
- Color scheme: dark background with white text (#0E1116 / #FFFFFF) + brand accent color (via CSS variables)
- Total slides = ceil(minutes / 2)

After the Agent outputs, copy it to ~/Notes/talks/2026-07-talk.html and double-click to present in full screen in the browser (F).

Don't let the Agent freestyle the styling — pin colors, font sizes, and grid in the prompt to avoid inconsistent output every time.

4. Streaming iteration

The first version won't be perfect — the worst thing you can do is start over:

Review finding	How to write the follow-up
Slide 5 bullets too dense	"Split slide 5 into two slides, ≤ 3 bullets each"
Want to add a chart	"Replace slide 7 with an HTML/CSS bar chart, 3 data points"
Color scheme too dark	"All slides use a light background with dark text (#FAFAF7 / #222), accent color `#C25B4F`"
Over time	"Cut total slides from 12 to 8, merge the agenda"

Append each round of changes to the document (the conversation flow); Flowix keeps the context.

5. Rules of thumb

Outline before design — Get the Markdown skeleton first, confirm the content, then switch to the HTML version
≤ 3 bullets per slide — More than 3 and nobody remembers
The first and last slides matter most — The cover answers "why am I here", the last slide answers "what you can take away"; polish these two repeatedly
Pin the title to the topic — Don't write "Product share", write "3 ways Flowix uses AI to take over your documents"