presentation-generator

Overview

This skill generates Hebrew presentations with correct right-to-left (RTL) layout. It covers two practical output paths: Marp markdown for developers who want version-controlled, text-based slides, and python-pptx for anyone who needs a .pptx file compatible with PowerPoint and Google Slides.

Hebrew presentations have unique technical requirements that generic presentation tools ignore. Bullet alignment defaults to LTR. Punctuation jumps to the wrong end of a line. Number formatting in Israeli business contexts follows conventions that differ from what US-centric templates assume. This skill addresses all of those problems with working code and explicit configuration rather than workarounds.

Instructions

Follow these steps to produce a correct RTL Hebrew deck:

1. Choose the output path: Marp markdown for version-controlled, text-based slides, or python-pptx for a .pptx file that opens cleanly in PowerPoint and Google Slides. For Israeli business recipients, prefer python-pptx (XML-level RTL is reliable); use Marp PDF for read-only sharing.
2. Pick the font: Heebo for business and tech decks, David Libre for formal reports, Assistant for education, Rubik for bold startup decks. Load via @import in Marp CSS, or ensure the font is installed on the machine running python-pptx.
3. Generate the content: write the slide text in Hebrew. Structure pitch decks per the Israeli VC ordering below; use NIS formatting and the Israeli fiscal calendar.
4. Apply the RTL patches: for Marp, set direction: rtl; text-align: right in the theme CSS. For python-pptx, call set_paragraph_rtl() on every paragraph that holds Hebrew text, plus the table-cell and inline-English helpers in references/pptx-rtl-patches.md. For charts, speaker notes, and the slide master, see the dedicated sections below.
5. Export: run marp presentation.md --pptx (or --pdf/--html), or prs.save(output_path) in python-pptx.
6. Verify: open the file and confirm bullets align right, punctuation sits at the correct end of each line, the currency symbol is placed correctly, and tables read right-to-left. Inspect the XML if a paragraph still renders LTR (each <a:pPr> must carry the rtl="1" attribute).

When to Use