Pptx Deck Context

by wshobson46891e7e60daNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Use when preparing the narrative, sources, and design context for a new editable PPTX deck.

AI-generated overview

Prepares narrative, source lineage, and design context for a new editable PPTX deck before slides are authored.

What it does: This skill guides the pre-authoring phase of an editable PowerPoint deck: confirming audience, decision, slide count, language, sources, and brand requirements. It helps select a narrative framework, assign stable source IDs with source_ref plans for every metric, quotation, chart value, and factual claim, and choose a documented design direction. It records the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in a summary before slides are written.
When to use it: Use it when starting a new editable PPTX deck and the narrative, sourcing, and design context need to be settled first. It fits situations where audience, decision, and brand requirements must be confirmed before any slide coordinates or objects are authored.
Requirements: No scripts are included; it is instructions only. It references a bundled design-profiles document and expects the agent to read it. It may draw on user-provided brand guides or read-only reference decks, but no specific tools, packages, runtimes, credentials, or network access are required.

PPTX Deck Context

Prepare the deck before coordinates or PPTX objects are authored. This skill owns the business narrative, source lineage, and design lock.

Confirm audience, decision, slide count, language, sources, and brand requirements.
Use the user-selected narrative framework. If none is specified, offer mckinsey, scqa, pyramid, mece, action-title, assertion-evidence, exec-summary-first, or custom; do not choose silently.
Assign stable source IDs and plan a source_ref for every metric, quotation, chart value, and factual claim.
Choose a documented design direction. Prefer a user brand guide, then read-only reference-deck evidence, then a reusable profile from references/design-profiles.md.
Record the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in summary before authoring slides.

One slide should communicate one message, with an action-style title where the framework calls for it.
Treat design references as design evidence, not content or asset sources.
Do not copy external fonts, images, icons, or logos without recorded licensing evidence.
Translate design signals into explicit fills, typography, spacing, and bboxes; do not rely on an automatic layout engine.
Keep long source material concise. Ask for a summary or decision-relevant excerpt instead of turning a deck spec into a document dump.

See references/design-profiles.md for reusable profile guidance.

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.