infographic-powerpoint-deck

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: infographic-powerpoint-deck
description: Create image-based PowerPoint decks by (1) turning raw article content or notes into a detailed per-slide message plan when needed, (2) turning that message plan into a slide display plan and then a visual-production plan, (3) generating one 16:9 slide image per slide with all displayed text baked into the image (English by default; multilingual slide text supported), and (4) assembling an images-only .pptx that simply concatenates those images full-screen. Use when the user wants polished, consistent visuals with extensible style packs (cinematic dark, cinematic light, cinematic editorial, illustrative cinematic, animated feature, editorial, warm pastoral, tech, youth social, academic, corporate, whiteboard sketch), prefers not to hand-layout PPT objects, or wants a repeatable prompt workflow to iterate over time.
---

# Infographic PowerPoint Deck

## Default input model (raw article first)

This skill should work directly from the user's raw article content by default.

If the user provides a full article, sermon, report, or long notes:
1. Read the source content and infer the audience, burden, density, and argument/story structure.
2. Build `slides_message_plan.md` from the article structure.
3. Turn `slides_message_plan.md` into `slides_display_plan.md`.
4. Turn `slides_display_plan.md` into `slides_visual_plan.md`.
5. Write one image prompt per slide and generate the deck.

If the user already provides `slides_message_plan.md` or an equivalent content-first slide table, you can skip the article-intake step and use that directly.

If the user provides one or more reference slides/screenshots, use `references/reference_slide_intake.md` to extract the reusable visual grammar before writing prompts.

## Artifact model

Use three distinct planning artifacts:

- `slides_message_plan.md`
  - content / presenter planning only
  - what each slide is meant to teach, explain, or say in full
  - the detailed speaking content or narrative burden behind the slide
  - source/article anchors, scripture/evidence anchors, and must-preserve claims
  - what beats must stay separate

- `slides_display_plan.md`
  - what will actually be shown on the slide
  - title, verse fragment, module headers, bullets, labels, captions, footer references
  - explicit on-slide text after text-budget and archetype decisions
  - can be much shorter than the message plan

- `slides_visual_plan.md`
  - downstream visual-production planning
  - deck archetype
  - style pack choice
  - layout routing
  - scene choice
  - text budget and other production constraints

`slides_message_plan.md` is the source of truth for what the presenter means to communicate.
`slides_display_plan.md` is the source of truth for what text the audience actually sees.
`slides_visual_plan.md` is the source of truth for design and prompt production.

## Quick start (default: images-only deck, structured planning)

1. Start from either:
   - raw article content / notes and use `references/article_intake_workflow.md`, or
   - a prebuilt `slides_message_plan.md`, or
   - an underspecified content slide table that you will normalize first
   - optional reference slide images / screenshots and use `references/reference_slide_intake.md`
2. If starting from a raw article, create `slides_message_plan.md` first.
3. Infer one **deck archetype** from the approved message plan using `references/deck_archetype_routing.md`.
   - If the user explicitly requests a style, use that as an override.
4. Pick one **style pack folder**.
   - If user does not specify style and archetype does not strongly imply a different choice, default to `editorial-light`.
   - Style pack chooses the deck's visual language (palette, lighting, typography attitude, scene bias). It does **not** force one fixed layout for every slide.
5. Create `slides_display_plan.md` from `slides_message_plan.md`.
   - Decide what the audience should actually see on each slide after consideri