academic-presentation

name	academic-presentation
description	Use when creating, revising, or converting academic presentations, paper slides, lab-meeting decks, conference talks, research proposals, midterm reports, thesis defenses, scientific mechanism figures, technical roadmaps, or flat diagram images that must become editable SVG or PowerPoint objects.

Academic Presentation

Core Contract

Create source-grounded academic decks and figures whose claims, citations, numbers, timing, and editability can be audited. Treat input sources and templates as read-only. Build text, shapes, connectors, tables, charts, and grouped vectors as native objects whenever possible.

Use this package's references/, scripts/, and assets/ directly; do not require a PowerPoint Master or another Skill at runtime. Use the current execution environment's Image 2 capability only when the routed workflow calls for generated or reconstructed imagery. Report if that capability is unavailable.

Route the Request

Request	Route
Full academic deck	Read academic-content.md, slide-workflow.md, editable-pptx.md, and quality-checks.md
Abstract/text to mechanism figure	Read image-to-editable.md, editable-pptx.md, and quality-checks.md
Existing image to editable SVG/PPTX	Read image-to-editable.md, editable-pptx.md, and quality-checks.md
Revise an existing academic PPTX	Read academic-content.md, editable-pptx.md, and quality-checks.md

Resolve every filename in the table under references/.

Required Inputs and Defaults

Collect the inputs and controls applicable to the selected route. For a full deck, collect sources, scene, audience, time or pages, output formats, template or screenshot, language, aspect, resolution, figure style, fidelity, recoloring, and all-vector preference. For a revision, also collect the original PPTX, exact change scope, and authorization for exporter-based rebuilding. For a standalone figure, collect the source text or image, requested PNG/SVG/PPTX formats, and fidelity/editability requirements. Record material assumptions instead of hiding them.

For a full deck, default to 16:9, auto-detect language, render previews at 1080p, use literal fidelity for conversion, and use adapted fidelity for inspiration or original work. Infer scene only when the request or sources make it unambiguous; otherwise ask before outlining. If both pages and time are absent and venue/context cannot supply them reliably, ask before outlining; in non-interactive execution, record pending intake/outline information and stop before rendering. Explicit choices override defaults. See references/slide-workflow.md for full-deck control semantics; other routes follow only the references loaded by their routing-table row.

Shared Workflow

Common intake and provenance

1. Inventory applicable inputs and controls, copy or index sources without modifying originals, and create stable source IDs.
2. Select one primary route. Whenever any deck needs figure generation or reconstruction, also load the applicable figure route, whether or not the figure is delivered separately.
3. Read the references named by the selected routing-table row. Do not impose a workflow from a reference that route did not load.

Full academic deck

1. Build source-index.json; extract claims and evidence; then draft a claim-led outline with timing status using the scene priorities in references/academic-content.md.
2. Record approval_state and stop while approval is pending when the Hard Gates apply.
3. After approval when required, write editable per-slide YAML specs, create source-grounded visuals, and deterministically assemble root-level deck-spec.json as the exporter input.
4. Export previews, PPTX, PDF, notes, and script; run content, citation, visual, and editability QA; then run scripts/validate_pptx.py on the final PPTX.

Revise an existing academic PPTX

1. Treat the original PPTX/POTX as a read-only style and layout source. The bundled exporter supports only rebuild revision: after explicit authorization, create root-level deck-spec.json and rebuild while retaining supported dimensions, theme, and layout choices.
2. Do not promise object identity or full preservation of animations, macros, embedded objects, or unknown OOXML. If the user requires in-place or object-preserving patching, report that it is unsupported and provide a change plan or request authorization to rebuild.
3. Do not require a complete new-deck outline unless the rebuild is complex or affects more than 10 slides; then create a revision outline and stop rendering while approval is pending.
4. QA and validate an authorized rebuilt deck before describing it as revised.

Standalone figure: text-to-figure or existing-image reconstruction

1. Build a figure spec and source/inventory record, then generate or reconstruct at the requested fidelity using native objects first.
2. For PNG/SVG-only delivery, run relevant QA and export without a deck spec. For PPTX, create standalone-figures/<figure-id>/deck-spec.json with one slide of native or svg-group elements, then invoke the same exporter and validator.
3. A standalone figure never requires a full-deck outline, approval record, slide YAML, or root-level full-deck spec.

Hard Gates

• Never fabricate scientific evidence.
• Never deliver a full-slide image as an editable deck.
• For full-deck or revision outline approval, track state as not-required, pending, or approved; never render while it is pending. Standalone figures have no deck-approval record.
• For a full academic deck that is complex or has more than 10 slides, obtain explicit outline approval before rendering. For a revision, apply this gate when the requested changes are complex or affect more than 10 slides; standalone figures do not use a deck-outline gate.
• For literal reconstruction, preserve exact text and symbols.
• Use native objects first; permit image fallback only at the minimum semantic unit and disclose each fallback.
• Never describe an exporter rebuild as an in-place or object-preserving PPTX patch.
• Run scripts/validate_pptx.py on every delivered PPTX before claiming completion.
• If Image 2 is unavailable, report the limitation; never silently substitute a different workflow.
• Keep original sources and templates unchanged.

Deliverables

Deliver only artifacts applicable to the selected route. For a full deck, deliver the source index, outline, applicable approval record, per-slide YAML specs, deck-spec.json, requested PPTX/PDF, previews, speaker notes, talk script, standalone figures, and QA reports. Record approval as not-required, pending, or approved; never claim an outline is approved without explicit approval. If intake or approval remains pending, deliver the pending record and outline material, not a final render.

For a revision, deliver a change plan and limitation report; after rebuild authorization, also deliver root-level deck-spec.json, the rebuilt PPTX, applicable approval record, and QA reports. For a standalone figure, deliver its spec/inventory, requested PNG/SVG/PPTX, relevant QA, and the nested one-slide deck-spec.json only when PPTX is requested. Identify assumptions, unresolved items, approximate screenshot inheritance, and minimum-semantic-unit raster fallbacks. Use the references/slide-workflow.md runtime tree only for a full academic deck.

Resource Routing

Resource	Use
references/academic-content.md	Evidence structure, scene narratives, action titles, citations, timing, and content QA
references/slide-workflow.md	Full-deck inputs, controls, approval, slide YAML, exporter JSON, and output layout
references/image-to-editable.md	Text-to-figure and image-to-editable reconstruction
references/editable-pptx.md	Native PowerPoint object construction and editable SVG/PPTX assembly
references/quality-checks.md	Rendering, visual, citation, and editability acceptance checks
scripts/validate_pptx.py	Mandatory final structural validation
assets/	Bundled default theme and reusable package assets when no user template is supplied

Use only the resources named by the selected route. scripts/validate_pptx.py is mandatory for every delivered PPTX and is not required for a standalone PNG/SVG-only delivery.