26 lines
3.8 KiB
Markdown
26 lines
3.8 KiB
Markdown
# 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](native-authoring.md) and [object reconstruction](object-reconstruction.md).
|
|
|
|
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.
|
|
|
|
## Icon material handoff
|
|
|
|
Apply [icon production](icon-production.md) 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.
|