Skip to content

nexu-io/open-design / plugins/community/humanize-ppt

humanize-ppt

Verified

A presentation system for agent-made PPTs — born for the talk, not just the template. It turns raw material into an AST (audience-state-transfer) outline with per-page visual-enhancement decisions (image / SVG diagram / video), hands a production brief to a downstream renderer (HTML-PPT skills or native PPTX), then runs a capped 3-round presentation checkup (演讲体检) on the rendered deck. It never renders slides itself. Use before generating PPT/HTML slides from raw material, and after rendering when the user says things like "给这份 deck 做演讲体检" or "PPT 渲染质检". If all you want is one beautiful template page with no outline and no checkup, a rendering skill alone is enough.

FileKindSize
LICENSEother219 B
SKILL.mdskill md15.6 KB
SPEC.mdmarkdown13.1 KB
adapters/guizang-bridge-notes.mdmarkdown153 B
adapters/ppt-master-bridge-notes.mdmarkdown3.3 KB
adapters/presenter-adapter-spec.mdmarkdown458 B
adapters/zara-bridge-notes.mdmarkdown175 B
contracts/asset-manifest.template.mdmarkdown75 B
contracts/ast-outline.schema.mdmarkdown211 B
contracts/deck-brief.template.mdmarkdown114 B
contracts/router-plan.schema.jsonconfig1.2 KB
contracts/run-manifest.schema.jsonconfig608 B
contracts/slide-plan.schema.jsonconfig4.4 KB
contracts/speaker-intent.template.mdmarkdown61 B
contracts/video-slots.schema.jsonconfig528 B
docs/index.mdmarkdown9.2 KB
docs/local-demo.mdmarkdown3.2 KB
examples/01-ai-tool-update/source.mdmarkdown940 B
open-design.jsonconfig1.6 KB
references/agent-teams-public-preview.mdmarkdown2.9 KB
references/beautiful-preview-first-adapter.mdmarkdown2.7 KB
references/guizang-material-qa.mdmarkdown5.2 KB
references/guizang-presenter-deploy.mdmarkdown1.9 KB
references/guizang-production-brief-orchestrator.mdmarkdown5.9 KB
references/humanize-ppt-public-writing.mdmarkdown2.5 KB
references/presenter-export-adapter.mdmarkdown2.5 KB
references/preview-outline-spec.mdmarkdown7.3 KB
references/qa-failure-modes.en.mdmarkdown18.7 KB
references/qa-failure-modes.mdmarkdown16.6 KB
references/renderer-guidance.mdmarkdown2.1 KB
references/renderer-verification.mdmarkdown2.9 KB
references/selected-template-full-deck-adapter.mdmarkdown2.5 KB
references/style-gallery-spec.mdmarkdown5.1 KB
references/workbuddy-team-packaging-and-video-materials.mdmarkdown5.2 KB
registry/renderer_registry.jsonconfig11.4 KB
scripts/humanize_ppt.pyscript349 B
scripts/humanize_ppt_v1.pyexecutablescript11.0 KB
scripts/humanize_ppt_v2.pyexecutablescript174.5 KB
scripts/humanize_ppt_v3.pyscript331 B
scripts/humanize_ppt_v4.pyscript350 B
scripts/humanize_ppt_v5.pyscript354 B
scripts/pptx_qa.pyscript14.9 KB
scripts/preview_outline_html.pyscript9.6 KB
scripts/smoke_check.pyscript11.4 KB

adapters/ppt-master-bridge-notes.md

View on GitHub
# PPT Master bridge contract

## Boundary

Humanize owns the audience-state-transfer story and writes `ppt-master-source.md` plus `ppt-master-production-prompt.md`. PPT Master owns project creation, mandatory Strategist confirmation, `design_spec.md`, `spec_lock.md`, sequential SVG authoring, notes packaging, native DrawingML export, animations, and template-fill.

Humanize never imports PPT Master's templates and never patches the exported OOXML.

The production brief resolves a real Python 3.10+ interpreter (`--ppt-master-python` overrides auto-detection) and uses `PPT_MASTER_PYTHON` for every downstream script. A binary merely named `python3` is not assumed compatible.

## Routes

| Humanize input | PPT Master route | Gate |
|---|---|---|
| Markdown/document/text plus `--renderer ppt-master` | Main SVG pipeline | PPT Master's three-stage Strategist confirmation |
| `--ppt-master-template <raw.pptx>` plus content | `workflows/template-fill-pptx.md` | Fill-plan page sequence remains `draft` until user review |
| `--style-gallery --renderer ppt-master` | PPT Master native Confirm UI | No speculative Humanize cover projects |

A raw `.pptx` template is never treated as a PPT Master SVG template directory. Creating a reusable SVG template remains PPT Master's `create-template` workflow and requires an explicit resulting directory path.

## Semantic mapping

- `slide_plan.json` page order/count/message → `ppt-master-source.md`; preserve unless the user changes it at PPT Master's confirmation gate.
- `speaker_intent.md` → `notes/total.md` in the main route or `fill_plan.json slides[].notes` in template-fill.
- `gpt-photo` → PPT Master `Acquire Via: ai` unless the asset already exists.
- `screenshot` → user/web factual asset; never synthesize UI evidence.
- `svg-html` / `html-table` → deterministic SVG or a native table/chart marker.
- Humanize video slots → explicit native-motion/static-keyframe/narrated-export fallback; PPT Master does not promise arbitrary MP4 embedding.
- `--presenter` stays native: embedded notes feed PowerPoint Presenter View; Humanize does not append an `html-ppt` renderer.
- `--export-adapter` delegates to PPT Master's native PPTX export and render manifest instead of producing Humanize's HTML/PDF package.
- In `template-fill-pptx`, native tables/charts and existing object animation XML are preserved from selected template slides. The route uses `apply --transition`; it does not accept the main SVG route's `-a` or `--native-objects` flags.
- `template-fill-pptx` v1 cannot replace images or add/retime object animations. Those requests must keep the template asset, choose another layout, become a separately approved direct-PPTX task, or be reported as `Needs-Manual`.

## Output and checkup

PPT Master keeps its project export as the source of truth and places a byte-identical copy at `outputs/ppt-master-rendered/deck.pptx`. Humanize then runs:

```bash
python3 scripts/humanize_ppt.py \
  --qa-from outputs/ppt-master-rendered/deck.pptx \
  --out <humanize-run> \
  --renderer ppt-master \
  --ppt-master-transition fade \
  --max-qa-iterations 3
```

The checkup reads OOXML and verifies package integrity, slide count, placeholder residue, non-empty editable slides, speaker notes, AST/notes drift, relationships, requested transitions, and requested native table/chart objects. Visual collision/overflow remains downstream browser review.
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