Preserve approved mockups with controlled adjustments and recolorable assets (0.9.4)

This commit is contained in:
2026-10-31 20:17:08 +08:00
parent 25be7ebb86
commit 36caa4c915
15 changed files with 100 additions and 33 deletions
+5 -1
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.9.3"
version: "0.9.4"
---
# PPT Template Workflow
@@ -56,6 +56,10 @@ Read [authoring handoff](references/authoring-handoff.md) for shared page inputs
Once the user confirms a page mockup, [reconstruct it faithfully](references/visual-design.md#approved-mockup-fidelity). Preserve its content, figures, graphics and relationship-bearing shapes, including connectors and grouping boundaries. Make necessary quality repairs while retaining the accepted meaning, composition and relationships; do not silently simplify, omit elements or treat difficult objects as dispensable decoration.
For that approved reconstruction, [controlled content-area adjustments](references/visual-design.md#controlled-adjustments-for-approved-mockups) allow necessary font-size, fit and alignment repairs through project-owned shared styles/recipes. Preserve the approved relative positions, visualization forms, icon identities and text styling; this allowance is not permission to redesign them. Prefer integers or consistent fixed-step values in explicit units; retain fixed page UI and locked structures. After each such adjustment, check overflow inside text frames/containers and beyond the page, including actual glyphs, formulas, strokes, clipping and occlusion. Repair source, rebuild and inspect the new render before completion.
When an approved element is impractical to express faithfully with native components or SVG, [use ImageGen for that element](references/visual-design.md#elements-that-need-imagegen), with the approved sample as reference. Preserve its appearance and relationships. Deliver generated material with a transparent background and one color or a few clearly separated color roles, retaining alpha masks/layers and declared adjustable/fixed bindings for reliable recoloring. Keep it as an independent project asset and disclose its picture editability. Do not replace it with a simpler visualization/icon or flatten the whole page. Exact evidence/identity originals remain authoritative.
For data graphics read [charts](references/charts.md); for native tables, metrics, timelines and explicit linear flows read [components](references/components.md). Their generators return data-bound component groups to compose inside an existing template slot, retaining its UI/Master/Layout. Keep sources and synchronize native payloads and visible fallback. New icons follow [icon production](references/icon-production.md) regardless of whether drawn, generated or externally sourced.
Apply the [visual design boundary](references/visual-design.md#page-composition-and-html-boundary) to every route: do not lay out report pages with HTML/DOM/CSS or convert such layouts through screenshots, printing or other formats. HTML may host a JavaScript visualization itself and its necessary runtime container; surrounding page text and layout use the permitted native/SVG route.