@thanh01.pmt/presentation-kit 0.2.10 → 0.2.12

package/dist/ai/index.d.ts

@@ -1,6 +1,6 @@
 import { z } from 'zod';
-import { c as SlideLayoutCategory } from '../presets-B_TY4i2a.js';
-import { b as SlideLayoutData } from '../types-C1121XLt.js';
+import { c as SlideLayoutCategory } from '../presets-BUzebXzj.js';
+import { b as SlideLayoutData, d as HtmlLayoutPresetId, f as HtmlDeckData, H as HtmlThemeName, m as HtmlSlideSlotData } from '../types-8AVYoEUn.js';
 
 declare const listSlidePresetsSchema: z.ZodObject<{
     category: z.ZodOptional<z.ZodEnum<["all", "cover", "content", "split", "code", "metrics", "diagram", "quote", "assessment"]>>;
@@ -201,6 +201,238 @@ declare function executeGenerateDeckOutline(params: {
     }[];
 };
 
-declare const SLIDE_DESIGN_PROMPT_CONTRACT = "\n# SYSTEM MANDATE: PROFESSIONAL PRESENTATION & SLIDE DESIGN INVARIANTS\n\nYou are an expert Presentation Architect & Visual Designer for educational, technical, and executive decks.\nWhen generating or modifying Marp slide presentations, you MUST STRICTLY obey the following non-negotiable rules:\n\n---\n\n## 1. DURATION-INDEXED SLIDE PACING\nStructure decks based on allocated talk time (averaging 1.5 - 2 minutes per slide):\n- **5 min (Lightning Talk):** 5 - 7 slides [Hook -> 2-3 Core Points -> CTA / Summary]\n- **15 min (Short Tech Talk):** 12 - 16 slides [Title -> Agenda -> Hook -> 3-4 Concepts -> Lab/Demo -> Summary]\n- **30 min (Conference / Class):** 24 - 32 slides [Full 5E Learning Cycle + Interactive Formative Checkpoint]\n- **45-60 min (Keynote / Workshop):** 36 - 50 slides [Modular Micro-cycles + Tiered Hands-on Exercises]\n\n---\n\n## 2. THE \"ONE IDEA PER SLIDE\" RULE\n- Each slide communicates **EXACTLY ONE** pedagogical or architectural concept.\n- Never pack multiple distinct topics into a single slide.\n- If a concept has both theory and code, split into: (Slide A) Concept Diagram -> (Slide B) Code Walkthrough.\n\n---\n\n## 3. STRICT WORD BUDGET (ZERO-SCROLL INVARIANT)\n- **Hard Limit:** Maximum **35 - 40 words** per card or column.\n- Never write paragraphs longer than 2 sentences. Use structured bullets with bold anchor terms:\n  - Format: `- **Key Concept:** Concise explanation in a single line.`\n- Vertical scrolling inside a slide is STRICTLY FORBIDDEN. Content must fit the 16:9 (1280x720) canvas cleanly.\n\n---\n\n## 4. TWO-COLUMN & CARD BALANCED LAYOUTS\n- Avoid centered vertical walls of text. Use responsive side-by-side card wrappers:\n  ```html\n  <div class=\"columns-2\">\n  <div>\n  ### \uD83D\uDD34 Legacy / Challenge\n  - High idle compute overhead\n  - Cascading timeout failures\n  </div>\n  <div>\n  ### \uD83D\uDFE2 Modern / Solution\n  - Event-driven webhook streams\n  - Automatic queue backpressure\n  </div>\n  </div>\n  ```\n- For 3 metrics or bronze/silver/gold differentiation, use `<div class=\"columns-3\">...</div>`.\n\n---\n\n## 5. MANDATORY PRESENTER NOTES (TEACHER TALK TRACK)\nEvery single slide MUST conclude with an HTML comment block containing:\n1. **Talk Track:** 2-3 sentences of what the speaker should say out loud.\n2. **Cold-Call Check Question:** 1 diagnostic question to ask a specific student or attendee.\n3. **Scaffolding Tip:** 1 hint or real-world analogy if learners look confused.\n\nExample:\n```markdown\n<!--\nPresenter Notes:\n- Walk through the primary bottleneck when scaling database writes under high concurrency.\n- Cold-call: \"Alex, if traffic spikes 10x in 1 minute, which subsystem will experience lock contention first?\"\n- Scaffolding tip: Remind the room of the I/O saturation trade-off discussed in the previous module.\n-->\n```\n\n---\n\n## 6. MARP COMPATIBLE YAML LAYOUT HEADERS\nWhen a precise coordinate layout is specified, include the clean YAML block at the very top of the slide:\n```markdown\n<!-- layout:\n  boxes:\n    - id: heading\n      target: h2\n      pos: [80, 50, 1120, 70]\n      fontSize: 2rem\n    - id: col-left\n      target: '.columns-2 > div:first-child'\n      pos: [80, 150, 530, 510]\n    - id: col-right\n      target: '.columns-2 > div:last-child'\n      pos: [670, 150, 530, 510]\n-->\n```\n";
+declare const SLIDE_DESIGN_PROMPT_CONTRACT = "\n# SYSTEM MANDATE: PROFESSIONAL PRESENTATION & SLIDE DESIGN INVARIANTS\n\nYou are an expert Presentation Architect & Visual Designer for educational, technical, and executive decks.\nWhen generating or modifying Marp slide presentations, you MUST STRICTLY obey the following non-negotiable rules:\n\n---\n\n## 1. DURATION-INDEXED SLIDE PACING\nStructure decks based on allocated talk time (averaging 1.5 - 2 minutes per slide):\n- **5 min (Lightning Talk):** 5 - 7 slides [Hook -> 2-3 Core Points -> CTA / Summary]\n- **15 min (Short Tech Talk):** 12 - 16 slides [Title -> Agenda -> Hook -> 3-4 Concepts -> Lab/Demo -> Summary]\n- **30 min (Conference / Class):** 24 - 32 slides [Full 5E Learning Cycle + Interactive Formative Checkpoint]\n- **45-60 min (Keynote / Workshop):** 36 - 50 slides [Modular Micro-cycles + Tiered Hands-on Exercises]\n\n---\n\n## 2. THE \"ONE IDEA PER SLIDE\" RULE\n- Each slide communicates **EXACTLY ONE** pedagogical or architectural concept.\n- Never pack multiple distinct topics into a single slide.\n- If a concept has both theory and code, split into: (Slide A) Concept Diagram -> (Slide B) Code Walkthrough.\n\n---\n\n## 3. STRICT WORD BUDGET (ZERO-SCROLL INVARIANT)\n- **Hard Limit:** Maximum **35 - 40 words** per card or column.\n- Never write paragraphs longer than 2 sentences. Use structured bullets with bold anchor terms:\n  - Format: `- **Key Concept:** Concise explanation in a single line.`\n- Vertical scrolling inside a slide is STRICTLY FORBIDDEN. Content must fit the 16:9 (1280x720) canvas cleanly.\n\n---\n\n## 4. TWO-COLUMN & CARD BALANCED LAYOUTS\n- Avoid centered vertical walls of text. Use responsive side-by-side card wrappers:\n  ```html\n  <div class=\"columns-2\">\n  <div>\n  ### \uD83D\uDD34 Legacy / Challenge\n  - High idle compute overhead\n  - Cascading timeout failures\n  </div>\n  <div>\n  ### \uD83D\uDFE2 Modern / Solution\n  - Event-driven webhook streams\n  - Automatic queue backpressure\n  </div>\n  </div>\n  ```\n- For 3 metrics or bronze/silver/gold differentiation, use `<div class=\"columns-3\">...</div>`.\n\n---\n\n## 5. MANDATORY PRESENTER NOTES (TEACHER TALK TRACK)\nEvery single slide MUST conclude with an HTML comment block containing:\n1. **Talk Track:** 2-3 sentences of what the speaker should say out loud.\n2. **Cold-Call Check Question:** 1 diagnostic question to ask a specific student or attendee.\n3. **Scaffolding Tip:** 1 hint or real-world analogy if learners look confused.\n\nExample:\n```markdown\n<!--\nPresenter Notes:\n- Walk through the primary bottleneck when scaling database writes under high concurrency.\n- Cold-call: \"Alex, if traffic spikes 10x in 1 minute, which subsystem will experience lock contention first?\"\n- Scaffolding tip: Remind the room of the I/O saturation trade-off discussed in the previous module.\n-->\n```\n\n---\n\n## 6. MARP COMPATIBLE YAML LAYOUT HEADERS\nWhen a precise coordinate layout is specified, include the clean YAML block at the very top of the slide:\n```markdown\n<!-- layout:\n  boxes:\n    - id: heading\n      target: h2\n      pos: [80, 50, 1120, 70]\n      fontSize: 2rem\n    - id: col-left\n      target: '.columns-2 > div:first-child'\n      pos: [80, 150, 530, 510]\n    - id: col-right\n      target: '.columns-2 > div:last-child'\n      pos: [670, 150, 530, 510]\n-->\n```\n\n---\n\n## 7. STEP REVEAL & PROGRESSIVE DISCLOSURE\nWhen presenting lists, comparisons, or multi-phase concepts, support sequential reveals:\n- Annotate lists or elements with `<!-- v-click -->` or apply class `.step-reveal` / `[data-step]`.\n- Clicking or pressing forward arrow reveals items sequentially before transitioning to the next slide.\n- Keep list items concise (< 15 words) to maintain visual rhythm during progressive steps.\n";
 
-export { SLIDE_DESIGN_PROMPT_CONTRACT, applySlideLayoutSchema, createSlideFromPresetSchema, executeApplySlideLayout, executeCreateSlideFromPreset, executeGenerateDeckOutline, executeListSlidePresets, executeUpdatePresenterNotes, generateDeckOutlineSchema, listSlidePresetsSchema, updatePresenterNotesSchema };
+declare const validateSlideDeckSchema: z.ZodObject<{
+    format: z.ZodDefault<z.ZodEnum<["auto", "html", "markdown"]>>;
+    markdown: z.ZodOptional<z.ZodString>;
+    htmlDeck: z.ZodOptional<z.ZodObject<{
+        title: z.ZodOptional<z.ZodString>;
+        subtitle: z.ZodOptional<z.ZodString>;
+        theme: z.ZodOptional<z.ZodString>;
+        slides: z.ZodOptional<z.ZodArray<z.ZodObject<{
+            layoutId: z.ZodString;
+            slots: z.ZodRecord<z.ZodString, z.ZodAny>;
+            notes: z.ZodOptional<z.ZodString>;
+        }, "strip", z.ZodTypeAny, {
+            layoutId: string;
+            slots: Record<string, any>;
+            notes?: string | undefined;
+        }, {
+            layoutId: string;
+            slots: Record<string, any>;
+            notes?: string | undefined;
+        }>, "many">>;
+    }, "strip", z.ZodTypeAny, {
+        title?: string | undefined;
+        subtitle?: string | undefined;
+        slides?: {
+            layoutId: string;
+            slots: Record<string, any>;
+            notes?: string | undefined;
+        }[] | undefined;
+        theme?: string | undefined;
+    }, {
+        title?: string | undefined;
+        subtitle?: string | undefined;
+        slides?: {
+            layoutId: string;
+            slots: Record<string, any>;
+            notes?: string | undefined;
+        }[] | undefined;
+        theme?: string | undefined;
+    }>>;
+    strict: z.ZodDefault<z.ZodBoolean>;
+}, "strip", z.ZodTypeAny, {
+    format: "markdown" | "auto" | "html";
+    strict: boolean;
+    markdown?: string | undefined;
+    htmlDeck?: {
+        title?: string | undefined;
+        subtitle?: string | undefined;
+        slides?: {
+            layoutId: string;
+            slots: Record<string, any>;
+            notes?: string | undefined;
+        }[] | undefined;
+        theme?: string | undefined;
+    } | undefined;
+}, {
+    markdown?: string | undefined;
+    format?: "markdown" | "auto" | "html" | undefined;
+    htmlDeck?: {
+        title?: string | undefined;
+        subtitle?: string | undefined;
+        slides?: {
+            layoutId: string;
+            slots: Record<string, any>;
+            notes?: string | undefined;
+        }[] | undefined;
+        theme?: string | undefined;
+    } | undefined;
+    strict?: boolean | undefined;
+}>;
+type ValidateSlideDeckInput = z.infer<typeof validateSlideDeckSchema>;
+interface SlideValidationIssue {
+    slideIndex: number;
+    severity: 'error' | 'warning';
+    rule: string;
+    message: string;
+}
+interface SlideValidationResult {
+    success: boolean;
+    valid: boolean;
+    score: number;
+    format: 'html' | 'markdown';
+    slideCount: number;
+    notesCoveragePercent: number;
+    issues: SlideValidationIssue[];
+    suggestions: string[];
+}
+/**
+ * Validate structured HTML slide deck against design and pedagogical invariants
+ */
+declare function validateHtmlSlideDeck(deck: {
+    slides?: Array<{
+        layoutId: string;
+        slots?: Record<string, any>;
+        notes?: string;
+    }>;
+    title?: string;
+    subtitle?: string;
+    theme?: string;
+}, strict?: boolean): SlideValidationResult;
+/**
+ * Validate raw Markdown / Marp slide presentation
+ */
+declare function validateMarkdownSlideDeck(markdown: string, strict?: boolean): SlideValidationResult;
+/**
+ * Universal executor for validating slide decks in either format
+ */
+declare function executeValidateSlideDeck(input: ValidateSlideDeckInput): SlideValidationResult;
+declare const handleValidateSlideDeck: typeof executeValidateSlideDeck;
+
+declare const listHtmlSlidePresetsSchema: z.ZodObject<{
+    category: z.ZodOptional<z.ZodEnum<["all", "cover", "content", "split", "grid", "timeline", "callout", "assessment"]>>;
+}, "strip", z.ZodTypeAny, {
+    category?: "all" | "cover" | "content" | "split" | "assessment" | "grid" | "timeline" | "callout" | undefined;
+}, {
+    category?: "all" | "cover" | "content" | "split" | "assessment" | "grid" | "timeline" | "callout" | undefined;
+}>;
+declare const htmlSlideSlotDataSchema: z.ZodObject<{
+    layoutId: z.ZodEnum<["hero-cover", "split-concept-code", "two-columns-compare", "three-cards-grid", "timeline-steps", "metric-callout", "checkpoint-quiz", "summary-takeaways"]>;
+    slots: z.ZodRecord<z.ZodString, z.ZodAny>;
+    notes: z.ZodOptional<z.ZodString>;
+}, "strip", z.ZodTypeAny, {
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+    slots: Record<string, any>;
+    notes?: string | undefined;
+}, {
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+    slots: Record<string, any>;
+    notes?: string | undefined;
+}>;
+declare const generateHtmlDeckSchema: z.ZodObject<{
+    title: z.ZodString;
+    subtitle: z.ZodOptional<z.ZodString>;
+    theme: z.ZodDefault<z.ZodEnum<["blue-professional", "editorial-forest", "cobalt-grid", "studio", "monochrome"]>>;
+    slides: z.ZodArray<z.ZodObject<{
+        layoutId: z.ZodEnum<["hero-cover", "split-concept-code", "two-columns-compare", "three-cards-grid", "timeline-steps", "metric-callout", "checkpoint-quiz", "summary-takeaways"]>;
+        slots: z.ZodRecord<z.ZodString, z.ZodAny>;
+        notes: z.ZodOptional<z.ZodString>;
+    }, "strip", z.ZodTypeAny, {
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+        slots: Record<string, any>;
+        notes?: string | undefined;
+    }, {
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+        slots: Record<string, any>;
+        notes?: string | undefined;
+    }>, "many">;
+}, "strip", z.ZodTypeAny, {
+    title: string;
+    slides: {
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+        slots: Record<string, any>;
+        notes?: string | undefined;
+    }[];
+    theme: "blue-professional" | "editorial-forest" | "cobalt-grid" | "studio" | "monochrome";
+    subtitle?: string | undefined;
+}, {
+    title: string;
+    slides: {
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+        slots: Record<string, any>;
+        notes?: string | undefined;
+    }[];
+    subtitle?: string | undefined;
+    theme?: "blue-professional" | "editorial-forest" | "cobalt-grid" | "studio" | "monochrome" | undefined;
+}>;
+declare const createHtmlSlideSchema: z.ZodObject<{
+    layoutId: z.ZodEnum<["hero-cover", "split-concept-code", "two-columns-compare", "three-cards-grid", "timeline-steps", "metric-callout", "checkpoint-quiz", "summary-takeaways"]>;
+    slots: z.ZodRecord<z.ZodString, z.ZodAny>;
+    notes: z.ZodOptional<z.ZodString>;
+}, "strip", z.ZodTypeAny, {
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+    slots: Record<string, any>;
+    notes?: string | undefined;
+}, {
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
+    slots: Record<string, any>;
+    notes?: string | undefined;
+}>;
+
+declare const SLIDE_HTML_PROMPT_CONTRACT = "\n# \uD83C\uDFA8 HTML SLIDE ENGINE \u2014 AGENT GENERATION CONTRACT\n\nYou are an expert Presentation Designer and Curriculum Architect producing professional, high-impact slide decks.\nInstead of generating free-form HTML or brittle Markdown hacks, you MUST fill structured content into pre-tested **Layout Presets**.\n\n## Available Layout Presets & Required Slots:\n\n1. **hero-cover** (Cover / Title Slide)\n   - `tag` (string): e.g. \"Unit 01 \u00B7 Lesson 02\"\n   - `title` (string): Main bold headline\n   - `subtitle` (string): Subtitle or 1-sentence learning objective\n   - `author` (string): Instructor / Organization\n   - `date` (string): Course term or date\n\n2. **split-concept-code** (Theory + Code Snippet)\n   - `tag` (string): Section topic tag\n   - `title` (string): Topic heading\n   - `points` (string[]): 3 to 4 concise bullet takeaways\n   - `code` (string): Executable source code\n   - `language` (string): Language name (e.g. \"python\", \"typescript\", \"swift\")\n   - `codeNote` (string, optional): One-line hint or execution output\n\n3. **two-columns-compare** (Comparison / Pros vs Cons)\n   - `tag` (string): Topic tag\n   - `title` (string): Headline\n   - `col1Title` (string): e.g. \"Synchronous I/O\"\n   - `col1Items` (string[]): 3 to 4 points\n   - `col2Title` (string): e.g. \"Asynchronous I/O\"\n   - `col2Items` (string[]): 3 to 4 points\n\n4. **three-cards-grid** (3 Core Pillars / Architecture)\n   - `tag` (string): e.g. \"Core Principles\"\n   - `title` (string): Overview headline\n   - `cards` (array of objects): Exactly 3 cards:\n     - `badge`: e.g. \"01\", \"LAYER 1\"\n     - `title`: Card headline\n     - `desc`: 1-2 sentence description\n     - `footer` (optional): Key takeaway\n\n5. **timeline-steps** (Algorithm / Execution Pipeline)\n   - `tag` (string): e.g. \"Workflow\"\n   - `title` (string): Headline\n   - `steps` (array of objects): 3 to 5 steps:\n     - `stepNum` (number/string): 1, 2, 3...\n     - `title`: Step name\n     - `desc`: What happens at this step\n\n6. **metric-callout** (Key Theorem / Benchmark Statistic)\n   - `tag` (string): e.g. \"Time Complexity\"\n   - `metric` (string): Big stat (e.g. \"O(log N)\", \"99.99%\", \"10x\")\n   - `metricLabel` (string): e.g. \"Lookup Efficiency\"\n   - `title` (string): Main takeaway\n   - `desc` (string): Contextual explanation\n\n7. **checkpoint-quiz** (Interactive Checkpoint)\n   - `tag` (string): e.g. \"Quick Knowledge Check\"\n   - `question` (string): Clear question prompt\n   - `options` (array of objects): 2 to 4 options:\n     - `label`: \"A\", \"B\", \"C\", \"D\"\n     - `text`: Option text\n   - `explanation` (string): Explanatory rationale\n\n8. **summary-takeaways** (Wrap-Up / Next Steps)\n   - `tag` (string): e.g. \"Recap\"\n   - `title` (string): Wrap-up headline\n   - `takeaways` (string[]): 3 to 4 memorable bullet points\n   - `nextStep` (string): Teaser for the next lesson or project\n\n## Aesthetic & Quality Invariants (\"Anti-AI-Slop\"):\n- **Brevity is King (Zero-Scroll Invariant):** Each slide is calibrated for a 1920\u00D71080 canvas. Maximum **35\u201340 words** per card or column; maximum **15 words** per bullet item. Never write dense multi-sentence paragraphs that cause vertical scrolling.\n- **Pedagogical Pacing:** Start with `hero-cover`, alternate between `split-concept-code`, `two-columns-compare` and `three-cards-grid`, insert a `checkpoint-quiz` midway, and finish with `summary-takeaways`.\n- **Theme Selection:**\n  - `blue-professional`: General academic, clean engineering, trustworthy.\n  - `cobalt-grid`: Advanced tech, algorithms, robotics, cybersecurity.\n  - `editorial-forest`: Thoughtful design, literature, ethics, science.\n  - `studio`: Minimalist product design, modern software.\n  - `monochrome`: Pure high-contrast dark mode.\n\n## \uD83E\uDE84 Step Reveal & Progressive Disclosure:\n- The presentation shell supports sequential step reveal via mouse click or Space/Arrow keys.\n- Bullet lists (`points`, `col1Items`, `col2Items`), cards in `three-cards-grid`, and steps in `timeline-steps` reveal progressively one by one before navigating to the next slide.\n- In custom HTML slots, you can attach `class=\"step-reveal\"`, `data-step`, `data-reveal`, or `data-auto-reveal=\"true\"` on parent containers to enable click-by-click stepped appearance.\n\n## \uD83C\uDF99\uFE0F Mandatory 3-Part Presenter Notes Contract:\nEvery single slide MUST include the `notes` property structured with these 3 explicit components:\n1. **Talk Track:** 2-3 sentences of exact conversational speaking script for the teacher/presenter.\n2. **Cold-Call Check Question:** 1 diagnostic question to check understanding with a named student or attendee.\n3. **Scaffolding Tip:** 1 intuitive analogy or troubleshooting hint in case learners struggle with the concept.\n\nExample Notes:\n```markdown\nTalk Track: Here we contrast synchronous blocking I/O with asynchronous event-driven handling. Notice how threads remain idle while waiting for network responses.\nCold-Call: \"Jordan, looking at the left column, what happens to thread pool throughput when network latency quadruples?\"\nScaffolding Tip: Compare it to ordering coffee at a counter (async buzzer) versus waiting at the register until the cup is brewed (sync blocking).\n```\n";
+
+declare function handleListHtmlSlidePresets(input: {
+    category?: string;
+}): {
+    success: boolean;
+    presets: {
+        id: HtmlLayoutPresetId;
+        name: string;
+        category: "cover" | "content" | "split" | "assessment" | "grid" | "timeline" | "callout";
+        description: string;
+        slots: {
+            name: string;
+            label: string;
+            type: "code" | "options" | "text" | "multiline" | "list" | "badge" | "metric";
+            required: boolean;
+            description: string;
+        }[];
+    }[];
+    availableThemes: string[];
+};
+declare function handleGenerateHtmlDeck(input: HtmlDeckData): {
+    success: boolean;
+    title: string;
+    slideCount: number;
+    theme: HtmlThemeName;
+    html: string;
+    error?: undefined;
+} | {
+    success: boolean;
+    error: any;
+    title?: undefined;
+    slideCount?: undefined;
+    theme?: undefined;
+    html?: undefined;
+};
+declare function handleCreateHtmlSlide(input: HtmlSlideSlotData): {
+    success: boolean;
+    error: string;
+    slide?: undefined;
+} | {
+    success: boolean;
+    slide: {
+        layoutId: HtmlLayoutPresetId;
+        slots: Record<string, any>;
+        notes: string | undefined;
+    };
+    error?: undefined;
+};
+declare const executeListHtmlSlidePresets: typeof handleListHtmlSlidePresets;
+declare const executeGenerateHtmlDeck: typeof handleGenerateHtmlDeck;
+declare const executeCreateHtmlSlide: typeof handleCreateHtmlSlide;
+
+export { SLIDE_DESIGN_PROMPT_CONTRACT, SLIDE_HTML_PROMPT_CONTRACT, type SlideValidationIssue, type SlideValidationResult, type ValidateSlideDeckInput, applySlideLayoutSchema, createHtmlSlideSchema, createSlideFromPresetSchema, executeApplySlideLayout, executeCreateHtmlSlide, executeCreateSlideFromPreset, executeGenerateDeckOutline, executeGenerateHtmlDeck, executeListHtmlSlidePresets, executeListSlidePresets, executeUpdatePresenterNotes, executeValidateSlideDeck, generateDeckOutlineSchema, generateHtmlDeckSchema, handleCreateHtmlSlide, handleGenerateHtmlDeck, handleListHtmlSlidePresets, handleValidateSlideDeck, htmlSlideSlotDataSchema, listHtmlSlidePresetsSchema, listSlidePresetsSchema, updatePresenterNotesSchema, validateHtmlSlideDeck, validateMarkdownSlideDeck, validateSlideDeckSchema };