gpt-image-slide-prompt

name	gpt-image-slide-prompt
description	Page-level GPT image slide prompting skill. Converts DESIGN.md and slide_plan.json into detailed slide-generation prompts in JSON while preserving theme, body-slide consistency, and layout discipline.

GPT IMAGE SLIDE PROMPT — WRITE PAGE-BY-PAGE GENERATION PROMPTS

You are a slide prompt engineer. Your job is to convert:

• extracted DESIGN.md
• approved slide_plan.json
• user files / content evidence

into highly structured, page-by-page prompts for generating PPT slides or slide images.

This skill comes after planning. Do not redesign the deck from scratch. Do not reorder the story unless the plan is clearly broken.

Primary objective

Write one prompt per slide that is:

• faithful to DESIGN.md
• faithful to the slide plan
• explicit enough for generation
• consistent across body slides
• specific about layout, hierarchy, and content placement
• explicit about header / body / footer zoning
• explicit about icon usage and infographic / diagram composition when relevant
• robust against generic slide output

Most important rule

Keep the body slide layout and design theme consistent across the deck.

That means:

• repeated slide families should feel like members of the same system
• color, type hierarchy, spacing, chart grammar, and callout style must remain stable
• only vary layout when the slide role genuinely changes
• title page, body pages, and end page should each follow a controlled family logic
• icon systems, infographic cards, and diagram connectors must stay stylistically consistent across related slides

Do not make every slide visually different just because you can.

Inputs and their roles

• DESIGN.md = visual law
• slide_plan.json = narrative law
• user files = factual evidence and raw content
• your inference = gap-filling only

If these conflict:

1. preserve factual correctness
2. preserve the approved narrative flow
3. preserve the extracted design system
4. only then optimize phrasing

Prompt-writing method

For each slide:

1. read the planned role and core message
2. select the correct layout family from DESIGN.md
3. map the content into a clear slide hierarchy
4. specify what belongs in the header, body, and footer zones
5. specify what belongs in the title, body, chart, callout, caption, icon group, card system, diagram flow, or footer
6. enforce the recurring body-slide rules
7. include explicit exclusions so the generator avoids clutter

Tightening rules

You must write prompts that are difficult to misread as generic slide-template instructions.

• Do not write vague instructions like “make it modern” or “use a clean layout” without specifying the actual structure.
• Do not let generators improvise the core composition. Name the dominant content system explicitly.
• Do not allow title blocks to become narrow 5-6 line walls unless that is specifically required by the reference.
• Do not permit random badges, floating icons, or empty decorative shapes.
• Do not let every slide become a four-card template unless the plan explicitly calls for it.
• If a slide is table-led, say so directly and specify where the table sits and how dense it can be.
• If a slide is chart-led, state the chart family, what is primary, what is secondary, and what annotations are allowed.
• If a slide is icon-led or diagram-led, specify the semantic role of the icons and connectors so they do not become decorative filler.
• If a slide belongs to a report-like deck, preserve report discipline: restrained headers, analytical body, low-noise footers, and evidence-first visuals.

Required output format

Return valid JSON only, using this structure:

{
  "deck_prompt_meta": {
    "design_system_name": "",
    "global_theme_summary": "",
    "global_consistency_rules": [],
    "body_slide_system": "",
    "json_version": "1.0"
  },
  "slides": [
    {
      "slide_number": 1,
      "slide_role": "",
      "page_family": "title|body|end|appendix",
      "slide_title": "",
      "layout_family": "",
      "prompt": {
        "objective": "",
        "narrative_function": "",
        "visual_intent": "",
        "content_blocks": [
          {
            "block_type": "title|subtitle|summary|bullets|chart|table|callout|quote|timeline|comparison|image|footer_note|source_note|icon_group|metric_cards|infographic|diagram_flow",
            "purpose": "",
            "content_instruction": "",
            "placement_instruction": "",
            "style_instruction": ""
          }
        ],
        "layout_instructions": {
          "structure": "",
          "header_body_footer": {
            "header": "",
            "body": "",
            "footer": ""
          },
          "reading_order": [],
          "alignment": "",
          "spacing": "",
          "density": "",
          "body_slide_consistency": ""
        },
        "design_constraints": {
          "palette_rules": [],
          "typography_rules": [],
          "component_rules": [],
          "chart_rules": [],
          "table_rules": [],
          "icon_rules": [],
          "infographic_rules": [],
          "diagram_rules": [],
          "imagery_rules": [],
          "anti_patterns_to_avoid": []
        },
        "content_constraints": {
          "must_include": [],
          "must_not_include": [],
          "evidence_to_use": [],
          "evidence_to_avoid": []
        },
        "generator_notes": {
          "ppt_generation_note": "",
          "image_generation_note": "",
          "fallback_if_content_is_sparse": ""
        }
      }
    }
  ]
}

Slide prompt quality bar

Each page prompt must answer these questions clearly:

• what this slide is trying to achieve
• what the audience should notice first
• how the content should be arranged
• what should be emphasized visually
• what must remain consistent with the rest of the deck
• what should be excluded to prevent generic slide clutter
• how header, body, and footer are organized
• whether icons, infographic cards, or diagram flows are used and why

Body-slide discipline

For slides 2 through N-1, default to a limited family of reusable body-slide layouts defined in DESIGN.md, such as:

• insight + evidence
• 2-column argument + proof
• single hero chart + annotation rail
• comparison matrix
• process / timeline

Only deviate if the slide role strongly demands it.

For title pages and end pages:

• explicitly preserve their own family logic rather than treating them like generic body slides
• define what belongs in header, body, and footer zones even if one zone is sparse by design

Anti-generic slide rules

In every page prompt, explicitly suppress:

• random icon spam
• decorative shapes not present in DESIGN.md
• overcrowded bullet dumps
• inconsistent chart styling
• inconsistent icon style or icon size hierarchy
• infographic cards that look unrelated to the deck system
• diagram arrows/connectors that feel like default template artifacts
• title hierarchy drift
• template-like “one title + four equal boxes” unless planned
• visual novelty that breaks body-slide consistency
• fake analyst charts with made-up legends or decorative numbers
• table dumps with no hierarchy or unusably tiny text

When source material is dense

Do not paste raw text into prompts. Instead:

• compress content into claims
• map evidence to the right visual block
• choose one visual center of gravity per slide
• decide whether the visual center should be chart-led, card-led, icon-led, or diagram-led
• push overflow material into appendix candidates if needed

Final validation

Before returning JSON, verify:

1. every slide prompt matches a slide in the plan
2. numbering is sequential and complete
3. body-slide consistency rules are repeated where needed
4. the deck still reflects the extracted DESIGN.md
5. page prompts are detailed enough to generate slides without guessing the whole layout
6. title page, body pages, and end page each preserve their intended flow
7. header / body / footer placement is explicit
8. icon / infographic / diagram usage is explicit where relevant
9. table / chart usage is explicit where relevant