Release PPT workflow 0.7.2 with text and container constraints
This commit is contained in:
@@ -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.7.1"
|
||||
version: "0.7.2"
|
||||
---
|
||||
|
||||
# PPT Template Workflow
|
||||
@@ -13,6 +13,8 @@ Use **template → theme → layout** as versioned inputs. A catalog can contain
|
||||
|
||||
Read [production rules](references/production-rules.md) for the whole workflow. Preserve source meaning, provenance, real data, implementation claims and rebuildable inputs as requirements; use its planning and design methods as recommendations. Reuse settled choices and review at the authorized granularity. Record justified design exceptions without adding approval gates.
|
||||
|
||||
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.
|
||||
|
||||
## Select and review
|
||||
|
||||
Read the supplied catalog or manifest with `scripts/template_ref.py`. For a foundation project, start with its README consumer links. If the task needs a template and no source is specified, ask once for the source instead of guessing a global library.
|
||||
|
||||
Reference in New Issue
Block a user