fangyuanopus/literature-report-ppt-builder/academic-slide-minimalist

Academic Slide Minimalist

Non-Bypassable Execution Gates

These gates override every other workflow section in this skill. Run them before any slide-generation or PPTX-packaging action.

Gate A: Image2 availability gate

Before creating final slide images, sample redesigned pages, or a PPTX, explicitly determine whether the current environment has an Image2-style native full-slide image-generation backend.

The backend counts as available only if all are true:

• it can generate one complete 16:9 academic slide image per page;
• the full-slide image can include title, navigation, real source figure crops, annotations, labels, notes, and page number inside the image;
• it can preserve scientific source crops faithfully without redrawing, restyling, or semantically changing them;
• its outputs can be saved as accepted final slide images and then mechanically packaged into an image-only PPTX.

If availability is unavailable, unclear, unconfirmed, or blocked by the current environment, do not create or deliver an Image2-only PPTX. First explain the boundary, then ask whether the user accepts a lower-fidelity fallback PPTX route. Until the user explicitly accepts that fallback, deliver only the valid non-image artifacts: paper reading outputs, adaptive navigation, deck_order_map.md, figure_source_manifest.md, page_briefs.md, Image2 prompts, and assembly notes.

Use this boundary statement when Image2 is unavailable:

当前环境未确认可用 Image2-style 全页幻灯片生成后端，因此无法交付严格 Image2-only 高保真 PPTX。请选择：
A. 只交付可用于后续 Image2 生成的页面方案、figure manifest、page briefs、prompts 与 assembly notes；
B. 接受降级版 PPTX：使用现有 `assets/sample-literature-report.pptx` 的模板、版式节奏和红黑灰学术风格生成可编辑 fallback PPTX；它不是 Image2-only 高保真交付，也不能声称通过 Image2 manifest 与 image-only 验证。

Gate B: Image2 manifest gate

Do not package a PPTX unless image2_manifest.json exists and records every final slide image. The manifest must include:

{
  "image2_backend_confirmed": true,
  "slides": [
    {
      "slide_no": 1,
      "final_image": "final_images/slide_001.png",
      "generation_route": "image2_full_slide",
      "accepted": true,
      "source_figures": []
    }
  ]
}

Every delivered Image2-only slide must have generation_route: "image2_full_slide" and accepted: true. If the manifest is missing, incomplete, or says any page used another route, do not deliver an Image2-only PPTX.

Gate C: PPTX validation gate

Before delivering a PPTX, run scripts/validate_image_only_pptx.py on the assembled file. If a manifest exists, validate with --manifest image2_manifest.json. Delivery is allowed only when the validator passes.

A passing PPTX must have exactly one full-slide image per slide and no editable text boxes, shapes, charts, tables, SmartArt, icons, or extra PowerPoint annotations.

Gate D: mandatory delivery statement

When delivering a PPTX, include this factual checklist in the final response:

Image2 backend used: yes
Full-slide images generated: yes
PPTX assembly mode: one full-slide image per slide
Editable slide elements: none
Source scientific visuals: real paper/SI/user-provided figures only
Validation completed: yes

If any line is not true, do not deliver the Image2-only PPTX.

Gate E: explicit fallback consent gate

Fallback PPTX creation is allowed only after all of these are true:

• Image2-style full-slide generation is unavailable, unclear, unconfirmed, or blocked;
• the user has been shown the boundary statement above;
• the user explicitly chooses the fallback route or otherwise clearly states that a lower-fidelity PPTX is acceptable;
• the fallback deck uses the bundled assets/sample-literature-report.pptx through a template-following workflow: inspect the sample deck, map every output slide to a source slide, duplicate the mapped slides, then edit inherited objects rather than drawing a parallel layout;
• the fallback deck is grounded in the current main paper, SI, or user-provided source figures; do not use mock figures, decorative substitutes, or scientific content copied from the sample deck;
• the fallback deck passes a render-based layout QA pass with no unintended overlaps, no clipped text, and no sparse pages that use only a small fraction of the slide canvas;
• the fallback deck has no unused template placeholders or leftover shapes occupying figure/text space;
• the fallback navigation follows the sample deck's quiet academic style rather than generic oversized button tabs;
• the final response and file names clearly distinguish the fallback deck from the authoritative Image2-only deck.

A fallback PPTX must not be named or described as final_presentation.pptx unless the user explicitly asks for that filename. Prefer names such as:

fallback_presentation.pptx
editable_fallback_presentation.pptx

When delivering a fallback PPTX, include this factual checklist instead of the Image2-only checklist:

Image2 backend used: no
Delivery mode: fallback PPTX accepted by user
Image2-only validation: not applicable
Scientific visuals: real paper/SI/user-provided figures only
Editable or code-rendered elements may exist: yes
Template source: assets/sample-literature-report.pptx
Render/layout QA completed: yes

Never imply that the fallback PPTX satisfies Gates B-D. If the user does not accept fallback output, continue with the non-image planning artifacts only.

Gate F: fallback template gate

