Prep That Slide

Make a presentation that the intended reader can understand, trust and act on. Visual choices serve that purpose. A client review, investor pitch, research briefing and live talk need different density, pacing and evidence.

Establish The Deliverable

Read the brief, supplied material and any existing deck or generator before editing. Preserve useful source structure and the user's chosen tools. Determine the audience, desired decision, delivery format, reading setting and constraints from context. Ask only for missing information that would materially change the result; otherwise state a reasonable assumption and proceed.

• For a PDF sent without a presenter, make the argument complete on the page. Speaker notes cannot carry essential qualifications or decisions.
• For a live talk, simplify the projected pages and put permitted supporting detail in notes or a handout.
• For a narrow revision, change the affected pages and shared styles only as needed. Recheck all pages affected by a shared change.
• Honor a requested PDF, editable slide file, HTML deck or paper size. Do not substitute a web link for a requested PDF. If the format is unspecified, infer it from the use: a PDF for reading, an editable slide deck for a presenter or team handover, HTML for browser delivery. If that distinction is still unclear and affects the build, ask one short question. Editable HTML source is not an editable PowerPoint file.

For an attached PowerPoint redesign, read the existing-deck workflow. Preserve the original, inspect its slides and notes, and verify that the revised deck retains the supplied facts.

For Google Slides, read the connected editing workflow. Check that the integration exposes the needed slide-editing operations and that the account can edit the target deck. A connection that only searches or reads files cannot update slides. Verify changes in the target presentation before claiming delivery. The skill supplies guidance, not a Google integration or a PDF/PPTX export engine.

Do not require a particular model, paid service, icon vendor or publishing account. Prefer tools already available. Follow the project's dependency and external-action permissions; creating a deck does not authorize sending or publishing it.