research-group-ppt

name

research-group-ppt

description

Prepare a research-group HTML presentation from local research-progress materials using a template-first workflow. Use when the user asks to make a 课题组组会 PPT, 科研组会汇报, 研究进展汇报, 网页 PPT, 杂志风 PPT, or 瑞士风 PPT. First search local materials for a template PPTX and treat it as the primary visual standard. Only offer built-in guizang-ppt Style A or Style B presets when no template PPTX exists. Preserve experimental data, formulas, units, terminology, figure legends, axes, and scale bars. Use source materials and an existing index.html as content references, rewrite and output a page-by-page outline, then stop and wait for explicit user confirmation before generating the deck.

Research Group PPT

Create a research-group HTML deck by applying a template-first, research-safe workflow around guizang-ppt-skill.

Do not assume Swiss style. This skill is template-first and uses built-in styles only as fallback options.

Non-negotiable gate

Do not generate or edit the final HTML deck before the user confirms the page-by-page outline.

Phase 1 output is only:

1. discovered template and source files;
2. proposed visual standard;
3. rewritten page-by-page outline;
4. questions or assumptions requiring confirmation.

End Phase 1 by asking the user to confirm or revise the outline. Continue to HTML generation only after explicit confirmation such as 确认, 按此生成, or an equivalent instruction.

Defaults

Use these defaults unless the user overrides them:

• Output after outline confirmation: 10-slide HTML deck with sibling images/.
• Chinese font: Microsoft YaHei.
• English and numeric font: Times New Roman.
• Content source: latest *研究进展*.pptx in the current directory by LastWriteTime.
• Content requirements: include research route, element-distribution model, TEM results, VASP results, and next steps when supported by the source materials.
• Images: preserve original content. Do not generate or redraw images without user confirmation.
• Delivery: keep an existing deck intact; write a new sibling output directory unless the user explicitly asks to overwrite.

Read references/format-contract.md before outlining or editing a deck. Read references/outline-format.md before writing the Phase 1 outline. Read references/prompt-template.md only when the user asks how to invoke or customize this skill.

Dependencies

Require the upstream guizang-ppt-skill in one of:

• ~/.claude/skills/guizang-ppt-skill
• ~/.codex/skills/guizang-ppt-skill

Use upstream built-in styles only as fallback options:

Style	Template	Layouts	Themes	Validator
A · Electronic magazine / e-ink	assets/template.html	references/layouts.md	references/themes.md	Manual checks
B · Swiss International Style	assets/template-swiss.html	references/layouts-swiss.md and references/swiss-layout-lock.md	references/themes-swiss.md	scripts/validate-swiss-deck.mjs

Phase 1 · Discover and outline

1. Discover the template first

Run:

powershell -ExecutionPolicy Bypass -File "<SKILL_ROOT>/scripts/find-local-presentation-inputs.ps1" -Directory "<WORKDIR>"

Visual-style priority:

1. Exact 模板.pptx.
2. PPTX filename containing 模板.
3. If multiple template candidates exist, use the newest by LastWriteTime and list the alternatives.
4. If no template PPTX exists, offer the built-in Style A / Style B choices and corresponding theme presets.

When a local template PPTX exists:

• treat it as the visual authority for colors, typography, title hierarchy, spacing, page rhythm, image treatment, headers, footers, and decorative elements;
• do not force Style A, Style B, IKB, or another built-in theme;
• use upstream HTML templates only as implementation scaffolding when helpful;
• preserve the local template's visual identity over upstream preset aesthetics.

2. Locate content references

Run:

powershell -ExecutionPolicy Bypass -File "<SKILL_ROOT>/scripts/find-latest-research-progress.ps1" -Directory "<WORKDIR>"

Use:

• latest research-progress PPTX as the primary factual source;
• other local PPTX, documents, spreadsheets, PDFs, and images as supporting materials when relevant;
• local index.html as an additional content and narrative reference when present.

State which files will be used and their roles.

3. Extract evidence

Extract slide text and inspect original slide previews. Preserve all:

