Design Consulting Slides

Turn an approved storyline into a visual argument and finished artifact. Own visual reasoning, composition, production, and rendered QA; do not adjudicate hypotheses or silently change the answer.

Confirm the handoff and format

Require approved answer/title spine; Audience/Onboarding Contract locator; presented or read_ahead; canonical page job | message/title | proof | source locator briefs; delivery mode; template/brand/permission/source constraints; and resolved or explicitly narrowed decision-material hypotheses. Return a defective title, proof, source, claim state, or reader assumption upstream instead of decorating it.

Choose:

• html_preview for a fast fixed-canvas proof;
• html_final for a final standalone browser deck;
• pptx_native for editable PowerPoint, template control, or requested PPTX; or
• dual when both are required or materially useful.

For PDF delivery without native-editability or template-control requirements, build the approved page in fixed-canvas HTML first and treat that HTML as the visual production master. Export PDF only as a uniformly scaled frozen render of the same 1600×900 composition; never maintain or repair a separate PDF layout.

Never substitute HTML/PDF for requested PPTX. Follow pptx-production-handoff.md and presentations:Presentations for native work; follow html-and-dual-render-production.md for HTML/dual.