Slide Agent, Animation-Rich HTML Deck Generator

Scheduling

Goal

Generate distinctive, anti-"AI slop" HTML presentation decks authored at a fixed 1920×1080 stage, validate geometry deterministically via the oma slide CLI, and deliver self-contained bundles exportable to PDF, PNG, and PPTX.

Intent signature

• User asks to create a slide deck, presentation, keynote, or series of slides.
• User provides a topic, outline, .pptx to import, or existing deck to enhance.
• User mentions slide, deck, pptx, keynote, 슬라이드, 발표자료, プレゼン, 幻灯片, 演示文稿.
• User mentions Canva, canva export, canva import, 캔바, キャンバ.
• User needs an editable PowerPoint (편집 가능한 PPT), wants an existing PPTX filled or edited with its design kept, a document (PDF/DOCX/XLSX/URL) turned into a PPTX deck, a reusable brand/style/layout/deck template, or a narrated PPTX/MP4 → native-pptx route.
• Another skill needs a visual output artifact (e.g., a research result delivered as a deck).

When to use

• Creating a new presentation from a topic or outline
• Enhancing or reformatting an existing deck
• Generating per-slide HTML with animations and design-doctrine aesthetics
• Exporting a deck to PDF, PNG, or image-backed PPTX after generation
• Applying a named style preset or bold template to a deck
• Exporting a generated deck to Canva as a presentation
• Importing a Canva design as input for enhancement
• Producing a natively editable PPTX through the upstream ppt-master skill (resources/native-pptx.md)

When NOT to use

• Plain document creation (no slides needed) → use oma-backend or direct output
• Image generation alone → use oma-image directly
• Brand/design-system definition → defer to oma-design
• Deterministic CLI ops (validate/bundle/export) without generation → call oma slide CLI directly
• Long-form scrolling code-change explainer document → use oma-explanation (deck is a fixed 1920×1080 stage)