Core Principles
PPT production is a structured pipeline, where each stage has clear inputs, outputs, and acceptance criteria.
| Stage | Lead | Responsibility |
|---|---|---|
| Planning | Author | Content planning, page type selection, evidence source organization |
| Style | Author + Review | Style setting, core page CSS baseline |
| Authoring | Author | Batch HTML slide production |
| Review | Layout Review + Brand Review | Layout/information review + brand/aesthetic review |
| Export | Author | Export validation, format check |
| Delivery | Author | Preview delivery, file archiving |
Opening Parameters (Must Be Declared)
Before production, the following parameters must be locked in first as the standard basis for all subsequent stages:
| Parameter | Description | Example |
|---|---|---|
| Output Format | Single complete file or paginated | HTML single file / PPTX single file / paginated HTML |
| Page Type (archetype) | Determines density, font size matrix, and information organization method | Strategic overview / data insights / solution comparison / reporting page |
| Brand | Visual DNA of the benchmark company | Huawei / Apple / Alibaba / Generic |
| Audience | Who will view this PPT | CTO / investors / technical team / clients |
| Scenario | Where the PPT will be used | Annual meeting report / client proposal / internal sharing / product launch |
| Primary Viewing Mode | Affects font size/density/whitespace standards | presentation (large-screen projection) / document (PDF reading) |
No opening parameters = no standards for either starting work or review. These 6 items must be locked before starting.
Scenario Routing
| Trigger | Scenario | Lead | Detailed Documentation |
|---|---|---|---|
| User says "make a PPT" | P: Content Planning | Author | refs/ppt-slide-authoring.md (planning section) |
| Outline confirmed | S: Style Setting | Author does + Review reviews | refs/ppt-style-tile.md |
| Style confirmed | A: Batch Slide Production | Author | refs/ppt-slide-authoring.md |
| Slides completed | R: Visual Review | Layout Review (D1) + Brand Review (D2) | refs/ppt-visual-review.md |
| Review passed | E: Export/Assembly | Author | refs/ppt-delivery.md |
| Export validation passed | D: Delivery | Author | refs/ppt-delivery.md |
| Need competitor comparison | B: Benchmark Comparison | Author | refs/ppt-visual-review.md |
| User dissatisfied / 2 consecutive rounds with P1>0 | Reset: Start Over | — | Return to P stage to replan |
Scenario Details
P: Content Planning
- Lock first:
archetype / 品牌 / 受众 / 场景 / 主观看模式 - At minimum produce:
本次 PPT 的一句话目标 + 证据源列表 + 页面结构草图 - If it is not made clear "what conclusion should people reach after viewing this page" → do not enter A stage
S: Style framing
- First make 1-2 core pages (cover + most complex content page)
- Extract CSS variables (brand color/font size/spacing/border radius)
- After Review confirms the style, Author mass-produces according to CSS variables
A: Slide mass production
- Select a template by archetype
- Density-driven: at least 3 filling methods per page
- After completion, self-check screenshots + density data
R: Visual review
See refs/ppt-visual-review.md for details
- D1 Layout Review: layout/information review (P1-level issues)
- D2 Brand Review: aesthetic/brand review (P2-level issues)
- The 6-piece input package is required before submitting for review
E: Export verification
- Check: native text / native chart / native table / screenshot fallback / repair dialog
- Any issue → do not proceed to D
D: Delivery
See refs/ppt-delivery.md for details
- Must open the preview with browser-preview
- Deliverables: HTML preview + screenshots + PPTX/PDF (if needed)
- Can only end after user confirmation
Visual review 6-piece set
Every time a visual review is initiated, it must include:
- Brand + audience brief — "Huawei style, audience CTO, explain the moat clearly in 1 page"
- Page type (archetype) + primary viewing mode — prevent the reviewer from changing the page type
- Purpose of this page — state in one sentence what this page should achieve
- Screenshot/preview URL — rendered result
- HTML/CSS source code — used to locate layout bugs
- Density data — whitespace%、element count、overflow
Without the 6-piece set = subjective commentary; with the 6-piece set = P1/P2-level review.
Review dimensions quick reference
D1: layout/information review (Layout Review)
| Level | Dimension | Judgment |
|---|---|---|
| P1 | Layout bug | Real CSS/HTML error |
| P1 | Information failure | Key points not explained clearly / wrong hierarchy / audience cannot understand |
| P1 | Density imbalance | Should be dense but is not / should be sparse but is not |
D2: brand/aesthetic review (Brand Review)
| Level | Dimension | Judgment |
|---|---|---|
| P2 | Brand drift | Does not look like the target company's design language |
| P2 | Visual consistency | Font size/cards/borders/icon language are not unified |
Five aesthetic dimensions: color system · typography · spatial grid · visual elements · density balance
Density filling methods
See refs/ppt-density-playbook.md for details
Deliverables checklist
According to the initial parameters'output format, generate the corresponding single file:
| Format | Description | File features |
|---|---|---|
| HTML single file | Complete PPT, all slides embedded in one HTML | *.html, can be opened directly in a browser, supports page turning |
| PPTX single file | Complete PPT, all slides embedded in one PPTX | *.pptx, can be opened directly with PowerPoint/WPS |
| Paged HTML | One file per slide | 01.html, 02.html... (only used in the review phase) |
Default output: single HTML file. Generate a PPTX version when the user explicitly requests .pptx.
Common Mistakes
| Error | Consequence | Fix |
|---|---|---|
| No opening parameters declared | No standard for kickoff and review | Lock 6 parameters before kickoff (including output format) |
| Review only after all 20 pages are finished | Rework costs explode | Phase S: first do 1-2 core pages to set the tone |
| Say "no problem" yourself without screenshots | Layout bugs missed | Self-check must take screenshots and review them before handing off |
| Review gives only screenshots, no HTML | Can only say "this looks weird" | Must include the 6-piece set |
| Generate multiple HTML files instead of a single file | The user needs to open them one by one | Phase E must assemble into a single reveal.js file |
| PPTX font sizes not converted | Text too small to read | CSS_px × 0.75 = PPTX_pt |
| Skip the Export Gate | Unexportable after export/garble | Independently verify export quality |
Brand template
A brand template is a preset of visual specifications for a specific company; after selecting a brand, the corresponding specifications are applied automatically:
| Brand | Template path | Features |
|---|---|---|
| Huawei | refs/huawei/template.md | Red/black/gray, right-angle system, high density |
| Apple | (To be expanded) | Minimalist, lots of white space |
| Alibaba | (To be expanded) | Orange/tech blue, Dashboard |
| General | — | Configurable, adjusted according to brief |
Usage: After selecting a brand in the opening parameters → when setting the style tone in Phase S, use the CSS variables of the corresponding template
Reference documents
| Document | Content |
|---|---|
| refs/ppt-style-tile.md | Detailed style-setting process |
| refs/ppt-slide-authoring.md | HTML production specifications |
| refs/ppt-visual-review.md | Visual review Gate |
| refs/ppt-delivery.md | Delivery process |
| refs/ppt-density-playbook.md | Density filling manual |
| refs/huawei/template.md | Huawei brand template |
| refs/huawei/huawei-brand.md | Huawei visual specifications |
| refs/huawei/huawei-archetypes.md | Huawei page-type templates |
| refs/huawei/huawei-density-rules.md | Huawei density standards |