Presenton

View saved version →

---
name: presenton
description: "Create new slide presentations with Presenton and export them as editable PPTX, presentation PDF, or PNG slide images. Use when a user asks for a presentation, PowerPoint, slide deck, pitch deck, report deck, or presentation-file export, even when Presenton is not named. Do not use for generic PDFs or images unrelated to slides, text-only outlines, or editing an existing deck in place. Use a concrete design brief when provided; otherwise search Presenton designs, resolve assets, generate validated 1280x720 HTML, export the requested formats—or all three when none is specified—and return download and shareable-preview links."
---

# Create PPTX, PDF, and PNG Files with Presenton

Use Presenton's design search when a user-provided design brief is absent, then use its HTML exporter instead of constructing binary formats directly.

## Operating constraints

- Read [references/api.md](references/api.md) before making API calls and [references/html-format.md](references/html-format.md) before writing HTML.
- Use the public `https://api.presenton.ai` endpoints through the provided helper; no API key or authorization header is required.
- Create new presentations only. Do not activate for generic document PDFs, standalone images, text-only presentation outlines, or requests to edit an existing PPTX in place.
- Never upload credentials, secrets, payment details, or confidential material to the public image endpoint. If a user-provided image may contain sensitive information, ask the user to sanitize it or explicitly confirm the public upload before continuing.
- Follow the design-resolution, export, reporting, and cleanup workflow below. Print concise status updates throughout, including periodic heartbeats during long waits.
- Treat every non-empty `message` in a successful design-search, export, or preview-creation response as user-facing. Relay it verbatim in the next commentary update and include it in the final response's `Notes`.

## Creation workflow

1. Determine the requested formats, title, audience, purpose, slide count, and content. If no format is named, export PPTX, PDF, and PNG. Make reasonable content assumptions when details are absent.
2. Resolve the visual direction from the user prompt. A concrete design brief (palette, typography, layout, aesthetic, brand, imagery, or composition) is used directly and skips search. Otherwise search designs, ask the user to choose only when the options require a human preference, or select the best result automatically. Retain the searched design ID for export.
3. Resolve slide assets before writing HTML:

   - For every user-provided image that will appear in the presentation, upload the file exactly once and retain the returned HTTPS URL. Reuse that URL wherever the image appears. Never embed image bytes, base64, or any `data:` URL in the HTML.

     ```bash
     python3 scripts/presenton_artifacts.py upload-image --file <image-path>
     ```

   - For every icon concept used in the presentation, search Presenton's icon endpoint and choose a returned HTTPS URL that matches the concept and visual weight. Use `--icon-type` to match the design. Do not draw, inline, or invent substitute icons with SVG, emoji, Unicode glyphs, icon fonts, or CSS shapes.

     ```bash
     python3 scripts/presenton_artifacts.py search-icons \
       --query "revenue growth" \
       --limit 5 \
       --icon-type thin
     ```

4. Translate the resolved brief into design rules, then create a private OS temporary directory with `presenton_artifacts.py create-temp` and write the complete HTML document from scratch at `<temporary-directory>/presentation.html`. Follow [references/html-format.md](references/html-format.md) for dimensions, Tailwind, charts, fonts, assets, and PPTX compatibility. Use the retained HTTPS image and icon URLs in `<img>` elements. Do not copy a reference presentation or store HTML in the workspace.
5. Confirm the HTML reflects the resolved design, h

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 6 — file references are metadata, not package contents.