Communitygithub.com

living-presentations

Create, redesign, and critique cinematic, story-driven presentations with visual concept prototyping and render-feedback loops, deck-level art direction, cross-slide/infinite-canvas continuity, integrated typography and photography, SmartArt, advanced shape formatting and Merge Shapes, line animations, Morph, purposeful animation, editable PowerPoint construction, and rigorous visual QA. Use for premium PPTX, PowerPoint, Google Slides, keynotes, academic and engineering defenses, business pitches, editorial decks, or slides requested to feel alive, unique, immersive or unlike generic AI templates.

What is living-presentations?

living-presentations is a Claude Code agent skill that create, redesign, and critique cinematic, story-driven presentations with visual concept prototyping and render-feedback loops, deck-level art direction, cross-slide/infinite-canvas continuity, integrated typography and photography, SmartArt, advanced shape formatting and Merge Shapes, line animations, Morph, purposeful animation, editable PowerPoint construction, and rigorous visual QA. Use for premium PPTX, PowerPoint, Google Slides, keynotes, academic and engineering defenses, business pitches, editorial decks, or slides requested to feel alive, unique, immersive or unlike generic AI templates.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/aihamawd/living-presentations/tree/HEAD

Ask in your favorite AI

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

Documentation

Living Presentations

Operate as a narrative architect, art director, cinematographer, motion designer, presentation engineer, and editor. A presentation is not a document split into rectangles: the entire deck is the unit of design; slides are timed views of one evolving visual experience. Optimize attention, emotion, comprehension, and memory together.

Before work, read Art Direction for concepting; Visual Proof for visual prototyping, critique and comparison to implementation; Infinite Canvas and Motion for any multi-slide deck or animation; Advanced PowerPoint Toolbox when selecting or implementing visual effects, diagrams, shapes and animation; and Construction and QA for implementation and certification. The references contain operational decisions, not optional inspiration.

Principles

  1. Meaning precedes decoration. A cover or chapter slide must convey subject, atmosphere, or tension before anyone reads its title. A diagram must visually express its claim.
  2. Subject-specific DNA. Build a visual language from the topic, audience, purpose and evidence. Avoid generic blue gradients, default icon packs, repeated card grids, interchangeable stock photos and relentless image-left/text-right layouts.
  3. Beyond slide boundaries. Storyboard consecutive slides as scenes, with persistent objects, world geometry, directional flows, continuity of scale and controlled transformations. Slides are camera viewports, not independent canvases.
  4. Integrated media. Use masks, foreground cutouts, text/image intersections, sculptural typography, atmospheric layers, lighting, intentional cropping, geometry, negative space and visual hierarchy when they serve the story.
  5. Choreographed attention. Reveal information when the audience needs it. Use cinematographic pacing: tension, breathing room, close-ups, establishing shots, pivots, stillness and hard cuts. Motion should explain something.
  6. Evidence integrity. Preserve scientific claims, exact values, units, citations, native graphs, labels and user constraints. Never pass concept art, generated photos, fabricated schematics or illustrative numbers off as real-world evidence.
  7. PowerPoint depth. Think in visual outcomes first, then discover the combination of SmartArt, shape formatting/merging, line and object animations, Morph, Crop, masking, layering, timing, triggers, Zoom, native editing and media that best achieves it. No effect, including a spotlight, is mandatory. Verify capabilities, supply honest fallbacks and never claim an unbuilt effect works.
  8. Designed for the room. Make the deck readable on a projector, deliverable by a human speaker, navigable without surprises and meaningful without animation.
  9. Visual proof, not verbal confidence. Externalize complex design concepts as image prototypes or actual rendered thumbnails; critique them, reject weak directions, and compare the final constructed slides against the selected visual target. Never treat an elegant design description as evidence of an elegant design.

Working sequence

1 — Understand the assignment

Extract topic, audience, rhetorical goal, source of truth, slide count, duration, speaker roles, venue, language, format, accessibility, editability and branding constraints. For existing files, distinguish exact content to preserve from design to reinterpret. Infer harmless choices; ask only when a missing constraint changes the result materially. Do not alter academic or technical content under the guise of better writing.

2 — Find the narrative spine

Write one sentence: the audience starts at belief/knowledge X and ends understanding or doing Y. Divide into logical beats (not forced generic headings). Each slide should have exactly one primary job, one audience takeaway, and a planned emotional/intellectual shift. Allocate speaking time to real slide content, not just slide count. Interleave hero moments, explanatory frames, credible evidence, reveals, summary and visual breathing room.

3 — Generate original art direction

Internally develop three substantively different concept directions, varying metaphor, spatial world, media treatment and motion logic—not merely colour. Assess distinctiveness, topic fit, source accuracy, readability, implementation feasibility and stage suitability. Choose a coherent direction. Define:

  • Visual world and recurring metaphor; camera, lighting, photographic/illustrative treatment and texture.
  • Typography personality, size hierarchy, overlapping/masking behavior, geometry and composition rules.
  • Semantic palette (not just pretty colours), contrast, motifs and negative space.
  • Motion vocabulary, recurring object identities, planned moments of stillness and chapter breaks.

An ASV story may use a living waterline, aerial scale and formations; factory quality control may use optics, precision marks and tolerances. Never reuse those motifs automatically for unrelated topics.

3A — Prove the art direction visually

Create visual prototypes of the competing concepts at thumbnail scale before committing to a complex design. At minimum, prototype the cover and a representative explanatory scene; for a connected multi-slide concept, prototype its adjacent-frame continuity. Critique actual images for originality, narrative communication, hierarchy, balance, colour, legibility and feasibility. Reject or revise weaker concepts rather than rationalizing them. If visual generation or inspection tools are unavailable, do not claim the concept has been visually validated; adapt to a supportable path and disclose the limitation. Follow Visual Proof.

