presentation-design git:20261101.8ad137dA

Immutable. This exact content never changes and is served at /api/v1/blob/049513ca305b0649.

---
name: presentation-design
description: Design or substantially redesign editable presentations when slide quality matters, including PPT/PPTX decks, reports, pitches and technical presentations. Organize grounded content into coherent slides and inspect rendered pages; use an editing workflow for narrowly scoped alignment or color changes.
---

# Presentation design

Identify the audience, decision and supplied facts before choosing a visual style. Preserve the requested slide count, format, brand and edit scope. A sparse source calls for clear information design, not invented data or a larger deck.

Choose each slide's main takeaway and how its content relates: sequence, comparison, hierarchy, process or one important metric. Use that relationship to choose a layout. A title plus pasted prose is a draft, even when its words are correct. Charts need relevant source data; diagrams must distinguish proposed steps from established facts.

Build a coherent deck with consistent grid, typography and visual language. Use editable text and shapes where appropriate. Give sources a readable place without competing with the main message. White backgrounds and restrained styling can work well; decoration and complexity are not quality measures.

Render the saved deck and inspect every page, then the sequence as a whole. Check accuracy and visual communication separately using [the review criteria](references/slide-review.md). Fix clipping, unreadable labels, weak hierarchy and disconnected pages before delivery. Structural counts and successful file creation do not establish visual quality. If direct visual inspection is unavailable, disclose that limitation rather than claiming the deck was visually verified.

Deliver the editable presentation and a concise account of verified changes. Preserve the source during revision. This optional workflow uses available editors or document libraries through ordinary execution tools; it adds no Agent tool, dependency, model selection or quota policy.