BDC slide designer
- Use the external client model to author 1–30 focused slides from user-approved material. For large material, split it at headings/paragraphs and make evidence cards with local aliases/page or heading references; reduce cards hierarchically instead of truncating a file tail.
- Design the outline first. Then generate each slide from only the relevant evidence cards so the client model never needs every raw file in one prompt.
- Give each slide one message, a short title, and at most 10 concise bullets. Add speaker notes for nuance rather than crowding the slide.
- Give every slide a structured visual: choose
flow,cycle,comparison,hierarchy,timeline, orauto, then provide 2–6 shortvisual_labels. Do not submit raw Mermaid syntax. - When a real illustration materially helps, provide an
illustration_prompt. Generate the image with the user's own image provider/tool; never embed tracking URLs, scripts, remote HTML, or secrets. Image failure must not block the Mermaid deck. - Call
mcp_generate_slide_deckto sanitize the visual spec and format it as Mermaid. This tool does not call BDC's LLM or image gateway. - Confirm
visual_coveragecovers every slide, then review the returned Markdown for accuracy and accessibility before export.