Introduction

beem-slide is the React slide framework that Beem Slide is built on. You say what the deck is about; the agent writes the JSX. The framework owns everything around it — the canvas and its scaling, page navigation, hot reload, present mode and export — so the agent only has to think about the page in front of it.

A page is one React component, drawn on a fixed 1920 × 1080 canvas. There is no layout system to satisfy and no markup dialect to learn: whatever you can express in JSX is a legal page.

npx --package=@beem-slide/cli beem init my-deck

Why a canvas instead of a template

On a slide, the layout carries as much of the meaning as the words do. Hand the model a template and that decision is already made for it; hand it a blank canvas and real React, and the shape of a page can follow what is on the page. What you get back is a file, so it diffs, reviews and reverts like the rest of your code.

• Skills your agent calls. /create-slide, /slide-authoring, /apply-comments and /create-theme ship with the scaffold and work from any Claude Code, Codex or Cursor session.
• Inspector in the dev server. Click an element to edit it directly, or leave a note on it — the note persists as a @slide-comment for the next /apply-comments run.
• Assets, per deck. Images, video and fonts in one panel, with brand marks searchable from the svgl catalogue.
• A presenter console. Fullscreen playback plus a second window with the next page, speaker notes and a timer.
• Export that needs no server. A self-contained HTML bundle, or a print-ready PDF.

What's next