Morph Motion PPTX
This skill produces premium motion using PowerPoint Morph slide transitions, not traditional Animation Pane effects. Each moving object is a real object on consecutive slides; Morph interpolates its position, size, rotation, crop, and style.
Use this skill together with the pptx skill when creating or editing a deck.
Pattern selection
| Pattern | Canonical ID | Best for | Signature motion | Reference |
|---|---|---|---|---|
| Panning gradient shards | pan-gradient | Urban/tech/cinematic hero slides, section openers | Three translucent slanted planes pan right while the hero image zooms out | references/pan-gradient-recipe.md |
| Rotating blade reveal | wheel-rotation | Image-led story slides, mood transitions, title reveals | A huge shadow blade rotates about 90° per slide while captions cycle vertically | references/wheel-rotation-recipe.md |
For deep mechanics, matching rules, and XML, read references/morph-mechanics.md.
Before delivery, run the checks in references/qa-checklist.md.
Clone-first rule for high fidelity
When the user wants "similar," "same as," or pixel-level fidelity, copy the matching bundled reference deck into the working directory first and treat it as a template:
assets/reference-decks/pan-gradient-reference.pptxassets/reference-decks/wheel-rotation-reference.pptx
Never edit the bundled reference itself. Open the copy, duplicate a designed slide, then replace images/text while preserving the named moving objects and their z-order. This is more reliable than redrawing every freeform from scratch.
Use scripts/analyze_morph_pptx.py to inspect the reference before changing it.
Required build workflow
- Lock the canvas. Use 16:9 at
12192000 x 6858000EMU unless the user explicitly requests another size. If resizing, scale all EMU values proportionally; rotation angles do not scale. - Choose the layer model. Use a picture shape when the image must pan or zoom. Use a slide background only when the image should crossfade in place. The pan-gradient recipe depends on this distinction.
- Build at least two states. Put the start geometry on one slide and the end geometry on the next. Morph is the interpolation, so the slides must remain individually valid end states.
- Duplicate slides instead of recreating moving objects. This preserves object names and ordering. Keep each moving object's exact name, type, z-order, crop, and basic geometry consistent across adjacent slides.
- Name objects explicitly. Use unique, stable names such as
!!Hero_Image,!!Pan_Shard_A,!!Wheel_Blade, and!!Caption_Center. The!!prefix is a useful forced-matching cue; still keep the same object type and structure. - Change only the motion-relevant properties. Prefer changing
x,y,cx,cy,rot, crop, or color stops. Avoid replacing the object with a newly inserted one. - Apply Morph. Set each animated slide after the first to
MorphwithbyObjectand2000 msas the default. Keep a fade fallback for compatibility. - Validate the package and playback. Run the analyzer, open the deck in PowerPoint, and play the slideshow transition. Do not judge animation from a PDF, static thumbnail, or LibreOffice preview.
Motion direction and timing defaults
| Parameter | Default | Notes |
|---|---|---|
| Transition | Morph, by object | p159:morph option="byObject" |
| Duration | 2000 ms | 1500 ms feels crisp; 3000 ms feels slower and more luxurious |
| Slide count for pan-gradient | 2 | More slides can repeat the gesture with new imagery |
| Slide count for wheel-rotation | 4 | 3 is the practical minimum; 4 creates a full rotation cycle |
| Wheel step | about -90° | Exact reference angles are in the wheel recipe |
| Text entrance/exit | off-canvas to center | Keep text boxes named consistently so they do not pop |
If the user asks for a different duration, still set both the spd hint and p14:dur; PowerPoint honors the millisecond duration.
Implementation options
PowerPoint or template editing
Duplicate the reference slide, replace the image, move named objects, update text, then set:
Transitions > Morph > Effect Options: Objects > Duration: 02.00
python-pptx, PptxGenJS, or raw OOXML
Build static slides in any tool that can assign shape names, then run:
python scripts/inject_morph_transition.py input.pptx output.pptx --slides 2- --duration 2000 --option byObject
This writes the correct mc:AlternateContent wrapper, Morph choice, and fade fallback without requiring PowerPoint automation.
Existing deck cleanup
python scripts/analyze_morph_pptx.py deck.pptx --strict
Fix duplicate names, missing Morph slides, unstable object identities, and unexpected transitions before delivery.
Precision rules
- Keep the moving object's name and id path stable across adjacent slides. Names matter more than a new id, but cloning the slide is safest.
- Keep z-order stable. Reordering layers can cause apparent hard cuts or incorrect masking.
- Keep fills, lines, shadows, and crop modes stable unless the change itself is part of the animation.
- Use one large hero image per slide. Avoid baking title text or UI into the image if it should stay sharp.
- Use high-resolution imagery, ideally at least 1920x1080; the pan recipe may start at 164% scale.
- Do not add Animation Pane motion to the same object unless requested. Competing animations make Morph unpredictable.
- Preserve a readable safe area. The reference title sits around 11% from the left and 24% from the top.
- Export an MP4 if the recipient may use software without Morph support.
Output contract
Deliver:
- The completed
.pptx. - A one-line note naming the pattern and transition duration.
- Any replacement assets or a list of required assets if the user did not provide them.
- A reminder that the motion must be viewed in PowerPoint Slideshow mode.
Do not claim the motion was visually verified if you only inspected static slides. Static checks prove structure; PowerPoint playback proves the effect.