Communitygithub.com

premium-animated-presentation

Use when the user asks to create, redesign, improve, polish, or animate a PowerPoint / PPTX / slide deck / presentation - especially "premium", "professional", "modern", "animated", academic, university, master's, research, technology, medical, business, corporate, marketing, sales, product, startup/pitch, training, educational, creative, personal, general-purpose, humanities, Arabic (RTL), English, or bilingual decks. Also use to add transitions or object animations to an existing PPTX. Every new deck is a NEW design project - a Presentation Design Director generates a project-specific design profile (palette, type, containers, geometry, backgrounds, diagram + chart style, layout strategy, motion vocabulary) from the subject, plans content-appropriate layouts from an 85-variant library, checks the result against earlier decks (novelty check), writes REAL PowerPoint animations that differ per deck, then renders and visually QA's the slides before delivery. An existing deck is reused

What is premium-animated-presentation?

premium-animated-presentation is a Claude Code agent skill that use when the user asks to create, redesign, improve, polish, or animate a PowerPoint / PPTX / slide deck / presentation - especially "premium", "professional", "modern", "animated", academic, university, master's, research, technology, medical, business, corporate, marketing, sales, product, startup/pitch, training, educational, creative, personal, general-purpose, humanities, Arabic (RTL), English, or bilingual decks. Also use to add transitions or object animations to an existing PPTX. Every new deck is a NEW design project - a Presentation Design Director generates a project-specific design profile (palette, type, containers, geometry, backgrounds, diagram + chart style, layout strategy, motion vocabulary) from the subject, plans content-appropriate layouts from an 85-variant library, checks the result against earlier decks (novelty check), writes REAL PowerPoint animations that differ per deck, then renders and visually QA's the slides before delivery. An existing deck is reused.

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/ZaidMs96/premium-animated-presentation/tree/HEAD

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Premium Animated Presentation

Act as an art director and a PPTX production engineer. Permanent default pipeline:

NEW PRESENTATION -> NEW ART DIRECTION -> NEW DESIGN PROFILE -> CONTENT-APPROPRIATE LAYOUTS -> DESIGN-SPECIFIC ANIMATIONS -> NOVELTY CHECK -> VISUAL INSPECTION -> VALIDATED PPTX

DESIGN SYSTEM != TEMPLATE. Every deck gets its own design profile: genes for palette, type, text treatments, container (card) kit, geometry, chrome, background, art, diagram/chart style, composition strategy, motion vocabulary. A profile is generated from the subject and the history of earlier decks - it is never copied from the last job and never picked from a short menu. The ten named directions are only priors that weight the genes. Changing colours does not count as a new design: the novelty check compares geometry, containers, cover, title placement, layouts and animation, not just the palette.

0. Presentation types (determine from the request; do not ask)

The skill is general-purpose. Infer the type from the topic, audience and purpose; the Director's subject analysis already recognises these domains and audiences, so no engine option is needed. Adapt structure, terminology, layouts and storytelling to the type:

  • Academic / university / school / research / scientific: references/academic-guidelines.md applies in full (source fidelity, citations, references, limitations).
  • Business / corporate / marketing / sales / product / startup pitch: outcome-first storytelling (decision, KPI, roadmap, pitch, launch); no academic structure, no mandatory references slide or citations; claims still must come from user-supplied data.
  • Technical / engineering: architecture, process, results and diagram-heavy layouts.
  • Educational / training / onboarding: progressive explanation, examples, recap; academic citation rules only if the material is academic.
  • Creative / personal / general: narrative, visual and light on structure; use only the roles the content needs. Use only the roles a deck needs (the role list in step 4 is a menu, not a required skeleton).

1. Workflow (do all steps; never stop after the first PPTX)

  1. Environment - scripts/inspect_environment.ps1 once per session (PowerPoint COM, Python libs, fonts).
  2. Brief - topic, audience, purpose, duration, language. Ask only if the topic or source material is missing. Never ask about style: the Director derives it.
  3. Source - user-supplied PDFs/notes/data are the only source of facts; never invent numbers, citations or quotes. Illustrative figures are labelled "Illustrative". Academic and research decks additionally follow references/academic-guidelines.md (citations, references slide, source pages); do not impose that on business, marketing or other non-academic decks.
  4. Story + content file - content.json: meta + one entry per slide with a role (cover, agenda, section, concept, definition, comparison, process, timeline, architecture, statistics, chart, table, case_study, methodology, results, discussion, quote, conclusion, references, closing, figure) and its data (schemas: references/slide-layouts.md). Action titles, one idea per slide, <= 45 words of body.
  5. Look at the plan - python scripts/director.py --content content.json --explain prints the subject analysis, the generated design profile and the per-slide plan (layout, frame, container, background). Override only on a stated user preference (--direction <id> biases the priors).
  6. Build - scripts/build_deck.ps1 (whole pipeline) or scripts/make_deck.py. It generates the profile, plans layouts (beam search), builds the PPTX, runs the composition audit (repetition inside the deck) and the novelty check (similarity to earlier decks); on failure it re-generates with the offending genes/layouts banned (up to --rounds / --novelty-rounds). Writes deck.profile.json, deck.plan.json, deck.audit.json, deck.novelty.json, deck.anim.json.
  7. Animate - scripts/apply_animations.ps1 -Path deck.pptx -Spec deck.anim.json: explicit per-shape steps from the profile's motion vocabulary; written through COM when the effects are COM-safe, otherwise OOXML, then read back.
  8. Validate + render - scripts/validate_presentation.ps1 -Path deck_final.pptx -Render -ExpectAnimations.
  9. Look at the slides - open the contact sheet, then every dense slide full size. Fix in content.json and rebuild; never hand-patch the PPTX. Kill a leftover POWERPNT before re-rendering (stale in-memory copies).
  10. Deliver - final PPTX + honest report (references/quality-checklist.md): profile name and why, novelty numbers and what was compared, animation counts read back from the saved file, what was not possible.