• experimental values and units;
• formulas and professional terminology;
• chart axes, legends, scale bars, annotations, and captions;
• TEM, SEM, optical, mechanical, thermal, DOS, and process evidence when present.

Prefer exporting source PPT slides to images for faithful evidence blocks. Do not redraw source figures by default.

4. Rewrite a page-by-page outline

Use references/outline-format.md.

The outline must:

• contain the proposed page count, default 10;
• include the required sections when supported by source materials: research route, element-distribution model, TEM results, VASP results, and next steps;
• rewrite titles for clarity while preserving facts;
• specify the factual source and proof object for every page;
• specify image handling, including 完整显示 when axes, legends, or scale bars must remain visible;
• state the template PPTX or fallback style used as the visual basis;
• identify unsupported or uncertain claims instead of inventing them.

5. Stop for confirmation

Output the outline and stop. Do not copy templates, create final output directories, generate images, or write final index.html.

Ask:

请确认逐页大纲。回复“确认，按此生成”后，我再继续制作网页 PPT；也可以直接指出需要调整的页码和内容。

Phase 2 · Generate after confirmation

6. Choose implementation basis

If a local template PPTX exists:

• follow its visual grammar;
• select the closest upstream HTML scaffold only as a technical base;
• document any unavoidable differences between PPTX template styling and HTML implementation.

If no local template PPTX exists:

• ask the user to choose Style A or Style B when unspecified;
• then ask for the matching theme preset;
• if the user delegates the decision, state the recommended option before generating.

Fallback presets:

• Style A: 墨水经典 / 靛蓝瓷 / 森林墨 / 牛皮纸 / 沙丘.
• Style B: 克莱因蓝 IKB / 柠檬黄 / 柠檬绿 / 安全橙.

7. Generate the deck

Copy the selected upstream scaffold to the output directory as index.html. Create images/.

Set the font variables in :root unless the user or local template specifies other fonts:

--sans:"Times New Roman","Microsoft YaHei UI","Microsoft YaHei","微软雅黑",serif;
--sans-zh:"Microsoft YaHei UI","Microsoft YaHei","微软雅黑",sans-serif;
--mono:"Times New Roman","Microsoft YaHei UI","Microsoft YaHei","微软雅黑",serif;

For every style:

• use fit-contain for text-dense scientific screenshots;
• avoid cropping axes, legends, units, and scale bars;
• keep image groups at consistent ratios and heights;
• avoid decorative changes that reduce scientific readability.

For fallback Style B additionally:

• use a registered data-layout="Sxx" on every slide;
• bind local images with data-image-slot;
• keep Chinese top headings left-aligned unless a registered split layout requires otherwise.

8. Validate

Run:

powershell -ExecutionPolicy Bypass -File "<SKILL_ROOT>/scripts/validate-research-deck.ps1" -Deck "<OUTPUT_DIR>/index.html" -Style "<A|B>"

For a template-first deck, pass the implementation scaffold style while visually checking against the local PPTX template.

Verify:

• expected rendered slide count, default 10;
• no [必填] or [选填];
• every referenced local image exists;
• no AI-generated or redrawn figure was introduced without confirmation.

9. Preview every slide

Use the Browser plugin for the local HTML deck when a controllable in-app browser pane is available.

If the in-app browser cannot be controlled, use local Edge headless screenshots as a fallback and create a contact sheet for review. Inspect:

• similarity to the local PPTX template when one exists;
• title wrapping;
• readable font size;
• image sharpness;
• uncropped axes, legends, and scale bars;
• bottom navigation safety area;
• static mode with B;
• ESC overview.

Delete QA screenshots and temporary extraction files before delivery.

Image generation gate

Do not call image generation by default. If generated illustrations or screenshot redesign would materially improve a page:

1. list the proposed pages, purpose, layout slot or ratio;
2. ask the user for confirmation;
3. generate only after approval.

Delivery

Provide a clickable link to index.html, name the content source, report the template or fallback style used, report validation status, and state whether visual inspection used the in-app browser or Edge fallback.