Skip to content

JunfengRan/PPTWork / ppt

Build PPT / PowerPoint / 演示文稿 / slide decks end-to-end via a .pptwork/<deck>/ filesystem contract. Use when the user wants to plan, author, screenshot, or export a slide deck. Provides Node scripts for deck CRUD, headless screenshot, and editable PPTX export. Covers clarification, story planning, single-page authoring (via the ppt-html-authoring skill), visual QC, and export troubleshooting.

FileKindSize
SKILL.mdskill md13.2 KB
assets/claude-warm/_preview/bento-asymmetric/slide.htmlother3.6 KB
assets/claude-warm/_preview/bento-asymmetric/thumbnail.pngbinary65.2 KB
assets/claude-warm/_preview/cover-editorial/slide.htmlother2.0 KB
assets/claude-warm/_preview/cover-editorial/thumbnail.pngbinary43.0 KB
assets/claude-warm/_preview/flow-timeline/slide.htmlother3.1 KB
assets/claude-warm/_preview/flow-timeline/thumbnail.pngbinary30.3 KB
assets/claude-warm/_preview/quote-highlight/slide.htmlother1.7 KB
assets/claude-warm/_preview/quote-highlight/thumbnail.pngbinary33.6 KB
assets/claude-warm/_preview/section-divider/slide.htmlother1.8 KB
assets/claude-warm/_preview/section-divider/thumbnail.pngbinary35.6 KB
assets/claude-warm/html/bento-asymmetric.htmlother3.6 KB
assets/claude-warm/html/cover-editorial.htmlother2.0 KB
assets/claude-warm/html/flow-timeline.htmlother3.1 KB
assets/claude-warm/html/quote-highlight.htmlother1.7 KB
assets/claude-warm/html/section-divider.htmlother1.8 KB
assets/claude-warm/index.jsonconfig1.8 KB
assets/corporate-light/_preview/agenda-grid/slide.htmlother3.2 KB
assets/corporate-light/_preview/agenda-grid/thumbnail.pngbinary53.5 KB
assets/corporate-light/_preview/closing-cta/slide.htmlother2.2 KB
assets/corporate-light/_preview/closing-cta/thumbnail.pngbinary91.8 KB
assets/corporate-light/_preview/cover-hero/slide.htmlother2.4 KB
assets/corporate-light/_preview/cover-hero/thumbnail.pngbinary198.9 KB
assets/corporate-light/_preview/kpi-stat-row/slide.htmlother2.4 KB
assets/corporate-light/_preview/kpi-stat-row/thumbnail.pngbinary127.6 KB
assets/corporate-light/_preview/two-column-insight/slide.htmlother3.6 KB
assets/corporate-light/_preview/two-column-insight/thumbnail.pngbinary42.5 KB
assets/corporate-light/html/agenda-grid.htmlother3.2 KB
assets/corporate-light/html/closing-cta.htmlother2.2 KB
assets/corporate-light/html/cover-hero.htmlother2.4 KB
assets/corporate-light/html/kpi-stat-row.htmlother2.4 KB
assets/corporate-light/html/two-column-insight.htmlother3.6 KB
assets/corporate-light/index.jsonconfig2.0 KB
package.jsonmanifest484 B
references/disk-layout.mdmarkdown2.2 KB
references/editable-html-rules.mdmarkdown2.0 KB
references/export-troubleshooting.mdmarkdown5.8 KB
references/material-digest.mdmarkdown2.0 KB
references/research.mdmarkdown2.7 KB
references/story-planning.mdmarkdown5.2 KB
references/visual-qc.mdmarkdown4.4 KB
scripts/deck.mjsscript9.5 KB
scripts/export.mjsscript8.0 KB
scripts/import-reference.mjsscript1.2 KB
scripts/lib/deck.mjsscript2.1 KB
scripts/lib/find-browser.mjsscript1.7 KB
scripts/lib/render.mjsscript12.6 KB
scripts/screenshot.mjsscript2.5 KB
test/smoke.mjsscript10.1 KB

references/story-planning.md

View on GitHub
# Phase: story planning

Turn user intent + digested material → an executable per-page plan. Output is
either `.pptwork/<deck>/outline.md` (deck >= 5 pages) or a structured summary
back into context (short deck).

**This phase does not write `design.md`, `slide.html`, or `deck.json`.** Story
planning means: every page gets a one-liner that says "what we're saying,
which template slot, where the content comes from".

## Preconditions

The clarification checklist must already be filled in (audience, length,
style/brand, must-have sections, output language, whether to verify
externally). If anything is missing, return to the user with a follow-up
question instead of making it up.

