Jobs Style Ppt Generator

Jobs Style PPT Generator

Overview

Rewrite the source into a tighter speaking script first, then generate the deck. Keep the original point of view intact. Make the deck feel like a keynote, not a document dump.

Workflow

1. Read the source and map the narrative

Accept either:

• a markdown/plaintext script file
• a topic plus rough bullet points
• a long article that needs to become a talk

Extract:

• the main thesis
• the section boundaries
• the strongest contrasts, pain points, metaphors, and numbers
• which 5-10 ideas deserve dedicated slides

If the source is long or repetitive, compress it before writing slides. One screen should communicate one idea.

2. Create the rewritten script before editing the PPT

Never overwrite the user's original file. Create a sibling file named {original_basename}_修改版.md.

Structure the rewritten file like this:

1. Cover annotation: [PPT：主标题 / 副标题 / 系列名]
2. Hook: 2-4 short lines, strong enough for the first 5 seconds
3. For each section:
   • one standalone keynote-style title line
   • one PPT annotation line such as [PPT：问题页 / 金句页 / 步骤页]
   • spoken copy rewritten into short spoken lines
4. Ending:
   • a summary line
   • a call to action or next-episode teaser

Use [停顿] or (放慢) only when it improves rhythm.

Read references/style-guide.md when you need title formulas, slide patterns, or rewriting heuristics.

3. Initialize the deck scaffold

Always use the bundled script instead of hand-creating the first HTML file. Resolve the script path relative to the skill directory:

./scripts/init-ppt.sh \
  --title "主标题" \
  --slogan "一句短标语" \
  --series "系列名" \
  --ratio "vertical" \
  --output "/absolute/path/to/output-dir"

Rules:

• run the command from the skill root, or resolve scripts/init-ppt.sh relative to this SKILL.md
• --output must be an absolute directory path
• --ratio vertical creates the warmer 9:16 keynote template
• --ratio horizontal creates the denser 16:9 template for matrices, diagrams, and comparisons
• the script creates presentation.html
• the generated file is a single HTML file with domestic CDN links, keyboard navigation, grouped animation, icon support, emoji-safe rendering, and Markdown-aware helpers

OpenClaw compatibility:

• the skill can live under ~/.openclaw/skills/ or any workspace skills/ directory that OpenClaw scans
• the same folder also works as a Codex skill when copied into ~/.codex/skills/

4. Replace the scaffold slides with the real deck

Edit the generated slides array inside presentation.html.

Available helpers in the vertical template:

• coverSlide(title, slogan, series)
• titleSlide(title, subtitle)
• highlightSlide(prefix, highlight, gradientClass)
• markdownSlide(title, markdown, options)
• cardGridSlide(title, cards, options)
• endSlide(message, cta)

Available helpers in the horizontal template:

• coverSlide(title, slogan, series, emoji)
• summaryGridSlide(config)
• matrixSlide(config)
• flowDiagramSlide(config)
• swarmSlide(config)
• proofSlide(config)
• closingSlide(title, summary, series)

Use the helpers directly. Do not rebuild the entire HTML structure unless the template is clearly insufficient.

Markdown and emoji notes:

• Titles, subtitles, card copy, matrix values, and proof content may use inline Markdown such as **重点**, list bullets, and inline code
• emoji may be used directly in strings such as 🔥, 🚀, 🦞, ✅
• prefer emoji as accent markers, not as decoration spam

Recommended slide flow:

1. cover
2. hook or question
3. contrast or pain point
4. key conclusion
5. process or steps
6. supporting comparison
7. ending

5. Keep the visual language strict

Follow these defaults unless the user explicitly asks for a different direction:

• warm charcoal background with amber, gold, cyan, and blue highlights
• white or warm-white primary text, softer secondary text
• grouped motion: let text blocks and image blocks drift as a unit
• use higher saturation than default dashboard UI; this should feel like a stage, not a B2B admin tool
• 9:16 for punchy narrative decks
• 16:9 for dense comparisons, model matrices, and system diagrams
• very large headline, compact supporting copy
• bold or black title weights
• icons and diagrams are preferred when they improve scan speed
• subtle atmospheric motion is good; noisy particles and random independent bouncing are not

If you need more detailed rules, load references/style-guide.md.

6. Preview locally

Prefer a zero-dependency preview:

cd /absolute/path/to/output-dir
python3 -m http.server 5173

Then open http://127.0.0.1:5173/presentation.html.

If the environment already uses Vite and the user explicitly wants Vite, serve the folder with Vite instead. Do not introduce a framework build step unless it materially helps.

Output Contract

Deliver these artifacts when possible:

• rewritten script: {original_basename}_修改版.md
• deck: /absolute/path/to/output-dir/presentation.html

In the final user response, report:

• where the rewritten script was saved
• where the deck was saved
• whether preview was started successfully

Resource Map

• Use references/style-guide.md for copy and slide rules.
• Use assets/presentation.template.html for the warmer 9:16 template.
• Use assets/presentation-horizontal.template.html for the denser 16:9 template.
• Use scripts/init-ppt.sh whenever a new deck is needed.