Turn real source material into editable, reviewable presentation deliverables — locally, with clear sources and checks before delivery. Already have a PowerPoint? Check it with PPTLint.
中文 · Live Workspace · Proof Packs · v6.1 Release Notes
Already have a PowerPoint to improve or check? Ultimate PPT Master repairs the editable deck; PPTLint independently checks the finished PPTX on your computer. In the published nine-slide Proof Loop, 103 reported issues were resolved with 0 new high-confidence problems. Open the complete before/after evidence →
Most AI presentation tools optimize for the first preview. Ultimate PPT Master optimizes for the moment the deck is opened in a real meeting, revised in PowerPoint, challenged on its sources, and handed to someone else.
It is not another free-form slide editor. It is a local presentation Agent and quality operating system for formal reports, consulting work, training, finance/government material, branded communication, and high-stakes handoff.
v6 replaces the old settings-first console with a task-first workspace:
- Input — describe the job, add files/URLs/existing PPTX, choose the delivery use.
- Storyboard — the Agent asks no more than three material questions, then shows slide jobs, evidence and gaps.
- Design & Generate — compare three real visual directions, generate a fast structural draft, then refine progressively.
- Refine & Deliver — work by stable
slideId, regenerate one slide, review quality findings, and finish in PowerPoint.
Bridge, providers, scripts, DeckIR and JSON contracts still exist, but they now live in professional and diagnostic paths instead of blocking the first screen. The previous four-step console remains available for one compatibility cycle at ?classic=1.
| Typical AI PPT failure | Ultimate PPT Master response |
|---|---|
| An extremely thin prompt becomes a confident but generic deck | The Best-Effect Brief Enhancer creates an Auto-expanded brief and exposes assumptions before production. |
| A polished preview is actually a flat image | Keeps PowerPoint text, shapes, tables, charts, notes and other supported objects editable. |
| Sources disappear during generation | Preserves source maps, evidence bindings, asset provenance and confidence boundaries. |
| One small edit regenerates the whole deck | Uses stable slideId, slide-level revision requests, checkpoints and reusable asset hashes. |
| Every page becomes “big title + three cards” | Uses visual direction packs, page roles, page recipes and repeated-layout audits. |
| Missing image/model keys break the workflow | Degrades to explicit Needs-Manual prompts instead of silently faking completion. |
| The final file looks right but cannot survive handoff | Runs rendered review, native-object checks and export gates tied to the current artifact digest. |
| You need | Recommended route | Deliverable |
|---|---|---|
| A formal report, consulting proposal, training deck, finance/government material, or anything others must revise | Editable PowerPoint | .pptx with editable content, notes and quality evidence |
| A keynote, public talk, demo day, editorial story or browser-first showcase | Magazine Web Deck | responsive HTML with Style A Editorial Fixed Rhythm or Style B Swiss International |
| A browser experience plus a formal handoff | Dual delivery | separate Web and PPTX projects sharing the same source and planning record |
PowerPoint remains the primary final editing environment. Ultimate PPT Master handles the work around it: source intake, narrative planning, visual direction, asset policy, generation, QA, review and recovery.
Requirements: Python 3.10+, Node.js 18+, npm. Rust is only needed for native desktop packaging.
git clone https://github.com/kdnsna/ultimate-ppt-master-skill.git
cd ultimate-ppt-master-skill
npm run setup
npm run doctor
npm run bridgeThen open the v6 Web Workspace. The hosted UI talks only to the local Bridge on 127.0.0.1; source files and generated handoff projects remain on your machine.
For an Agent-first workflow, install or link the Skill and ask naturally:
Use $ultimate-ppt-master to turn this quarterly review and the attached workbook
into a 10-slide editable PPTX for the management committee. Lead with the decision,
keep every number traceable, and use our previous deck only as a style reference.
You do not need a special prompt. v6 infers low-risk settings and asks only when audience, evidence, brand/IP permission or delivery expectations materially change the result.
- Editable PPTX route with safe Office typography, speaker notes and native-object regression checks.
- Style A editorial/e-ink and Style B Swiss Web Deck routes with structural validators.
- Existing-PPTX reference learning for masters, layout rhythm, theme fonts/colors, placeholders and common page roles.
- Six complete visual directions covering cover, body, data, chart, image, section and closing behavior.
- Three structural variants per slide before expensive refinement.
- Single-slide regeneration, checkpoint recovery, attachment hashing and incremental progress events.
- Local-first source handling, provider-secret isolation and explicit official/IP asset rules.
- Web and Desktop surfaces sharing the same
DeckSessionstages and design tokens.
The root-level DESIGN.md locks atmosphere, semantic color, typography roles, component grammar, layout, depth, anti-patterns, responsive behavior, and the fields every Agent writes before generation. Six visual directions are executable contracts—not recolored themes—and each carries its own type personality, composition model, surface rhythm, image behavior, shape grammar, and prompt. The system was informed by awesome-design-md and adopts the strongest production disciplines from the latest guizang-ppt-skill and baoyu-design: title sequence first, registered recipes, one visual protagonist per slide, planned light/dark/image rhythm, standard image geometry, projection-scale type, bottom safe space, and rendered browser review. These are workflow principles, not copied templates or brand identities.
Start with the public presentation gallery: three complete nine-slide decks now demonstrate three materially different systems—Precision Evidence, Cinematic Product, and Editorial Intelligence—above the stable Proof Packs. GPT-5.6 and Claude Fable 5 use official release material; the requested “Grok 4.6” was corrected to the latest verified official release, Grok 4.5, as of 10 July 2026. Proof Pack scores remain self-assessed by Design Doctor, not external benchmarks.
| Case | Inspectable output |
|---|---|
| GPT-5.6 · Three Orbits | Open 9-slide deck |
| Grok 4.5 · Engineering Efficiency | Open 9-slide deck |
| Claude Fable 5 · Long Horizon | Open 9-slide deck |
| Executive Business Review | Open stable proof |
| Consulting Proposal | Open stable proof |
| Product Pitch | Open stable proof |
| Tech Trend Web Deck | Open stable proof |
v6 includes a real HTTP Bridge for preparation and orchestration:
| Endpoint | Role |
|---|---|
POST /handoff |
stage the brief, attachments, storyboard and production contracts |
GET /events |
stream read-only progress events with SSE |
POST /slides/regenerate |
write a stable-slide revision request |
GET /health, GET /providers |
inspect runtime and provider readiness without returning secrets |
POST /agent/launch |
return or explicitly launch an allowlisted local Agent command |
The current Bridge is intentionally not a public, authenticated, standalone POST /generate service. It binds to localhost for safety. A server deployment still needs either:
- an Agent runner such as Codex/Claude Code/OpenClaw that executes the Skill; or
- your own orchestrator that calls the repository scripts, persists
DeckSession, runs quality gates and publishes artifacts.
Do not expose the current Bridge directly to the internet. See Agent Connect Bridge for the exact boundary and deployment patterns.
The workflow is inspectable and resumable because important decisions are written to files:
| Artifact | What it proves |
|---|---|
project-brief.json |
user request, inferred brief, route, assumptions and expectationFit |
storyboard.json |
stable slide IDs, page roles, variants, evidence references and editability targets |
asset_plan.json |
every image slot, source policy and status; generated rows carry current_generation_evidence |
source-map.json |
traceable source claims used by the deck |
spec_lock.md |
compact execution contract for visual consistency |
quality-report.json |
rendered-review findings, delivery readiness and known blockers |
pipeline-state.json |
digest proving export is tied to the latest passing checks |
npm run test:node
npm run test:worker
npm run build:web
npm run build:desktop
npm run audit:v6-workspace
npm run audit:web-console
npm run audit:docs
npm run audit:image-contracts
npm run audit:featured-decksFormal PPTX projects also support:
python3 scripts/audit_formal_delivery.py <project>
python3 scripts/audit_design_completion.py <project>
python3 scripts/audit_visual_recipes.py <project>
python3 scripts/audit_pptx_native_objects.py <final.pptx> --expect text,shape
uvx pptlint check <final.pptx> --profile ai-generated # Proof: https://kdnsna.github.io/pptlint/Legacy decklint remains available through PPTLint v0.4; new integrations should use pptlint.
Web / Desktop workspace
│
▼
DeckSession ── intake → outline → generating → review → delivered
│
▼
Local Bridge ── source extraction · SSE · handoff · slide revisions · cache
│
▼
Agent / orchestrator ── storyboard · asset plan · generation · audits
│
├── Editable PPTX
└── Magazine Web Deck
The legacy contracts (project-brief.json, storyboard.json, asset_plan.json, quality-report.json and Bridge handoff) remain compatible in v6.
- The Bridge binds to localhost and never returns provider secrets to the browser.
- Private source material stays local unless the user explicitly approves upload.
- Official logos, QR codes, seals, card faces and campaign IP require an official/user-provided asset or an explicit replacement blocker.
- Generated visuals should not contain Chinese body copy; editable/vector layers carry labels and text.
- Missing image backends produce actionable prompts and filenames instead of fabricated success.
- The system does not pretend a sample preview is a finished deliverable when no real source has been provided.
- The production-quality path remains Agent/orchestrator-led; the Bridge is not a multi-tenant headless service, and decks above roughly 16 pages should use the resume workflow after planning.
- PowerPoint-specific rendering can vary by Office version and installed fonts; use the native-object and visual checks before external delivery.
- Free-form Canva-style canvas editing, deal-room analytics and complex multiplayer collaboration are intentionally out of scope for v6.
Capability history and canonical release links
Hybrid-Editable Visual Workflow v4.0 · Simplified Web Console v4.1 · DeckIR AI Planning Workflow v4.2 · v4.3 Rendered Review Loop · Release Notes - v5.0.0 · Release Notes - v5.1.0 · Release Notes - v5.2.0 · Release Notes - v5.3.0 · v5.4 Swiss Deck and Asset Factory (examples/swiss-v54-demo/index.html, npm run audit:swiss-deck) · v6.1.0
| Goal | Guide |
|---|---|
| Understand the v6 workspace | Web Experience |
| Connect local files and Agents | Agent Connect Bridge |
| Install the Agent Skill | Agent Setup |
| Choose PPTX, Web Deck or Desktop | Choosing a Workflow |
| Configure models and providers | Model and Provider Setup |
| Review v6 changes | v6.1.0 Release Notes |
| Troubleshoot | Troubleshooting |
Issues, reproducible source examples, proof packs, layout directions, provider adapters and quality checks are welcome. Please keep public claims tied to an executable test, audit, documented proof or release note.
MIT. The latest Guizang PPT Skill and Baoyu Design methods informed parts of the registered-layout, rhythm, editable-delivery, and review discipline. This repository maintains its own design directions, implementation, safety rules, and quality contracts.
If this project helps you turn “AI-generated slides” into something you can actually deliver, consider starring the repository — it makes the work easier for the next person to discover.