AI Agent Hub
Back to skills
Editable Browser HTML Slide Generator icon

Editable Browser HTML Slide Generator

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md and install @user_26736ada/frontend-slides-editable-breakingwall.

About this skill

What it solves

Building HTML presentations usually forces a tradeoff: zero-dependency single-file decks are easy to ship but hard to keep adjusting, while editor-heavy templates can drift into generic dashboard aesthetics. frontend-slides-editable puts both in one layer: it generates standalone HTML decks that still run in the browser with a built-in editing surface.

How the skill works

  • Generate first, edit later: it emits single-file HTML/CSS/JS without npm, build tools, or React. The runtime covers object movement, Ctrl+click multi-selection, alignment snapping, font controls, undo/redo, Ctrl+S persistence, and export HTML.
  • Discover before generating: for new decks or decks reconstructed from .pptx / .pdf, the skill requires purpose, length, content, style direction, editing scope, image intent, and mobile target. When the brief is incomplete, it asks only for missing items instead of guessing slide count or preset.
  • Converge with previews: STYLE_PRESETS is not only color and type. It includes layout, signature elements, and differences between title slides and content slides; those rules should be implemented in HTML/CSS rather than reusing one generic “title + subtitle + rounded card” geometry.
  • Keep template boundaries: ported presets use data-edit-slot for text, image, metric, and table-cell content, while grids, decorative layers, textures, and spacing usually stay locked. User-added objects enter .slide-edit-layer and can be moved, resized, or multi-selected.

Where it fits

Use it for zero-dependency, directly shareable HTML decks or presentations that need post-generation manual adjustment. If a read-only deck is enough, the notes suggest the original frontend-slides instead. This is not a general-purpose web editor: it does not promise that every template node is draggable, and it is not intended for projects that require component-level interaction, backend services, or a build pipeline. Every slide must still respect 100vh / 100dvh and overflow: hidden, with no intra-slide scrolling.

Use Cases

  • A frontend engineer turns launch notes into a single-file HTML deck, then drags objects, adjusts fonts, and exports it in the browser.
  • A marketer extracts titles and bullets from a `.pptx`, then generates an editable HTML deck instead of rebuilding the PPT from scratch.
  • A designer compares `STYLE_PRESETS` previews, picks Swiss Modern, and delivers a single-file deck.
  • A teacher prepares lecture slides where every page fits `100vh`, reorders thumbnails in the sidebar, and saves drafts with `Ctrl+S`.

Best For

  • Frontend engineers delivering single-file HTML decks who want to avoid a React build and keep browser-side tweaks.
  • Marketers or operators converting PPT/PDF decks into web presentations without returning to Office files.
  • Instructors preparing course or internal talks who need fixed viewport slides, drag reordering, and `Ctrl+S` saves.
  • Design engineers maintaining `STYLE_PRESETS` who must preserve layout and signature elements, not just recolor them.