---
name: 高维学堂PPT
description: Use this skill whenever the user asks to create, rewrite, audit, or repair 高维学堂 courseware, 导师PPT, 学员手册, 开课课件, or any "高维PPT协作指南" compliant deck, especially when they say "高维学堂PPT", "给高维上课做课件", "导师PPT", "高维手册", "字少图清", "投影和纸质手册都要用", or "用HTML实现PPT". This skill creates a self-contained HTML slide deck, not a .pptx, unless the user explicitly asks to edit an actual PowerPoint file.
version: 1.0.0
updated: 2026-06-29
source: https://wx.gaowei.com/Customer/Forward?id=21730072-a5ab-4476-83c1-90c6b3b6fd46
---

# 高维学堂 HTML PPT

Use this skill to turn a course outline, manuscript, article, workshop plan, model, tool, case, or rough notes into a 高维学堂-compliant HTML courseware deck. The output should behave like PPT for teaching, while printing cleanly as a learner handout.

The central standard is "一份材料，双重场景":

- Live projection: concise visual guide, teacher explains, learners can read from the middle/back rows.
- Printed handout: clean, rigorous, durable reference material learners can annotate and revisit.

## Default Output

Create these outputs unless the user asks for something narrower:

- A self-contained HTML deck saved under the current workspace `outputs/`.
- A local browser preview opened after generation.
- A short QA note with slide count and checks performed.
- Optional supplemental notes file when source material is too dense for slides.

Do not create a `.pptx` by default. If the user provides or asks to edit a real `.pptx`, coordinate with the PPTX skill for file extraction/editing, then return to this skill for the HTML deck standard.

## Read First

Before building or auditing a 高维学堂 deck, read:

- `references/gaowei_requirements.md` for the institution's source requirements.

When starting a new deck from scratch, use:

- `templates/gaowei_deck_starter.html` as the implementation shell.

## Workflow

1. **Clarify the teaching job**
   - Identify course name, teacher/display author, date, audience, teaching length, delivery scene, and whether the deck will be printed.
   - If details are missing, proceed with reasonable placeholders instead of blocking. The filename should follow `课程名称_姓名_日期` when known.
   - Remove private names, group names, internal IDs, chat handles, and unrelated promotional QR codes unless the user explicitly says they are public.

2. **Split slide content from handout depth**
   - Keep the slide as the visual outline: one core point per page, title plus structure.
   - Move long data tables, extended cases, legal/detail notes, and source-heavy explanations into speaker notes, an appendix, or a separate supplemental notes file.
   - Add a "工具/模型速查" or "核心心法速查" page for methods learners will revisit.

3. **Build the deck spine**
   - Cover: course name, teacher, date, one sentence promise.
   - Learning map: what learners will be able to recognize, decide, and apply.
   - Chapter pages: 3-6 sections, each with a visible logic path.
   - Teaching slides: one conclusion-led title, one visual structure, short prompts for discussion.
   - Practice/check pages when useful; fill-in pages must stay within 10 slides and answers go into the final appendix.
   - Closing: three-sentence summary plus next action or review path.

4. **Implement as HTML**
   - Use a 16:9 slide stage, keyboard navigation, previous/next controls, progress indicator, fullscreen support, and hash-based slide URLs.
   - Inline the CSS and JS so the file can be opened directly.
   - Add print CSS that reveals every slide as a separate handout page.
   - Keep the deck mobile-readable, but optimize primarily for projection and printing.
   - Avoid external network dependencies for core viewing. Use Alibaba PuHuiTi only when locally bundled or safely available; otherwise use system sans-serif fallbacks.

5. **Apply 高维 visual rules**
   - Background: pure white or light gray no darker than about 10% gray.
   - Text: black or deep gray. Use 高维蓝 `#00A0EB` or deep blue `#0000FF` only as a restrained accent.
   - Body text on slides should feel equivalent to at least 22pt PPT text; use roughly `30px` or larger in HTML.
   - Main titles should feel equivalent to at least 30pt PPT text; use roughly `40px` or larger.
   - Chart labels should feel equivalent to at least 16pt PPT text; use roughly `22px` or larger.
   - Prefer clear black table grid lines over colored fills for print.
   - Use high-resolution images, thickened diagram lines, and no shadows/glow/transparency that will print as gray smudges.

6. **Design each slide for 3-second understanding**
   - Title states the insight, not just the topic.
   - Use at most three major bullets or visual anchors.
   - Convert dense paragraphs into matrices, flow strips, contrast tables, ladders, scorecards, or checklists.
   - Split a crowded page instead of shrinking text.
   - For complex charts, include the three title elements: figure/table code, core insight, and data source/year.

7. **QA before delivery**
   - Open the HTML deck locally and navigate every slide.
   - Check for text overflow, clipped charts, tiny labels, dense tables, low contrast, blank pages, and private/internal wording.
   - Verify print mode shows all slides and keeps the content within page boundaries.
   - If browser automation is available, capture screenshots or a contact sheet for visual review.
   - Fix issues before reporting completion.

## Layout Rules

- Use one main idea per slide.
- Use text as teaching cues, not a transcript.
- Put detailed explanations in speaker notes, appendix, or supplement.
- Keep table cells to 3-5 short lines, no more than 5 columns when possible, and enough row height for print.
- Keep at least 1cm equivalent breathing space around dense tables/figures in print.
- Every data chart should show the year range and source.
- Sensitive proprietary pages may carry a quiet corner note: "内部资料，请勿外传".

## Avoid

- Text-wall slides.
- Small gray footnotes that disappear in print.
- Low-contrast yellow/green text or fills.
- Decorative blobs, purple AI gradients, dark theme decks, and generic marketing hero pages.
- Shadows, glow, blur, transparency, and fine hairlines in diagrams.
- Hard advertising, unrelated QR codes, or brand clutter.
- In-page explanations of how to use the deck UI unless the user requests a training artifact.

## Delivery Note Template

```markdown
已完成：<HTML文件路径>
预览：已打开本地预览 / 未能自动打开，文件可直接打开
页数：<N>页
高维自检：投影字号、手册打印、表格/图表、数据源、版权/隐私、导航与打印模式已检查
补充材料：<无 / 文件路径>
```