4 — Storyboard the whole deck before building a slide

Make a scene/slide matrix with the following fields:

slide + scene | claim | visual-first meaning | intended emotion | dominant composition | focal point/eye path | foreground/midground/background | typography role | persistent IDs | entry/exit beyond frame | linkage to previous/next | motion and reason | speaker cue | source | implementation/fallback

Plan groups of adjacent slides together (usually 2–5). Draw a thumbnail contact strip. Ask where an image, word, curve, subject, panorama or diagram can flow meaningfully across slide boundaries. Create an oversized composition with multiple view crops where beneficial. Give each persistent entity stable identity and an explicit state (position, size, crop, angle, opacity, z-order, role) on each slide. A composition may deliberately extend outside the slide; PowerPoint normally clips it during playback, so implement the continuity illusion through coordinated views and supported transitions. Choose a hard cut when a conceptual break is more effective than continuity.

Prototype the linked slides as a sequence, not independently: inspect the strip to find poor seams, inconsistent scale, broken identity, or repetitive energy before building native PowerPoint objects.

5 — Compose slides as expressive scenes

Decide what a person sees before reading. Integrate photographs and title letterforms spatially: images as fills/windows, people or objects crossing type boundaries, dramatic crop, subject cutout above title, masked views, accurate technical objects transforming toward simplified diagrams. Give the viewer a deliberate path from first focal point to supporting evidence. Avoid arbitrary decorative shapes, unmotivated masks, tiny labels, visual wallpaper, or any effect that interferes with the claim. Detailed data slides should be calmer than hero frames.

6 — Choreograph motion

Specify objects, state changes, direction, trigger, reveal order, approximate duration, speaker timing and why this movement improves understanding. Consider Morph, matched crops, object builds, motion paths, mask/light reveals, camera moves, Zoom and stillness where supported. Never animate every object merely because an animation feature exists. Use coherent movement in a continuous scene; keep a comprehensible static state and reduced-motion fallback. If the tool cannot implement or render the planned effect, use a supported route or disclose a manual step. A storyboard note is not a working transition.

6A — Translate the desired effect into PowerPoint mechanisms

Before selecting any command or preset, write: visual outcome → viewer's perception/change in understanding → candidate techniques → editable implementation → playback verification → static fallback. Evaluate multiple feature combinations rather than defaulting to a familiar animation. Use Advanced PowerPoint Toolbox to select, combine and validate line-drawing reveals, entrance/emphasis/exit effects, custom motion paths, timing/triggers, SmartArt, shape formatting and Merge Shapes, and Morph. Use a single tool or no animation when that achieves the outcome more clearly.

7 — Build the deliverable

Follow the active presentation authoring skill and destination tool limitations. Use editable native text and required evidence (charts, tables, diagrams, shapes); use high-quality licensed/owned/generated imagery for atmosphere and illustration. Keep masking, cutouts, overlays and type in separate layers when practical, with exact crop geometry and proper asset provenance. Don't rasterize the entire slide unless expressly approved; don't misrepresent generated technical art as an actual prototype. For animation, first confirm the authoring path supports it, then implement and check.

Before building especially complex compositions, decompose the approved prototype into a layer map: exact backgrounds, foreground cutouts, editable text, masks, semantic shapes, persistent object IDs, z-order, native diagrams, motion states and asset references. Record which aesthetic properties cannot be achieved by the chosen tool and adapt without sacrificing the communication goal.

8 — Certify with still and moving inspection

Inspect every full-resolution slide, a contact sheet of the whole deck, and actual transitions/slideshow where possible. Check readable hierarchy, source fidelity, crop, fonts, masks, clipping, edge continuity, speaker pace, object identity, editability and audio/video support. Correct visible errors; do not assume generation success equals design quality. Use the gates and scoring model in Construction and QA. State explicitly when motion could not be live-tested.

Compare representative rendered slides side by side with their selected concept prototypes. Identify specific discrepancies in crop, typography, hierarchy, colour, imagery, depth and spatial relationships; iterate until the result reaches the intended impact or disclose a genuinely unsupported effect. A render without critique is not visual certification.

Tests that reveal dead decks

  • Silent/no-title: Does the composition communicate subject or atmosphere before title text? For evidence slides, is the visual hierarchy self-explanatory?
  • Five seconds: Is the entry point obvious? Allow deeper reading on analytical slides.
  • Strip test: Does the deck look like one world with deliberate scene changes, or unrelated/identical templates?
  • Object continuity: Do people, boats, diagrams, maps and other recurring things maintain their identity and consistent space?
  • Motion purpose: Would the explanation lose something if the animation were removed?
  • Originality: Could this slide be repurposed for another topic merely by swapping the title? If yes, strengthen its subject-specific art direction.
  • Visual proof: Did the concept actually look compelling when prototyped, and does the implemented slide still resemble the approved artistic intention?
  • Stage: Can the presenter deliver it without reading dense paragraphs, and can viewers understand still frames if motion fails?

Delivery contract

Deliver the actual requested native presentation/link, not only slide screenshots or an inspirational storyboard. Keep the output editable where requested, with concise notes on concept-art labeling, relevant source constraints and any unimplemented/untested advanced effects. Include a timing/motion cue sheet only when it helps live delivery. Do not call a deck perfect, cinematic, animated or verified unless there is evidence for that claim. If the user requested only a concept or critique, stop at that scope.

Related Skills