When producing a fallback PPTX, use the bundled assets/sample-literature-report.pptx as the required template source. Preserve its 16:9 format, red-black-gray academic tone, title hierarchy, navigation rhythm, figure/caption treatment, and page-number/footer habits as much as the fallback tooling allows.

The fallback deck may be editable and may contain PowerPoint text boxes, shapes, and normal picture objects, but it must not be a hand-redrawn imitation of the template. Use a strict template-following workflow:

1. inspect all slides in assets/sample-literature-report.pptx;
2. use references/sample-template-slot-manifest.json as the bundled template slot reference, or regenerate it with scripts/extract_template_slot_manifest.py if the sample PPTX changes;
3. choose a source slide for every output slide;
4. create a fallback_edit_plan.json or template-frame-map.json that lists each source slide and explicit edit targets;
5. duplicate the mapped source slides into a starter deck;
6. prepare every real source figure with scripts/prepare_fallback_figure.py or an equivalent deterministic crop step before insertion, and record prepared_figure_manifest.json;
7. edit inherited text, image, table, and placeholder objects in place while preserving their original position, size, typography, crop, and frame treatment;
8. replace sample scientific content only with current paper/SI/user-provided content;
9. render the result and check overlap, clipping, sparse layout, placeholder leftovers, off-center/margin-dominated figures, and inherited-template overflow.

Use scripts/draft_fallback_edit_plan.py to create a first-pass fallback_edit_plan.json from structured slide briefs when no hand-authored plan exists. Then use scripts/build_fallback_template_pptx.py for fallback construction when possible. The builder accepts the edit plan, applies inherited slot edits from references/sample-template-slot-manifest.json, prepares source figures, emits prepared_figure_manifest.json, and writes a build report with overflow, ellipsis, untouched-slot, and image-preparation warnings. If this builder reports status: "needs_review", fix the plan/content before delivery.

Fallback image placement must be figure-aware, not a rigid slot fill. The draft plan should profile each real paper figure or table by aspect ratio, density, and layout hint. When a wide table, wide plot, or dense multi-panel figure does not fit a single inherited image slot, the edit plan may use fit_strategy: "adaptive_contain" and frame_scope: "all_image_slots" to merge inherited image slots into one larger figure region. This is allowed only inside the mapped template slide's inherited image area and must not redraw the page from scratch, stretch the scientific image, or crop away scientific content.

For literature-report fallback decks, every content slide should include at least one real paper/SI/user-provided scientific figure, table, or source crop unless it is a true cover, ending, section divider, or explicitly documented logic-only transition. Do not let background, method, result, application, or summary pages become generic text-only slides when relevant real figures or tables are available.

Do not build fallback pages with a fresh freeform layout engine, generic card grid, oversized UI navigation, or new PowerPoint objects over the copied template when an inherited source object should be edited instead. If the tooling cannot identify editable targets or cleanly replace inherited objects, stop with planning artifacts instead of delivering a loosely redrawn deck.

Never copy the sample deck's scientific content into a new paper deck. Treat assets/sample-literature-report.pptx as a template/style source only; all scientific figures, claims, captions, and conclusions must come from the current paper, SI, or user-provided material.

Read references/sample-template-intro.md, references/fallback-template-pptx.md, references/fallback-template-edit-spec.md, and references/sample-template-slot-manifest.json before creating any fallback PPTX.

The fallback workflow should mirror the useful contract of gorden-ppt-skill: use slot IDs or explicit object addresses, preserve template typography and same-level font sizes, respect capacity hints, rewrite overly long text instead of shrinking individual boxes, and keep every output slide traceable to a source template slide.

Core Mission

Create academic literature-report PPTs that are clear before they are beautiful.

The default target is a complete Chinese academic presentation deck that follows the user's sample deck rhythm while adapting to the current paper's argument.

Use the sample PPT as a visual and rhythm reference, not as a fixed set of section names. Derive the actual navigation labels and page order from the paper's domain, evidence chain, and story structure. A simple paper can use a default rhythm such as basic information, background, research idea, results, summary, and closing; a result-heavy paper should split results into meaningful sections such as design strategy, performance validation, structure evidence, mechanism explanation, application validation, or limitations.

When the user says to follow their sample PPT, do not invent a generic commercial deck and do not hard-code one universal navigation bar. Preserve the sample deck's navigation style, page rhythm, academic tone, and restrained red-black-gray visual language, while adapting section names to the current paper. Use references/sample-deck-rhythm.md, references/adaptive-navigation.md, and, when needed, the bundled assets/sample-literature-report.pptx as style references only.

Image2-Only Route Lock

This skill is an Image2-style full-slide academic deck workflow, not a code-rendered slide engine and not an editable PowerPoint layout workflow.

For any final slide page image, redesigned page, sample page, full-deck page, or delivered PPTX:

1. Image2-style native full-slide generation is the only allowed visual generation route.
2. Each slide must be generated as one complete 16:9 full-slide image.
3. The generated image itself must already contain the title, navigation, real source figure crops, annotations, labels, notes, and page number.
4. A final PPTX, when delivered, is only a mechanical container for those accepted full-slide images.
5. Each PPT slide must contain exactly one full-slide image and no editable slide objects.