Use a Skill to generate shareable, deployable web PPT

The most time-consuming part of making a PPT was never the layout, but turning the structure in your head into concrete pages.

The Skill’s idea: solidify layout into a reusable set of instructions, so the agent outputs to the same spec every time.

What it can do

The input can be three things:

# 1. A topic
"Make a 12-page talk about indie-dev cold start"

# 2. Some notes
"Turn notes/product-positioning.md into an 8-page deck"

# 3. An existing file
"Convert deck.pptx into a web version, keeping the original structure"

The output is a single-file HTML — no build step, just double-click to open.

Why not just use PPT

	PPTX	Single-file HTML
Sharing	have to send a file	just a link
Mobile viewing	formatting often breaks	natively adaptive
Version control	binary, no diff	plain text, Git-friendly
Animation	fixed templates	write any CSS
Deployment	none	drop on any static host

The last one is decisive: it becomes a shareable URL.

Key designs

Style preview

Before generating, it shows 3–4 style options for you to pick. This step matters — words like “tech feel” or “minimal” mean completely different things in different people’s heads; see first, then choose, faster than repeated edits.

Keyboard navigation

→ / Space    next slide
←            previous slide
F            fullscreen
O            overview mode
P            export PDF

Mobile

Touch-swipe to flip pages, adapts to both landscape and portrait. The real scenario: someone taps your link in WeChat and views it on their phone.

PDF export

Directly invokes the browser’s print stylesheet — one page per screen, no back-and-forth.

Practical advice

1. Fix the page count before generating content: have it give an outline first, then produce pages after confirmation
2. Write the design spec as a file: colors, font sizes, spacing as DESIGN.md, referenced every time
3. One thing per page: if there are more than two points, split into pages
4. Finally present it yourself once: content the agent writes often “looks right but reads awkward”

Limitations

• Complex charts fall short of pro tools
• Chinese fonts depend on the system; minor cross-device differences
• Unsuitable for occasions needing fine-grained animation

Its best-fit scenario is tech talks, project intros, internal sharing — content-first, visual-second.