mcpField
P
pptx-deck-context

pptx-deck-context

github.com/wshobsonDocuments41.9k2.7k installsUpdated 2w ago
Repository

About pptx-deck-context

A skill for planning PPTX content and design before slide authoring. It establishes the audience, decision, narrative framework, and source lineage, then records explicit design rules and assumptions.

Key features

  1. 01Confirm audience, decision, and sources
  2. 02Select a narrative framework
  3. 03Assign source references to claims
  4. 04Record palette and typography rules
  5. 05Translate design evidence into explicit layout

Use cases

  1. 01Shape a business narrative before authoring slides
  2. 02Plan source traceability for data and claims
  3. 03Set a deck design based on brand guidance
  4. 04Avoid dumping lengthy source material into slides

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wshobson/agents --skill pptx-deck-context

After installing, type/pptx-deck-contextin Claude Code to confirm it loaded.

Bundled filesreferences/design-profiles.md

Details

From the project README

PPTX Deck Context

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

Decision sequence

  1. Confirm audience, decision, slide count, language, sources, and brand requirements.
  2. 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.
  3. Assign stable source IDs and plan a source_ref for every metric, quotation, chart value, and factual claim.
  4. 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.
  5. Record the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in summary before authoring slides.

Rules

  • 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.

Comments

Markdown supported