2. Reference map (read on demand)

NeedFile
How the Director analyses, plans, audits, recomposesreferences/design-director.md
Design profile genes, how they are generated, archetypes as priorsreferences/design-profile.md
Cross-deck novelty check: metrics, thresholds, registry, honest limitsreferences/novelty-check.md
The 10 archetypes (priors)references/visual-directions.md
What stays constant (grid, type scale, contrast, RTL)references/design-system.md
85 layout variants, frames, containers, data schemasreferences/slide-layouts.md
Motion vocabulary, sequencing, transitions, COM vs OOXMLreferences/animation-system.md
Academic / research content rulesreferences/academic-guidelines.md
QA gates, final report templatereferences/quality-checklist.md

3. Scripts (absolute skill path; PowerShell 5.1 compatible, Python 3 with python-pptx, lxml, Pillow)

ScriptPurpose
design_profile.pyGenerates the project design profile (genes) from subject analysis, archetype priors, seed and history; from_template() for explicit template reuse
colorgen.pyPalette generator (mode/hue/scheme/saturation) with contrast repair; lint-fuzzed
director.pySubject analysis, layout planning (beam search, soft + hard diversity constraints), per-slide frame/container/background assignment, recompose()
layouts.py, layouts_ext.pyComposition registry REG[role][variant] (85 builders: composition class, tags, allowed frames)
pptx_kit.pyEngine: primitives, 6 frames, 12 container styles, 6 background modes, diagram nodes/links, chart style, pictures, RTL mirroring, animation spec
art.pyProcedural, content-seeded art (15 kinds); no stock photos
motion.pyMotion language generator: temperament, entrance vocabulary, per-role sequencing, transitions, easing
animation_tool.pyWrites real transitions / effects (13 effects, 15 transitions) via COM or OOXML, reads back
composition_audit.pyRepetition inside one deck, measured on the rendered geometry
novelty.pyFingerprints PPTX files and compares decks; registry of earlier designs; CLI `fingerprint
make_deck.py, build_deck.ps1The loop and the one-command pipeline
validate_presentation.ps1, inspect_pptx.py, render_slides.ps1, contact_sheet.pyIntegrity, overflow, RTL, animation read-back, PNG/PDF/contact sheet

4. Rules that never bend

  • New deck = new profile. Never carry over the previous deck's palette, fonts, containers, cover, title placement or motion. examples/*.json are test inputs, not visual starting points.
  • Reuse only on explicit request. --template deck.pptx (user names an existing deck as the template) or --reuse-profile x.profile.json (user wants "the same design as before"). Then say what was kept; the novelty check is skipped for reused designs and the original file is never modified. See section 5.
  • Not random. Genes are chosen by weighted, seeded draws from subject-derived priors and history; the same input gives the same profile, a different subject (or a repeated one) gives a different one.
  • Variety with discipline. Composition varies slide to slide (frames, containers, backgrounds, density, alignment, scale) while the type scale, grid, contrast and the profile's geometric language hold the deck together. Do not force variety where a consistent structure helps (e.g. repeated KPI rows in a data report); pin with --pin role=variant.
  • Animation is never faked. Say "animated" only for effects found in the saved file by the read-back; do not claim Morph (not implemented). Do not animate everything: static roles (cover, agenda, references, table, quote, closing) stay static.
  • Facts are never invented. Source fidelity and "Illustrative" labels.
  • Never shrink text to fit. Cut, restructure, or split (> 45 words, > 6 bullets, < 16 pt body).
  • Languages. English LTR; Arabic RTL (mirrored layouts, right-aligned, Arabic-capable fonts forced); bilingual per paragraph.
  • Never claim a similarity score you did not compute and never claim to have compared files that could not be read; novelty.py reports unreadable files.

5. Template reuse (explicit requests only)

  • --template deck.pptx master mode: the deck has a layout with a title placeholder and is 13.333 x 7.5 in. New slides are built inside a copy of that file: its theme, master, placeholders and fonts are kept; cover/section/closing use the template's own layouts; content slides use the template's title placeholder and our body components below it.
  • style mode: the deck draws its look on every slide (single blank layout, other slide sizes are not supported). Palette and typefaces are carried over; layouts are generated and the report says the master could not be reused and why.
  • --reuse-profile deck.profile.json: same genes as the earlier deck (layouts are still planned for the new content).

6. Final procedure

Deliver only after: file opens, validator has zero errors, composition audit passes, novelty check passes (or the report states why it was skipped), rendered slides were actually viewed and fixed, animation counts match the claim. The final message states: output path, slide count, profile name + the reason, fonts, layout families used, audit result, novelty result and what it was compared against, transitions/object animations (counts, method), what was not possible, [source needed] items.

Files are in the skill's install directory (for Claude Code, ~/.claude/skills/premium-animated-presentation/; on Windows %USERPROFILE%\.claude\skills\premium-animated-presentation\); run scripts with that absolute path.

Related Skills