Presentation Generator

Create a clear presentation specification and, when the local toolkit is available, render it as editable PPTX and standalone HTML. The generator runs locally and does not require an AI API key.

Use when

• The user asks for an investor pitch, business decision deck, educational slides, or a data presentation.
• The user provides an outline, brief, or source material that can be structured into slides.
• A reproducible local PPTX/HTML export is preferred over an image-only deck.

Inputs

Ask for or infer from context: audience, objective, approximate slide count, tone/theme, required facts, source materials, and desired call to action. Do not fabricate missing data. If a key choice materially affects the result, ask one focused question before drafting.

Workflow

1. Extract the audience, purpose, central takeaway, supplied facts, and unresolved questions.
2. Propose a story arc. Keep one idea per slide; move nuance to notes.
3. Use ../../prompts/master-presentation-prompt.md or the matching deck prompt to draft JSON.
4. Save the JSON in a user-approved working directory. Do not overwrite existing files.

5. From the project root, run:

   node src/cli.js validate --input <spec.json>
   node src/cli.js qa --input <spec.json>
   node src/cli.js generate --input <spec.json> --out <output-directory>

6. Review every heuristic warning. Open the HTML and PPTX, check clipping, fonts, chart labels/data, slide flow, and all factual claims.
7. Tell the user which outputs were produced and disclose any limitations.

Specification and outputs

The schema is documented in docs/usage.md and illustrated in examples/. Version 1 accepts title, bullets, metric, process, chart, comparison, quote, and closing slide types. The first slide is a title slide and the last is a closing slide.

• PPTX: editable native text/shapes and native bar charts; speaker notes are supported.
• HTML: standalone file with keyboard navigation, notes, and print CSS.
• PDF: not generated by this toolkit version.

Validation and limits

The validator catches malformed specifications and invalid chart arrays. QA checks contrast, text length, and approximate density; it does not render slides or prove that text fits. Human review is required for factual accuracy, source quality, layout, font availability, and visual clarity. Do not claim that a model-generated source has been verified merely because it parses.

Example

For “Explain how heat pumps work to homeowners,” create an educational deck with a plain-language opening, a four-step process, one comparison slide, a short recap, and notes for technical caveats. Use no numerical efficiency claim unless the user supplies a reliable source.