morph-ppt

Automating morph transitions involves using officecli to generate PowerPoint decks that enforce strict morph naming conventions (!!scene-*, #sN-) and apply ghosting to manage slide transitions consistently. This ensures repeatable animated decks for demos and pitches.

The morph naming convention requires prefixing elements with !!scene-* and #sN- tags so PowerPoint can track object movement and ghosting across slides during morph transitions. This standardization prevents animation errors and ensures smooth visual continuity.

Create repeatable animated decks by following a phase-based design workflow: plan morph-pairs, clone slides with officecli, ghost old content, add new content, and run a final automated verification check to ensure morph is configured correctly.

Yes, officecli supports morph-based workflows by integrating morph-helpers for cloning slides, ghosting old content, and running final verification checks across slides to validate that morph transitions are configured correctly.

Morph transitions fail when object naming conventions are inconsistent or ghosting is not applied to hidden elements. Enforce strict !!scene-* and #sN- naming tags and run automated verification to identify and fix mismatched morph pairs.