| name | tappy-pdf-export |
| description | Create visually strong, theme-bound PDF reports from Tappy documents using source-accurate SVG pages. |
Tappy PDF Export Skill
Use this skill when creating a PDF report from a Tappy document.
Goal
Create a print-safe, screen-readable PDF that feels purpose-built for the document. The PDF may be a memo, operating report, board brief, appendix, visual explainer, or executive one-pager depending on context.
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
- Identify the report job and expected reader.
- Decide page count, section flow, and information density yourself.
- Preserve source-backed facts exactly. Never invent or alter numbers, dates, names, or labels.
- Use the supplied theme tokens as the visual system. You may vary layout, scale, tints, and rhythm inside that system.
- Design each page as a complete SVG surface sized
1200x1553.
- Favor readability: clear headings, good margins, readable tables, concise callouts, and appendix pages for detail.
- Avoid generic AI artifacts: decorative blobs, emoji, fake labels, repeated card grids, filler slogans, and cramped text.
- Return only Tappy surface envelopes. Do not include commentary, markdown, JavaScript, or external assets.
Output Contract
Return one or more surfaces:
---TAPPY_SURFACE: Short page title---
<svg xmlns="http://www.w3.org/2000/svg" width="1200" height="1553" viewBox="0 0 1200 1553">...</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.
- Keep text readable on screen and in print.
- Draw charts and tables directly from supplied values.
- Use subtle citations where source-backed data appears.
Quality Bar
The report should look intentionally designed for its content. It can be editorial, analytical, dashboard-like, appendix-heavy, or memo-like as appropriate. Do not force a fixed template.
