admin/Templated-PPT-Master
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Integrate confirmed report workflow and review inputs (0.9.0)

Browse Source
This commit is contained in:
Commilitia
2026-10-20 10:25:03 +08:00
parent 3b7de84c49
commit 4729693a9e
9 changed files with 108 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+6 -2
View File
@@ -2,7 +2,7 @@
name: ppt-template-workflow
description: Create and revise template-based editable PPTX decks, design page mockups and materials, reconstruct visual pages into native objects, and maintain portable source projects. Select one external template and theme at a time; includes its own native compiler and workflows without requiring another installed Skill.
metadata:
version: "0.8.0"
version: "0.9.0"
---
# PPT Template Workflow
@@ -15,6 +15,8 @@ Read [production rules](references/production-rules.md) for production and conte
Report logic, chapter relationships and page content allocation are maintained separately by the optional `report-structure` Skill, including its user examples and derived rules. Consume an existing content plan through [content handoff](references/content-handoff.md): identify what the audience should understand, necessary premises, progression within the page, key reasoning steps and the visual association between conclusions and evidence. This Skill remains independently usable: establish a minimal current-page brief when none is provided, and return consequential content changes for review at the user's agreed granularity. It does not maintain a second narrative rule or example library.
For a structure-workflow handoff, receive the page-explanation PDF together with its editable page source. Take slide text, formulas and required visual descriptions from that source, keeping speaker analysis separate; PDF text extraction is not a prerequisite. Reuse the user's confirmed review assignments, post-revision review, page/block production mode, ImageGen scope and alternatives through [execution and review](references/execution-and-review.md). Confirm only consequential choices still unresolved, together before dependent work; do not silently replace a declined tool or Agent arrangement.
For every authored or reconstructed page, apply the required [text and container rules](references/text-and-containers.md): prefer one native text frame per paragraph; any necessary fragments must remain one logical text block with unified content and layout. Keep substantive explanations out of small muted notes, distinguish different text roles by size/weight/color, and use one shared internal layout implementation per container type/variant. Authors supply content and whole-container bounds, never instance-specific child positions.
Paragraphs must also obey punctuation prohibitions at line starts/ends and must never leave a line with only one substantive character, alone or surrounded by punctuation. Check every rendered line, including the final line, and reflow the whole paragraph without breaking its logical identity. The shared [paragraph helper](scripts/paragraph_layout.py) supports measured plain-text wrapping; it does not replace actual render checks.
@@ -45,7 +47,7 @@ Keep the user's working style above downstream defaults. For `interactive-page`,
If the manifest declares `page_library`, read [page examples](references/page-library.md). Use `scripts/page_library.py list` to find compositions, then `inspect --entry <id> --theme <id> --for-use` to verify a compatible reference and its source/preview hashes. Read its rationale, method and actual preview before adapting the source. Examples do not change the active template, palette, layout roster or review sequence. Templates without a library remain supported.
- **Native:** read [native authoring](references/native-authoring.md). Author the current SVG page against its declared layout and compile it with `scripts/native_export.py`, retaining Master, Layout and placeholder identities. Avoid slide-local copies that cover inherited objects.
- **Page mockups and materials:** read [visual design and materials](references/visual-design.md). Use the host image-generation tool for requested raster mockups, illustrations and image edits; keep exact supplied evidence and identity assets separate from style references. Use existing vectors and the bundled `scripts/paint_asset.py` for declared SVG paint changes.
- **Page mockups and materials:** read [visual design and materials](references/visual-design.md). Under the confirmed ImageGen choice, use actual visuals from the selected template/theme to make a rough current-page layout for grouping, hierarchy and reading-order feedback, then implement the authorized page. Reuse confirmed preferences within their recorded scope. Use the host image-generation tool for requested raster mockups, illustrations and image edits; keep exact supplied evidence and identity assets separate from style references. Use existing vectors and the bundled `scripts/paint_asset.py` for declared SVG paint changes.
- **Image-rebuild:** read [object reconstruction](references/object-reconstruction.md). Inventory the current page, separate background and foreground sources, then author native text and structural objects in the selected SVG layout. Use source material or host image editing where needed; an image assembly is not editable completion.
Read [authoring handoff](references/authoring-handoff.md) for shared page inputs, icon roles and theme changes. Use [PowerPoint checks](references/powerpoint-checks.md) when application opening, rendering or actual editing evidence is needed. If a required host capability is unavailable, finish independent work and name that specific evidence gap; do not substitute an old export or change the selected backend silently.
@@ -74,4 +76,6 @@ Prepare useful page-library contributions as sanitized candidates with rationale
Check the rendered current page and actual editable objects. Distinguish editable text/shapes/tables/charts/formulas, picture exceptions and inherited placeholders. Confirm native structure separately from appearance. Read [runtime and provenance](references/runtime-and-provenance.md) for dependencies, bundled compiler integrity, supported source boundaries and destination font checks.
Follow the confirmed post-revision review assignment. For independent review, use a reviewer who did not edit that portion and provide current source, necessary evidence and criteria without author self-assessment, expected verdicts or leading explanations. The reviewer judges the current version before comparing old findings; substantive later changes need the agreed review of their affected scope. Label main-Agent self-checks and skipped reviews accurately. See [review inputs](references/execution-and-review.md#review-after-revision).
Deliver the PPTX with its selection record and a compact account of template version, theme, object exceptions, structural evidence, rendering and application checks. XML, screenshots and successful export alone do not prove application editing or projection acceptance.