tappy-pptx-export

name	tappy-pptx-export
description	Create visually strong, theme-bound PowerPoint slide decks from Tappy documents using source-accurate SVG surfaces.

Tappy PPTX Export Skill

Use this skill when creating a PowerPoint deck from a Tappy document.

Goal

Create a polished, context-specific deck. Do not convert the document block-by-block. Build a clear presentation story using the data, prose, and source context provided.

Inputs

• Document title and blocks.
• Source/citation labels when available.
• Selected Tappy theme tokens: background, panel, surface, border, text, muted, primary, success, warning, danger, chart palette, and font hints.
• Optional audience, persona, saved instructions, and recent chat context.

Workflow

1. Identify the deck job: board update, operating review, memo summary, command center, briefing, appendix, or another purpose implied by the document.
2. Decide the slide count and narrative order yourself.
3. Use source-backed facts exactly as provided. Never invent or silently alter numbers, dates, names, or labels.
4. Use the supplied theme tokens as the brand system. You may create tints, contrast, scale, and layout variation inside that system.
5. Design each slide as a complete SVG surface sized 1600x900.
6. Use visual hierarchy: strong titles, clear sections, useful whitespace, real charts/tables from source values, and concise implications.
7. Avoid generic AI artifacts: repeated card grids, decorative blobs, emoji, filler slogans, fake chart points, and crowded tiny text.
8. If there is too much material, add detail or appendix slides instead of cramming.
9. Return only Tappy surface envelopes. Do not include commentary, markdown, JavaScript, or external assets.

Output Contract

Return one or more surfaces:

---TAPPY_SURFACE: Short slide title---
<svg xmlns="http://www.w3.org/2000/svg" width="1600" height="900" viewBox="0 0 1600 900">...</svg>
---END_TAPPY_SURFACE---

SVG Rules

• Use inline SVG only.
• Do not use <script>, <foreignObject>, remote images, remote fonts, external CSS, or event handlers.
• Use text, rect, line, path, circle, polyline, polygon, and similar standard SVG elements.
• Use plain readable text from the document. Do not use placeholder glyph bars, lorem ipsum, icon fonts, emoji, or decorative Unicode.
• Make all text readable at slide size.
• Draw charts and tables directly from the supplied values.
• Use subtle citation text where source-backed data appears.

Quality Bar

The deck should feel designed for the specific document and audience. Slides may be sparse, dense, editorial, dashboard-like, or appendix-heavy depending on the content. Do not force a house template.