## Workflow

1. **Confirm clarification is complete.** If something key is missing, raise
   it before planning, do not paper it over.
2. **Read summaries, not raw material.** If the source is too long, run the
   `material-digest` phase first.
3. **Pick layouts by id, do NOT read the raw HTML.** That's the
   `ppt-html-authoring` skill's job. You only read these fields from each
   bucket's `index.json` under `assets/<bucket>/`:
   - `id`
   - `pageType`
   - `description`
   - `authoringHints`

   If no bucket is configured for this project, skip the assetId lookup —
   describe each page's layout in plain language ("two-column comparison
   with a chart on the left, three bullets on the right") and let the
   authoring phase compose slide.html from scratch.
4. **Layout diversity hard rules:**
   - No two adjacent pages share the same `assetId`.
   - Whole deck covers at least 4~5 distinct `pageType`s.
   - Don't dump every data page onto a single KPI-style layout. Trends →
     chart layout, phases → flow / timeline, comparisons → two-column.
5. **Each page must record:** `pageType`, `assetId`, **source mapping**
   (which user material section / which research query / `TBD`),
   **transition sentence** (how the previous page's conclusion leads into
   this one), and bullet points of key content.
6. **Output split:**
   - >= 5 pages → write `.pptwork/<deck>/outline.md` once (no incremental
     patching).
   - < 5 pages → return a structured summary directly; skip the file.
7. **External data:** if a page depends on time-sensitive facts, run the
   `research` phase, then cite the conclusion in the source field as
   `see research.md §<timestamp>`. If it's too uncertain to research now,
   mark `应联网: query=...` in the source so the main loop knows to follow
   up.

## outline.md format (strict)

```markdown
# <Deck topic> — Outline

> Audience: ...; Length: ...; Style: ...; Verified externally: yes/no

## Layout diversity self-check

- Covered pageType: cover / agenda / two-column-insight / chart-demo / flow-timeline / closing
- No two adjacent pages share an assetId ✓
- Data pages use charts (not pure text) ✓

## P1 | <conclusion-style title>
- pageType: cover
- assetId: cover-hero        # or omit entirely if no template bucket
- source: user material §1 (digest item 2)
- transition: N/A (opening)
- content:
  - <bullet 1>
  - <bullet 2>

## P2 | <conclusion-style title>
- pageType: agenda
- assetId: agenda-columns
- source: user material §2
- transition: from P1's ... lead to ...
- content:
  - <bullet 1>
  - <bullet 2>

...
```

## Title style (the single biggest lever against "filler" pages)

| ❌ Noun-form | ✅ Conclusion-form |
|---|---|
| "AI Agent market" | "AI Agent market crosses USD 100B in 3 years" |
| "Digital transformation" | "Digital transformation lifts ops efficiency 40%" |
| "Edge computing" | "Pushing inference to the edge cuts latency to 15ms" |

Both the page-frontmatter `title` and the outline `## PN |` lines follow this
rule.

## Common story arcs (compressed; pick by topic shape)

- **Conclusion → support**: P1 cover → P2 conclusion → P3~P5 three lines of
  support (data / case / architecture) → P6 closing call to action. Best for
  briefings, pitches, product launches.
- **Problem → cause → solution → outcome**: P1 cover → P2 status quo →
  P3 root cause → P4 solution → P5 outcome KPIs → P6 next step. Best for
  engineering proposals, post-mortems.
- **Timeline / phased evolution**: P1 cover → P2 three-phase agenda →
  P3~P5 phase 1~3 → P6 main-thread closing. Best for roadmaps,
  transformation cases, market evolution.
- **Value prop → capability map**: P1 cover → P2 customer pain → P3 value
  proposition → P4 capability map → P5~P6 cases → P7 delivery / commercial.
  Best for sales decks.

## When to push back to the user

Surface these directly in your response — do **not** improvise an answer:

- User gave a topic but no material, and the topic is data-heavy
  ("AI Agent market analysis").
- User said "use this PPTX as reference" but the digest shows it covers far
  more page types than this deck needs.
- User asked for "20-page deep report" but the material can only support 8
  pages.
- User asked for a specific brand style but must-have sections include
  clearly off-brand terminology / content.

## Forbidden in this phase

- Writing `design.md` / `slide.html` directly.
- Copying example copy from template HTML into the outline (placeholder bleed).
- Stopping after 1~2 pages — story planning must be one-shot complete.
- Calling web tools directly (use the `research` phase).
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall