Files
Templated-PPT-Master/references/authoring-handoff.md
T

5.5 KiB

Authoring handoff

Give every authoring step the same selected template ID/version, theme, layout, exported style, source specification, content and notes, strict input assets, approved visual references, editability policy and input hashes. These are local project inputs; reading another installed Skill is unnecessary.

For the current page, decide the message and evidence first, then compose the page within the selected layout. A mockup image establishes visual direction; the editable deliverable is authored from independent objects. Reuse approved decisions and the user's page-by-page workflow. A known page count does not authorize creating the remaining pages in bulk.

Native compilation uses the separate template's complete workspace roster, retaining Master, Layout and placeholder links. The final source page identifies its intended layout with data-pptx-layout. A whole-slide picture, selectable SVG picture or generic text reconstruction does not establish those links by itself. See native authoring and object reconstruction.

Native formulas, tables and charts need their own object checks. Bitmap or SVG formula assets remain pictures even when individually selectable. Exact logos, charts and scientific figures keep their originals and evidence meanings. If a specialized object cannot be reconstructed faithfully, record its picture exception and source rather than claiming native editability.

This package carries no template, theme or global style library. Installation and source synchronization belong to the installation owner.

A theme switch changes only declared palette and asset properties. Shared canvas, typography, geometry, layout/slot identities and content meaning remain fixed unless the template explicitly defines an exception. Rebuild and inspect affected pages after a switch. Recompilation sets the PowerPoint theme palette; it does not retroactively recolor undeclared source literals.

For a template with chapter/subsection agendas, use its declared generator and data contract. A single overview may expand all subsections or collapse them all. Repeated agendas precede chapter and subsection entries, expand only the chapter being entered, and highlight the actual target through stable parent/child IDs. Preserve chapters without children. Bind any generated insertion plan to the report's real page order; co-located chapter/first-subsection entries need one agenda rather than consecutive duplicates. Reuse the template's fixed typography and whole-chapter column recipe; report capacity failures without dropping children, shrinking text or silently turning a single overview into multiple pages.

When the selected template provides a shared page-header generator, all pages with that header must use it. Supply the page title, the navigation number or upper-line text with its existing report meaning, and the current chapter or subsection's full title plus any explicit header short title. Keep the agenda title intact. Select the current leaf by stable IDs; do not infer a page number, chapter number or new numbering policy from that selection. Respect the template's fixed short-title capacity, actual font-width checks, divider and page-title coordinates. A shorter name does not move the main title; an overlong name needs an explicit short title, and a page title requiring two lines uses the declared two-line layout. Do not shrink type, change tracking, truncate text or replace only a prototype navigation token. Preserve layouts without this header. When adapting a frozen page-library source, first apply the current template's header adapter to a project-local copy; leave the library source and preview bytes intact.

Icon material handoff

Apply icon production to template reuse and all new authored, generated or external icons. Use a project-local material descriptor for new icons; do not edit a locked vendor snapshot. Whole and partial coloring follow the same contract.

Supply the original SVG, its paint_contract_data, selected palette and exact asset bindings together. New vector materials use stable element IDs and adjustable fill/stroke pairs with semantic tokens. Distinct tokens express independent roles; a shared token expresses a shared role. Keep fixed details as literal values and unpainted openings as structural: none. Undeclared channels preserve their source paint.

scripts/paint_asset.py --manifest <path> --theme <id> --asset <role> --output <new.svg> applies only the selected theme's palette whitelist. It verifies exact IDs, explicit source paint, fixed/structural values and bindings, then protects existing output. It intentionally rejects stylesheets, overridden target channels and inherited target paint; flatten those channels into explicit reviewed attributes before using this helper. Other SVG authoring tools may support richer materials if they preserve the same contract.

Do not replace colors across a whole image or infer roles from matching colors. Keep geometry, opacity, masks, paint order, fixed colors and none intact. Raster materials with independent color roles require layers or reviewed per-role alpha masks; a flat PNG's colors do not grant recoloring permission. Preserve original assets and record derivatives separately.

Render the derived material on its intended background and compare it with the original. Structural gaps and fixed details must remain visible. Path/JSON/hash validation, SVG transformation, rendering, native structure and application editing are distinct evidence levels.