1weiho/open-slide

1weiho/open-slide — A slide framework built for agents.

Updated 2026-07-29 · Source https://github.com/1weiho/open-slide · 中文版

What is the idea?

A React slide framework aimed at coding agents: describe a deck in natural language, the agent emits components, and open-slide handles canvas, scaling, layout and export.

Who would use it, and what do they get?

Non-developer user: an office worker who has to present tomorrow. Finished thing: a PPTX in the company template, already formatted, that a colleague can open and edit.

Why would anyone bother?

Gives an agent a deck format it can actually write, with the layout and scaling problems already solved.

What is missing today?

Only geeks can use it: it is a React framework, so the deliverable stops at source code. The person who needs a deck is a teacher, a salesperson, a student — they need a file that opens in the room they are standing in, with their employer's fonts on it.

What makes this one different?

Skip the framework and sell the last mile that no framework does: brand lock-in. Take a company's existing PPTX template, learn its masters, and make every AI-generated deck come out already inside it — fonts resolved, logo placed, exportable to PPTX that a colleague can edit. One job: 'my deck already looks like our deck'. Cold start (Chinese): 小红书 and 知乎 threads on 「PPT 模板 公司规范」and 秋叶PPT's comment sections, where office workers describe re-formatting decks by hand; Cold start (English): r/powerpoint and r/consulting, search 'brand template deck reformat'.

What is the sharpest thing about it?

Agents got good at writing decks and had nowhere to render them — PowerPoint XML is hostile to generate and hand-rolled HTML slides break on scaling. 6k stars for plumbing rather than an end-user app says builders want a slide target they can emit into.

What could kill it?

This is a feature, not a company. Gamma, Canva and Microsoft are all shipping agent-authored decks with the template library and the distribution already in place, and an MIT framework is absorbed in one release. The durable asset here belongs to whoever owns the assistant, not to whoever owns the renderer.

Who pays, and for what?

The framework is the wedge, not the product. Money sits a layer up: hosted rendering, brand and template locking for teams, share links with view analytics, and PPTX/PDF export as a paid API for the many agent products that need 'export to deck' and will not build it. Gamma has already shown a deck tool can carry subscription pricing.

What is the main risk?

Closer to a feature than a company. Gamma, Canva and Microsoft are all adding agent-authored decks, and whoever owns the assistant can ship a native slide target that makes the framework redundant. MIT plumbing is easy to absorb, and the durable asset — the hosted layer — does not exist yet.

How much work is it?

about two months of work

Where does the evidence come from?

https://github.com/1weiho/open-slide

GitHubWatchingTwo months of work

Leaping AI  ·  KunAgent/Kun