morph-ppt

What it does

This skill extends the base pptx v2 rules with morph-specific behavior. It enables cross-slide shape-name binding, scene actors prefixed with !!scene-* and !!actor-*, and per-slide content using #sN-* to achieve smooth morph transitions when the user requests morph-like motion across at least two consecutive slides. It governs how shapes are named, ghosted, and moved (including exiting off-canvas via a ghost position), and it documents the morph workflow, including the auto-prefix quirks and how to apply transitions with transition=morph.

How it works

• Inherits all pptx v2 rules (visual floor, grid, palettes, delivery gates, etc.). The skill adds only morph-specific: cross-slide shape-name binding, namespace prefixes !!scene-*, !!actor-*, and #sN-* for per-slide content.
• Morph is activated when a slide pair contains transition=morph on the target slide; the agent uses the morph workflow, matching identical name= values across adjacent slides to interpolate position, size, rotation, fill, and opacity.
• Scene actors persist or ghost across slides according to the three-prefix naming system; shapes prefixed with !!scene-* are background decorations, !!actor-* are evolving content, and #sN-* are per-slide content that ghost off-canvas on subsequent slides.
• Ghosting rules require exiting shapes to be moved to x=36cm or otherwise prepared to exit the morph; leaving shapes unpaired results in silent fades or no morph.
• The skill specifies how to construct and plan morph pairs in advance (Morph Pair Planning table) and emphasizes that naming must avoid collisions and that charts can participate if given an identical !!-name across slides.

When to use it

Use this skill when the user explicitly asks for morph motion / smooth transitions / continuous animation AND ≥ 2 consecutive slides share a visual element that transforms. If the deck lacks cross-slide motion, stay with the pptx v2 base. If the deck is fundraising narrative without morph, consider the sibling skill for pitch decks.

What it can touch

• The skill relies on commands such as officecli add, officecli set, and officecli batch to manage slides, shapes, and transitions. It requires proper usage of name=, transition=morph, and prefixed names !!scene-*, !!actor-*, and per-slide #sN-* content.
• It documents specific shell-quoting rules for morph safety (e.g., --prop 'name=!!scene-ring') and the use of batch heredocs for multi-shape slides.

Caveats

• Morph only interpolates shape properties for identically named shapes across slides; the plotted data inside charts cannot be morph-interpolated. If data visualization needs morph-like behavior, use morph-paired shapes with identical !! names instead.
• Renderer differences: Morph renders in PowerPoint 365 / Keynote / WPS; LibreOffice may render as plain fade. The plan should account for renderer variations.
• This skill inherits the base pptx v2 constraints (visual floor, grid, palettes, etc.) and should not re-teach them; follow the Morph-specific additions and Gate 5b checks for validation.