Frontend Slides

Why it's ranked here

The strongest case is its unusually complete presentation workflow. It covers design selection, generation, editing, navigation, printing, PDF export, and deployment. The opinionated fixed canvas also keeps layouts predictable, though it sacrifices responsive reflow on small screens.

What's good

Generated decks keep styling and behavior inline, avoiding frameworks and build tools at runtime. The deck component supports keyboard and touch navigation, speaker notes, viewport scaling, print layouts, reduced motion, and preserved state for hidden slides. The template library balances restrained presets with more expressive systems.

Tradeoffs

Every deck remains fixed at 16:9 and letterboxes instead of rearranging content for phones. PowerPoint extraction needs the Python PowerPoint package. PDF export requires Node.js, installs Playwright and Chromium, captures slides as images, and therefore loses animation. External font links may still require network access.

How to use it well

Use it for pitches, talks, internal presentations, reading decks, or turning existing PowerPoint content into a browser-based deliverable. Choose density early, compare the generated visual directions, then inspect overflow at desktop and phone viewports. It does not replace native PowerPoint authoring or produce editable PowerPoint files.

Observed

License

MIT License

Implementation

JavaScript deck runtime with Python and Bash helper scripts

Packaging

Claude Code plugin or manually installed coding-agent skill

Primary interface

Claude Code slash command; other local agents read the core skill instructions

Presentation output

Browser-based HTML decks with inline CSS and JavaScript

PowerPoint support

Imports PPTX text, images, and speaker notes through a Python command-line helper

Export and hosting

Shell helpers provide PDF export through Playwright and deployment through Vercel

Runtime model

Fixed 1920×1080 slide canvas scaled uniformly to the browser viewport