Producing decks
New decks: always through the generation pipeline
For blank/from-scratch decks do not hand-assemble pages element by element — use the pipeline:
If the brief is vague,
ask_clarification(audience, goal, tone) or decide with professional judgment.Pick a style spec from
templates/decks/and read it:Spec Character modern.mdBold, asymmetric, one idea per slide elegant.mdEditorial serif, muted luxury professional.mdCorporate reviews/QBRs, agenda + summary keynote-speaker.mdStage deck: huge type, dark, no bullets minimal.mdMonochrome, typographic, zero decoration tech-dark.mdDeveloper product: dark UI, code cards investor-pitch.mdFundraising: traction-first, ≤12 slides workshop.mdInteractive session: exercises + timeboxes plan_deckwith acore_hook, the spec's Style section asstyle, and the user's content mapped onto the spec's suggested page plan.generate_deckonce, passing all planned pages; follow the<generation-progress>notes until every page is done.
Refining an existing deck (native tools)
When the deck already has real content, refine with the element tools:
read_slide for fresh ids, then set_element_text/style/transform/fill/ stroke, edit_table_*, edit_chart, set_slide_background. For
multi-element layout changes use execute_slide_script (atomic, reads real
geometry) and heed the layout-audit warnings it returns.
Data discipline
Charts require a declared dataSource (user / document / search /
sample). search requires an actual web_search in this conversation;
sample data must be explicitly flagged to the user as illustrative.