Editable Visual Deck

Provide the topic, audience, desired decision, approved copy and numbers, slide count, visual references and existing design-system constraints. Identify the target presentation application and which text/objects must remain editable there. State animation needs and notes preference; the authored slides are static, so any essential motion needs a separate agreed scope.

Inspect the supplied assets and prior slides, then establish a simple export-safe grammar before drawing pages. Choose Lavender Construction, Signal Cream or Mint Ledger and document font choices/substitutes. Specify whether to include notes rather than relying on the conflicting old/new defaults.

Write a state/object plan for every page and select the closest style-kit recipe. Keep meaningful words and numbers in text leaf nodes, make repeated modules literal, and keep source data separate from decorative geometry. Use small tables of four or fewer rows and a single chart callout where appropriate. Adapt the model for a table if needed; the seven-recipe inventory does not include a standalone table recipe.

Populate the kit with approved content and replace the Signal Notebook sample claims, chart values and handoff labels. In particular, a sample label saying NATIVE SHAPES is not proof of the current exporter’s result. Use simple labeled SVG cues, avoid screenshot slides and do not flatten meaningful text merely to preserve a font.

Compose the plan, resolve sample leftovers and build/check with Python 3 and the agreed count/style kit. The current core build uses the bundled runtime and does not require Node packages. Keep the shared editor unchanged and fonts/media embedded; set interface language independently of slide language, which defaults to English unless requested otherwise.

Open over local HTTP and test Edit/E, wording, labels and values, picture replacement, object movement, slide order, notes, undo/redo and Save. Reopen the saved HTML. Inspect all pages for bounds, contrast, chart scale and readable text; the browser’s local recovery copy is not the portable handoff.

Export PPTX, run check-pptx.py against the project and inspect in the target native application. Confirm titles, labels, chart values and table text are actual text boxes; if intended text was rendered into an artwork layer, correct its source node and export again. Check notes, separate photo objects and fonts. Artwork, bars, shapes and SVG generally become rendered layers, not native editable chart components.

Deliver the HTML and requested PPTX/PDF with a plain inventory of actual editable/rasterized objects, observed font substitutions and validation limits. Mark untested items as untested rather than copying the sample object-audit labels. Check PDF pagination separately and do not infer native editability from a browser screenshot.