Choose theme
AI Resources
open-slide
open-slide turns React components into presentation slides, with a development preview where you can edit elements or leave comments for a coding agent.
The framework handles the slide canvas, navigation and presentation runtime. Your agent writes the deck source; you review the result and choose how to present or export it. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
A deck made of source files
Each page is a React component on a fixed 1920 by 1080 canvas. Deck files and their assets live in a workspace you can revise through code.
Why it stands out
Visual changes reach the source
The development inspector supports direct element edits and comments attached to the relevant code. Agent skills connect those comments to a later editing pass.
Availability
CLI scaffold and local runtime
The CLI creates a workspace; the core package runs its preview and build. Official docs and a demo show the workflow. HTML, PDF and PowerPoint exports serve different handoffs.
Why it matters
What makes it useful
For a product update or technical talk, you can ask a coding agent to draft the deck and then review the actual slides. Small text and layout adjustments can be made in the inspector; changes that need explanation can be left as comments for the agent. The deck remains React source.
What to know
Where it fits
open-slide supplies the presentation framework, not the model or coding agent. Its CLI scaffolds the workspace, while the core package owns preview, navigation and builds. The documentation shows decks as arrays of page components, with local assets alongside them; this fits a team willing to maintain presentation source rather than only a presentation-app file.
Notable points
What stands out
Inspector comments are stored as @slide-comment markers next to the selected element in source. The /apply-comments documentation describes an agent pass that reads those markers, edits the surrounding code and removes resolved markers. It says comments the agent cannot resolve are left in place and reported as skipped, so a review note is not the same as a completed change.
Before using
What to review
For the current v2 toolchain, the migration guide specifies Node 20.19+ or 22.12+. It also warns that an old workspace's separate Vite dependency can conflict with the core package, and describes removing that entry and reinstalling.
Choose the handoff format by installed version. The v2 changelog lists editable PPTX text boxes, shapes and images; the export guide still describes image-based PPTX and says native editable export is unavailable. Those official pages disagree. Inspect the version and output before promising an editable deck.
Check what goes into a public build. The export guide says it includes decks under slides/, their imported assets and the runtime. Hiding the deck browser or toolbar changes the displayed interface; review the actual files you intend to publish.
For a proxied development server, the config docs explain allowing the workspace domain. They warn that accepting every host with allowedHosts: true disables Vite's DNS-rebinding protection and reserve that setting for a trusted network.
The repository declares MIT. Review the original project and separate terms for your coding-agent provider, fonts, images and other imported assets.
Reader fit
Who may find it relevant
Developers or technical presenters who want to revise a deck as React source and are comfortable reviewing an agent's changes.
Teams that want visual feedback to point at specific slide elements instead of explaining every change in a separate chat.
Readers needing only a finished presentation-app file should compare the actual export with that need. Source authoring and exported editability are separate choices.
Editorial note
Why LifeHubber lists it
When rehearsing a talk, the presenter-mode documentation shows speaker notes stored in an array alongside the page array, with matching positions. A page without notes uses undefined in that position, so later notes stay aligned with their slides. Presenter view opens in a second window with the current slide, next slide, notes and timer. This connects the deck source to the speaking script without putting that script on the audience-facing slide.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
More in Productivity
Keep browsing this category
Explore more productivity tools.
Penpot
penpot/penpot
An open-source collaborative design platform with an official MCP server that lets AI agents inspect and modify Penpot files, components, tokens, styles, layouts, and assets through hosted or local connection paths.
DeskcommCRM
melgarafael/DeskcommCRM
A self-hosted sales and support CRM centered on WhatsApp, with AI agents, lead pipelines, human handoff, follow-up rules, and a choice of AI providers. It uses a VPS and Supabase; AI features need a provider key.
Archify
tt-a1i/archify
An agent skill for making interactive diagrams from a description or codebase, with editable JSON source, structure and layout checks, and portable HTML that others can explore.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
