返回提示词目录第 1465 页

规划演示文稿逐页视觉呈现

把每页内容转成明确观点,匹配能支撑观点的图表或视觉布局,并整理数据需求与整套演示的视觉规则。

完整提示词

<context>
Slides that only repeat the speaker's words in bullets make the audience read instead of listen. The assertion-evidence approach, tested in engineering and science presentations, works better: each slide's title is a full-sentence claim, and the body is the visual evidence for it. The right visual follows from the relationship in the content: change over time is a line, comparison across items is a sorted bar, part of a whole is a stacked bar (a pie only for two or three parts), a distribution is a histogram, a relationship between two measures is a scatter, a process is a flow, a hierarchy is a tree, a sequence of events is a timeline. Some slides need no visual at all: a single big number, a quote, or a question can carry the slide on its own.
</context>

<task>
Plan the visuals for this deck.

<slide_outline>
{{slide_outline}}
</slide_outline>
{{#brand_constraints}}
<brand_constraints>
{{brand_constraints}}
</brand_constraints>
{{/brand_constraints}}

1. If the outline has no clear message per slide, or the slides with data have no numbers, say which slides are affected; plan the rest and mark those slides as needing input rather than guessing.
2. For each slide, state its message as a full-sentence assertion title (rewrite the title if it is a topic label like "Q3 results").
3. Choose the visual that proves that assertion, or "none" if text, a big number or a quote does the job better. Name the specific type (for example "horizontal bar, sorted descending, 6 regions"), not just "chart".
4. Give layout notes: what to highlight (one bar in the accent colour, a callout on the key point), what to remove (gridlines, legend if labels can sit on the data), and where the eye should land first.
5. For each chart, list the exact data it needs, and whether the outline supplies it.
6. Set a handful of rules for the whole deck so visuals stay consistent.
</task>

<constraints>
- One message per visual. If a slide is trying to show two things, propose splitting it.
- Prefer simple, honest charts: no 3D, no dual axes unless unavoidable (and then say why), bar axes start at zero, and no pie with more than three slices.
- Use stock photos only where an emotional or concrete image adds meaning (a customer, the product in use, a place); never as decoration.
- Accessibility: do not encode meaning by colour alone, keep text on slides readable from the back of the room (about 24 pt minimum for live decks), and note alt text for key visuals if the deck will be shared.
- If the deck will be sent rather than presented, allow fuller annotations on each visual and say so.
- Respect the brand constraints if given; if a constraint conflicts with readability, say so once.
- Use only numbers in the outline. Never invent data to fill a chart; mark gaps as `[NEEDED: …]`.
</constraints>

<output_format>
## Visual plan
A table: # | Assertion title | Visual | Layout notes.
## Charts to build
For each chart: slide number, chart type, data series and categories, sort order, the highlight, and axis and label notes.
## Rules for the whole deck
Four to six bullets (colour use, fonts, chart style, image style, how highlights work).
## Missing data
Bullets of `[NEEDED: …]` items, or "None".
</output_format>

可替换内容

  • {{slide_outline}}
  • {{#brand_constraints}}
  • {{brand_constraints}}
  • {{/brand_constraints}}
  • [NEEDED: …]

分类与标签

设计创意、演示文稿、图表设计、视觉叙事

前往 AI 图片创作