html-slideslisted

# Multi-Style HTML Presentations Turn a one-sentence request into a readable, editable, single-file HTML deck: 1920×1080, inline CSS, and at most 120 lines of runtime JavaScript. Keep code and guidance separate. `assets/core/` contains base CSS, runtime, and layout skeletons; `assets/<style>/` contains variables, style-specific patterns, and assets; Markdown under `references/` defines rules and points to those files. Core code uses variables only; styles supply values. Built-in styles are `generic` (default), `huawei`, and `apple`; add a style through `references/styles/_template.md` plus `assets/<style>/`. Activate only when the user names `$html-slides` or the skill. Do not invent data or citations, install dependencies, or export PPTX unless requested. When exporting, state whether the result is image-based or natively editable. ## Principles 1. Confirm the topic and outline before writing pages; read `references/process.md`. 2. Every content-page title is an arguable sentence naming the key technology or method; the titles alone form the argument chain. 3. Always include cover, agenda, and final thank-you pages; rebuild the agenda from the current outline. 4. Fix every `section` at 1920×1080 with `overflow:hidden`; deliver only when `?debug` shows no red overflow frames. 5. Use at least 21px for teaching prose and 18px for presentation/self-read cards; tables, axes, and diagram labels may use 15px. 6. Change visual family within every three consecutive p