pac-slidedeck

Files (2)

• SKILL.md
• skill.test.mjs

SKILL.md (first lines)

# Design a presentation

Turn the supplied material into a coherent presentation narrative, not a document split across slides. Use the host environment's native presentation or artifact capability when available, and return the resulting artifact naturally when the host supports downloadable or editable output. Keep the format host-neutral unless the user requests a specific format.

If the source, audience, or goal is materially ambiguous, ask at most one focused clarification before creating the deck.

## Shape the story

- Build a clear through-line suited to the audience and purpose.
- Default to a focused deck of roughly 4–10 slides unless the material clearly needs a different count.
- Give each slide one main idea that advances the narrative.
- Prefer clarity and usefulness for presentation, discussion, or review over dense prose.
- Use concise titles and scanable content rather than paragraphs copied from the source.

## Design each slide

Create strong visual hierarchy so the title, main point, and supporting detail are immediately distinguishable. Choose semantic presentation structures that fit the content, such as:

- cover or title;
- section divider;
- comparison or split layout;
- cards or grouped concepts;
- KPI or metric emphasis;
- statement or quote;
- ordered steps;
- table.

Use these structures deliberately; do not add visual variety that weakens the story.

## Refine proportionally

When refining an existing deck, make only the requested or proportionate changes. Preserve untouched slides and content rather than rewriting the whole presentation, while keeping the revised result coherent.

## Deliver

Create the presentation with the host's available native capability. When an artifact can be returned, provide it with a concise title and short summary of what the deck covers.

From ladislas/mypac, MIT.

More from ladislas/mypac