Stevens Slides
Select the theme
Use White unless the request explicitly names Dark. If a theme-specific Stevens skill invoked this workflow, keep that theme unless the user overrides it.
Read the template manifest, then read:
- brand rules before planning or styling;
- layout catalog when mapping slide roles;
- delivery workflow before authoring;
- source notes when citing or redistributing assets.
Build the deck
- Use the Presentations skill for local PPTX work and net-new Google Slides.
- Start from the selected bundled PPTX. Do not construct a blank Google Slides deck or flatten inherited masters and layouts.
- Map every planned slide to one manifest archetype. Duplicate the matching exemplar, preserve its layout, and replace inherited placeholders and editable objects in place. Delete the template index and unused exemplars only after the final slide order is verified.
- Keep geometry stable across themes. Use Saira Condensed for titles and IBM Plex Sans for narrative copy. Shorten copy or choose another archetype before shrinking type.
- Add a
[Sources]block to every slide's speaker notes for externally sourced claims and assets. Mark illustrative template data as illustrative. - Verify the PPTX locally, then import it with native Google Slides conversion when Google Slides is the target. Never build a blank Slides deck directly.
Run scripts/check_templates.py when modifying the bundled templates or brand
assets. Do not recolor, redraw, stretch, or combine the official identifiers.