Request the user to review and approve a presentation outline before any design generation.
This tool is the MANDATORY ENTRY POINT for ALL presentation creation workflows. NEVER respond with a plain-text outline when user gives feedbacks on the outline, always call this tool again with the updated outline. Keep text response to user to a minimum, you only need to launch the ui://widget/outline-review.html widget for user to review the outline.
INTENT RESOLUTION (CRITICAL — ALWAYS APPLY): Any user request that includes BOTH: 1) a presentation artifact noun ("presentation", "slides", "deck", "pitch"), AND 2) an action or assistance verb ("help", "make", "create", "build", "work on", "put together", "prepare", "generate")
MUST ALWAYS be interpreted as a request to CREATE A PRESENTATION, not as content-only help.
This includes ambiguous phrasing such as:
- "help make a presentation about frogs"
- "help with a presentation on climate change"
- "work on some slides for school"
In all such cases, you MUST call this tool immediately.
DEFAULT BEHAVIOR (NO EXCEPTIONS):
- If the user asks to create, make, help, build, or generate a presentation or slides about any topic, call this tool immediately.
- Do this even if the user provides a complete slide-by-slide outline, full content, or structure.
- Do NOT ask clarifying questions about whether the user wants a presentation.
- Do NOT call generate-design or generate-design-structured before this step is completed.
PURPOSE:
- Generate a proposed slide outline.
- Present it in the outline review widget.
- Allow the user to review, edit, approve, or request changes before any design is generated.
WHEN TO USE (NON-NEGOTIABLE):
- Any request involving "presentation", "slides", "deck", or "pitch"
- Any request phrased as "help me make/create/work on a presentation…"
- Any request like "make slides about…" or "presentation about…"
This applies regardless of wording, tone, or level of detail.
WHAT YOU MUST PROVIDE:
- You MUST generate a complete pages array based on the user's request.
- Each page MUST include:
- title: clear, concise slide title
- description: markdown bullet-point explanation of the slide's content
- Each description MUST contain at least one bullet.
- Each description MUST contain ONLY markdown bullets.
- Descriptions may contain one or more bullets, but ZERO non-bullet text.
SLIDE SEMANTICS (CRITICAL): A slide represents a coherent theme or concept, not a single idea. When users provide many ideas or points that clearly belong to the same theme, prefer grouping them into a single slide and enumerating them line-by-line, unless the user explicitly signals that each idea should be its own slide.
CONTENT PRESERVATION (CRITICAL):
- Populate as much relevant context as possible from the conversation into the outline.
- Treat user-provided content as source-of-truth, including:
- Sample slide content, timelines, phased narratives, bullet points, or year-by-year progressions
- Metaphors, bracketed phrases, emoji used as meaning, and slogan-like language
- Specific examples, data points, and named concepts
- Narrative structure and ordering implied by the user’s writing
- Preserve the user’s wording, formatting, ordering, and level of detail whenever provided.
- The length parameter guidelines apply primarily when generating NEW content, not when mapping or projecting user-provided content into slides.
STRUCTURE PRESERVATION: If the user provides an explicit structure (e.g. timelines, years, phases, steps, or repeated patterned lines), you should preserve that structure explicitly in the outline by enumerating each item as its own slide OR as a clearly listed, line-by-line section within a slide. Describing multiple items in prose does NOT count as enumeration; enumeration requires each item to appear as a distinct line, bullet, or slide. Inline or single-sentence enumeration does NOT count; enumerated items must appear on separate lines, bullets, or slides.
ENUMERATION DEFAULT: When preserving lists, timelines, or multiple related ideas, default to enumerating them within a slide before splitting them into multiple slides.
MULTI-SLIDE SIGNALS: Create separate slides for each item ONLY when the user:
- Explicitly requests one slide per item or section
- Uses language implying presentation pacing (e.g. “one slide on…”, “dedicate a slide to…”)
- Provides a fully formed slide-by-slide outline
USER PREFERENCES (MUST RESPECT):
- If the user expresses ANY preference for audience, length, or style (e.g. "for executives", "make it short", "playful style"), you MUST include those choices in the tool call parameters (audience, length, style) so the widget reflects the user's intent.
- For audience/style, when user explictly provides a audience or style, try to match the user's choice to an existing predefined option when it clearly fits (e.g. audience: casual/professional/educational; style: minimalist/playful/organic/modular/elegant/digital/geometric). If the user's preference does NOT clearly match a predefined option, provide a custom audience/style description.
CONTENT-BEARING OUTLINE (CRITICAL): This outline is content-bearing and may be used verbatim in the final slides. Do not treat it as a scaffold. Every slide description MUST contain final factual values, not TODOs, not "average/typical," and not blanks.
LENGTH PARAMETER (for NEW content generation): The length parameter controls the number of slides only: • "short" - 1-5 slides • "balanced" - 5-15 slides (DEFAULT) • "comprehensive" - 15+ slides
DESCRIPTION FORMAT (CRITICAL - applies to ALL lengths): Always use detailed markdown bullet lists for slide descriptions:
- Use hyphen/asterisk syntax with newlines: "- Item\n- Item\n- Item"
- Do NOT use Unicode bullet characters (•)
- Provide detailed, substantive bullet points for each slide
- Every description must contain final factual values, not placeholders or meta-commentary
- Placeholders are forbidden, including (but not limited to): "TBD", "N/A", "unknown", "varies", "typical", "average", "~", "about", "insert", "research", "estimate later"
- Example: [{ title: "Introduction", description: "- Key point 1: full explanation\n- Key point 2: full explanation\n- Key point 3: full explanation" }]
PROSE BAN (NON-NEGOTIABLE):
- Descriptions MUST consist ONLY of markdown bullet lists.
- Any non-bullet text (including paragraphs, sentences before/after bullets, or inline explanations) is INVALID.
- If a description visually resembles a paragraph, it is INVALID.
✗ INVALID (DO NOT DO THIS): description: "This slide explains Acme Corp’s growth from 2023–2026 and why adoption matters."
✗ INVALID (DO NOT DO THIS): description: "- Acme Corp grew significantly over several years, focusing on extensibility, partnerships, and adoption." Reason: summarizes multiple distinct ideas into a single bullet instead of enumerating them line-by-line.
✓ VALID (DO THIS): description:
- 2023: Proved extensibility worked across core surfaces
- 2024: Scaled integrations and ecosystem partnerships
- 2025: Became foundational to AI and enterprise workflows
- 2026: Focus on adoption and default design-layer status
Defaults if not specified by the user:
- audience: "professional"
- length: "balanced"
- style: "minimalist"
REVIEW LOOP: 1. Call this tool with the generated outline. 2. The user reviews the outline in the widget. 3. If the user requests changes, update the pages and call this tool again. 4. Repeat until the user approves the outline.
NEXT STEP AFTER APPROVAL:
- Only after the outline is approved:
- The user clicks "Generate Design" in the widget, OR
- The user explicitly asks you to generate the design
- ONLY THEN should you call generate-design-structured using the approved outline parameters.
IMPORTANT:
- This tool is required for every presentation.
- Presentation design generation must never bypass outline review.
- This tool is the single gateway for presentation creation.