Visual Canvas Deck

Bring rough notes, approved content blocks/source material, the purpose, audience and desired decision. State approximate slide count, visual direction, brand boundaries and navigation preferences. Resolve only the missing essentials in one round; a shortcut default should be clearly labeled and accepted rather than silently selected.

Review the full title, story summary, ordered page list, look and asset decision together before generation. Approve that complete plan, not only a cover. Ask for refinement when the direction is right but parts need work; request a separate branch when a different direction should be compared.

Choose Cobalt Registry, Vermilion Archive or Moss Signal. Compose purposeful boards with oversized type, unequal columns, offset planes and ruled backgrounds. The default cobalt surface comes from a style class in addition to the three theme tokens. Do not turn every item into equal rounded cards or assume a preset-switching control exists in the shared editor.

Use the five style-kit recipes and adapt nodes for a process wall or quote crop. Keep IDs unique and words literal so specific pages/objects can be changed without recreating the whole deck. Replace neighborhood-workspace claims, capacity values and labels with approved material. Use current-color inline SVG for meaningful cues, not decorative model marks or text-glyph arrows.

Keep the composition complete with programmatic paper, rules and diagrams. Prefer approved user assets and embed pictures locally at an appropriate 2× display size only when they materially support a point. Set UI language independently of content language, which defaults to English unless requested otherwise.

Compose the plan, resolve leftovers/unfilled slots and build/check with Python 3 and the agreed count/style kit. Open over local HTTP and inspect all boards for hierarchy, asymmetric balance, legible source/coordinate labels, crops and bounds. Use Edit or E to revise content/order/notes, and test object changes, undo/redo, Save and reopening the saved HTML.

For refinement, name the affected page/node and preserve unrelated material. For a branch, retain a separate version and compare its narrative as well as its appearance; the workflow does not itself provide a cloud comparison service. Recheck pacing after reordering.

Export requested PPTX/PDF from the standalone deck, run the packaged PPTX check and inspect notes, text wrapping, rendered diagrams and fonts in the intended presentation software. Record actual differences and keep the approved plan alongside the handoff so reviewers can see which direction was developed.