@thanh01.pmt/presentation-kit 0.2.15 → 0.2.16

package/dist/ai/index.d.ts

@@ -215,20 +215,20 @@ declare const validateSlideDeckSchema: z.ZodObject<{
             slots: z.ZodRecord<z.ZodString, z.ZodAny>;
             notes: z.ZodOptional<z.ZodString>;
         }, "strip", z.ZodTypeAny, {
-            layoutId: string;
             slots: Record<string, any>;
+            layoutId: string;
             notes?: string | undefined;
         }, {
-            layoutId: string;
             slots: Record<string, any>;
+            layoutId: string;
             notes?: string | undefined;
         }>, "many">>;
     }, "strip", z.ZodTypeAny, {
         title?: string | undefined;
         subtitle?: string | undefined;
         slides?: {
-            layoutId: string;
             slots: Record<string, any>;
+            layoutId: string;
             notes?: string | undefined;
         }[] | undefined;
         theme?: string | undefined;
@@ -236,8 +236,8 @@ declare const validateSlideDeckSchema: z.ZodObject<{
         title?: string | undefined;
         subtitle?: string | undefined;
         slides?: {
-            layoutId: string;
             slots: Record<string, any>;
+            layoutId: string;
             notes?: string | undefined;
         }[] | undefined;
         theme?: string | undefined;
@@ -251,8 +251,8 @@ declare const validateSlideDeckSchema: z.ZodObject<{
         title?: string | undefined;
         subtitle?: string | undefined;
         slides?: {
-            layoutId: string;
             slots: Record<string, any>;
+            layoutId: string;
             notes?: string | undefined;
         }[] | undefined;
         theme?: string | undefined;
@@ -264,8 +264,8 @@ declare const validateSlideDeckSchema: z.ZodObject<{
         title?: string | undefined;
         subtitle?: string | undefined;
         slides?: {
-            layoutId: string;
             slots: Record<string, any>;
+            layoutId: string;
             notes?: string | undefined;
         }[] | undefined;
         theme?: string | undefined;
@@ -324,12 +324,12 @@ declare const htmlSlideSlotDataSchema: z.ZodObject<{
     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>;
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
     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>;
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
     notes?: string | undefined;
 }>;
 declare const generateHtmlDeckSchema: z.ZodObject<{
@@ -341,19 +341,19 @@ declare const generateHtmlDeckSchema: z.ZodObject<{
         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>;
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
         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>;
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
         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>;
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
         notes?: string | undefined;
     }[];
     theme: "blue-professional" | "editorial-forest" | "cobalt-grid" | "studio" | "monochrome";
@@ -361,8 +361,8 @@ declare const generateHtmlDeckSchema: z.ZodObject<{
 }, {
     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>;
+        layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
         notes?: string | undefined;
     }[];
     subtitle?: string | undefined;
@@ -373,16 +373,16 @@ declare const createHtmlSlideSchema: z.ZodObject<{
     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>;
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
     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>;
+    layoutId: "hero-cover" | "split-concept-code" | "two-columns-compare" | "three-cards-grid" | "timeline-steps" | "metric-callout" | "checkpoint-quiz" | "summary-takeaways";
     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 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\n## \uD83E\uDDF1 MANDATORY JSON DECK OUTPUT STRUCTURE & SCHEMA:\nYou MUST output a single valid JSON object.\nCRITICAL: All layout data MUST be placed inside the `slots` object of each slide. Never put raw unstructured strings like `content: \"...\"`!\n\n```json\n{\n  \"title\": \"Full Lesson Presentation Title\",\n  \"theme\": \"blue-professional\",\n  \"slides\": [\n    {\n      \"id\": 1,\n      \"layoutId\": \"hero-cover\",\n      \"slots\": {\n        \"tag\": \"Unit 01 \u00B7 Lesson 01\",\n        \"title\": \"macOS & Xcode Environment Setup\",\n        \"subtitle\": \"Master the Apple developer toolchain and build your first SwiftUI application lifecycle\",\n        \"author\": \"Curriculum OS\",\n        \"date\": \"2026\"\n      },\n      \"notes\": \"Talk Track: Welcome everyone. Today we establish our core iOS development environment...\\nCold-Call: 'Alex, why do we need Xcode Command Line Tools?'\\nScaffolding Tip: Think of Xcode as the full workshop and the SDK as the raw materials.\"\n    },\n    {\n      \"id\": 2,\n      \"layoutId\": \"split-concept-code\",\n      \"slots\": {\n        \"tag\": \"Architecture & Syntax\",\n        \"title\": \"SwiftUI App Entry Point\",\n        \"points\": [\n          \"@main attribute designates the entry point of the app\",\n          \"App protocol defines the structure and scene hierarchy\",\n          \"WindowGroup manages the root view lifecycle across platforms\"\n        ],\n        \"code\": \"import SwiftUI\\n\\n@main\\nstruct MyApp: App {\\n    var body: some Scene {\\n        WindowGroup {\\n            ContentView()\\n        }\\n    }\\n}\",\n        \"language\": \"swift\",\n        \"codeNote\": \"Notice how Scene encapsulates WindowGroup automatically\"\n      },\n      \"notes\": \"Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ...\"\n    },\n    {\n      \"id\": 3,\n      \"layoutId\": \"three-cards-grid\",\n      \"slots\": {\n        \"tag\": \"Core Pillars\",\n        \"title\": \"Three Pillars of App State\",\n        \"cards\": [\n          { \"badge\": \"01\", \"title\": \"Active State\", \"desc\": \"App is in foreground and responding to user events directly.\" },\n          { \"badge\": \"02\", \"title\": \"Inactive State\", \"desc\": \"App is transitioning, interrupted by system dialogs or Control Center.\" },\n          { \"badge\": \"03\", \"title\": \"Background State\", \"desc\": \"Executing background tasks or preparing for memory suspension.\" }\n        ]\n      },\n      \"notes\": \"Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ...\"\n    },\n    {\n      \"id\": 4,\n      \"layoutId\": \"timeline-steps\",\n      \"slots\": {\n        \"tag\": \"Step-by-Step\",\n        \"title\": \"Xcode Setup Workflow\",\n        \"steps\": [\n          { \"stepNum\": 1, \"title\": \"Download Xcode\", \"desc\": \"Install latest Xcode from the Mac App Store\" },\n          { \"stepNum\": 2, \"title\": \"Command Line Tools\", \"desc\": \"Run xcode-select --install in Terminal\" },\n          { \"stepNum\": 3, \"title\": \"Select Simulators\", \"desc\": \"Download iOS 18+ runtime simulators\" },\n          { \"stepNum\": 4, \"title\": \"Verify Build\", \"desc\": \"Create a new SwiftUI project and press Cmd+R\" }\n        ]\n      },\n      \"notes\": \"Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ...\"\n    },\n    {\n      \"id\": 5,\n      \"layoutId\": \"two-columns-compare\",\n      \"slots\": {\n        \"tag\": \"Comparison\",\n        \"title\": \"SwiftUI vs UIKit Architecture\",\n        \"col1Title\": \"SwiftUI (Declarative)\",\n        \"col1Items\": [\n          \"State drives the UI automatically\",\n          \"Lightweight immutable structs\",\n          \"Cross-platform unified API\"\n        ],\n        \"col2Title\": \"UIKit (Imperative)\",\n        \"col2Items\": [\n          \"Manual view controller manipulation\",\n          \"Heavyweight class hierarchies\",\n          \"Explicit event-driven updates\"\n        ]\n      },\n      \"notes\": \"Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ...\"\n    },\n    {\n      \"id\": 6,\n      \"layoutId\": \"checkpoint-quiz\",\n      \"slots\": {\n        \"tag\": \"Knowledge Check\",\n        \"question\": \"Which SwiftUI modifier is used to observe external observable state objects?\",\n        \"options\": [\n          { \"label\": \"A\", \"text\": \"@State\" },\n          { \"label\": \"B\", \"text\": \"@StateObject / @ObservedObject\" },\n          { \"label\": \"C\", \"text\": \"@Binding\" },\n          { \"label\": \"D\", \"text\": \"@Environment\" }\n        ],\n        \"explanation\": \"@StateObject manages the lifecycle of reference-type ObservableObjects, while @State is for value types.\"\n      },\n      \"notes\": \"Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ...\"\n    },\n    {\n      \"id\": 7,\n      \"layoutId\": \"summary-takeaways\",\n      \"slots\": {\n        \"tag\": \"Recap & Next\",\n        \"title\": \"Lesson Summary & Key Takeaways\",\n        \"takeaways\": [\n          \"Configured complete developer toolchain with Xcode 16+\",\n          \"Understood SwiftUI declarative lifecycle and @main entry point\",\n          \"Mastered App State transitions between active, inactive, and background\"\n        ],\n        \"nextStep\": \"Lesson 02: State Management & Reactive Data Flow with @State and @Binding\"\n      },\n      \"notes\": \"Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ...\"\n    }\n  ]\n}\n```\n\n## \uD83D\uDEAB STRICT ANTI-SLOP CONSTRAINTS:\n1. NEVER output a raw unstructured string like `content: \"...\"` or `content: \"Concept: ... Code snippet: ...\"`. All slide content MUST be placed inside the `slots` object with its specific keys (`points`, `code`, `cards`, `steps`, `options`, `takeaways`).\n2. NEVER use ellipsis `...` or placeholder comments in `code`. Every code snippet MUST be real, fully typed, syntax-valid, and pedagogical.\n3. NEVER leave `slots` empty `{}`.\n4. Output 6 to 8 substantive, rich slides covering the lesson plan thoroughly.\n";
 
 declare function handleListHtmlSlidePresets(input: {
     category?: string;

package/dist/ai/index.js

@@ -1,4 +1,4 @@
-import { SLIDE_LAYOUT_PRESETS, getSlideLayoutPresetsByCategory, getSlideLayoutPresetById, serializeLayoutToComment, updateSlideLayoutInMarkdown, splitMarkdownSlides, HTML_SLIDE_PRESETS, HTML_THEMES, compileHtmlDeck } from '../chunk-YPYAP4TF.js';
+import { SLIDE_LAYOUT_PRESETS, getSlideLayoutPresetsByCategory, getSlideLayoutPresetById, serializeLayoutToComment, updateSlideLayoutInMarkdown, splitMarkdownSlides, HTML_SLIDE_PRESETS, normalizeSlideSlots, HTML_THEMES, compileHtmlDeck } from '../chunk-7QHDWDSB.js';
 import { z } from 'zod';
 
 var listSlidePresetsSchema = z.object({
@@ -480,9 +480,10 @@ function validateHtmlSlideDeck(deck, strict = false) {
     if (preset.category === "cover" && idx === 0) hasCover = true;
     if (preset.id === "checkpoint-quiz") hasQuiz = true;
     if (preset.id === "summary-takeaways") hasSummary = true;
+    const slots = normalizeSlideSlots(slide);
     for (const slotDef of preset.slots) {
       if (slotDef.required) {
-        const val = slide.slots?.[slotDef.name];
+        const val = slots[slotDef.name];
         if (val === void 0 || val === null || typeof val === "string" && val.trim() === "") {
           issues.push({
             slideIndex: slideNumber,
@@ -493,7 +494,6 @@ function validateHtmlSlideDeck(deck, strict = false) {
         }
       }
     }
-    const slots = slide.slots || {};
     for (const [key, val] of Object.entries(slots)) {
       if (typeof val === "string") {
         const words = countWords(val);
@@ -865,6 +865,135 @@ Talk Track: Here we contrast synchronous blocking I/O with asynchronous event-dr
 Cold-Call: "Jordan, looking at the left column, what happens to thread pool throughput when network latency quadruples?"
 Scaffolding Tip: Compare it to ordering coffee at a counter (async buzzer) versus waiting at the register until the cup is brewed (sync blocking).
 \`\`\`
+
+## \u{1F9F1} MANDATORY JSON DECK OUTPUT STRUCTURE & SCHEMA:
+You MUST output a single valid JSON object.
+CRITICAL: All layout data MUST be placed inside the \`slots\` object of each slide. Never put raw unstructured strings like \`content: "..."\`!
+
+\`\`\`json
+{
+  "title": "Full Lesson Presentation Title",
+  "theme": "blue-professional",
+  "slides": [
+    {
+      "id": 1,
+      "layoutId": "hero-cover",
+      "slots": {
+        "tag": "Unit 01 \xB7 Lesson 01",
+        "title": "macOS & Xcode Environment Setup",
+        "subtitle": "Master the Apple developer toolchain and build your first SwiftUI application lifecycle",
+        "author": "Curriculum OS",
+        "date": "2026"
+      },
+      "notes": "Talk Track: Welcome everyone. Today we establish our core iOS development environment...\\nCold-Call: 'Alex, why do we need Xcode Command Line Tools?'\\nScaffolding Tip: Think of Xcode as the full workshop and the SDK as the raw materials."
+    },
+    {
+      "id": 2,
+      "layoutId": "split-concept-code",
+      "slots": {
+        "tag": "Architecture & Syntax",
+        "title": "SwiftUI App Entry Point",
+        "points": [
+          "@main attribute designates the entry point of the app",
+          "App protocol defines the structure and scene hierarchy",
+          "WindowGroup manages the root view lifecycle across platforms"
+        ],
+        "code": "import SwiftUI\\n\\n@main\\nstruct MyApp: App {\\n    var body: some Scene {\\n        WindowGroup {\\n            ContentView()\\n        }\\n    }\\n}",
+        "language": "swift",
+        "codeNote": "Notice how Scene encapsulates WindowGroup automatically"
+      },
+      "notes": "Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ..."
+    },
+    {
+      "id": 3,
+      "layoutId": "three-cards-grid",
+      "slots": {
+        "tag": "Core Pillars",
+        "title": "Three Pillars of App State",
+        "cards": [
+          { "badge": "01", "title": "Active State", "desc": "App is in foreground and responding to user events directly." },
+          { "badge": "02", "title": "Inactive State", "desc": "App is transitioning, interrupted by system dialogs or Control Center." },
+          { "badge": "03", "title": "Background State", "desc": "Executing background tasks or preparing for memory suspension." }
+        ]
+      },
+      "notes": "Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ..."
+    },
+    {
+      "id": 4,
+      "layoutId": "timeline-steps",
+      "slots": {
+        "tag": "Step-by-Step",
+        "title": "Xcode Setup Workflow",
+        "steps": [
+          { "stepNum": 1, "title": "Download Xcode", "desc": "Install latest Xcode from the Mac App Store" },
+          { "stepNum": 2, "title": "Command Line Tools", "desc": "Run xcode-select --install in Terminal" },
+          { "stepNum": 3, "title": "Select Simulators", "desc": "Download iOS 18+ runtime simulators" },
+          { "stepNum": 4, "title": "Verify Build", "desc": "Create a new SwiftUI project and press Cmd+R" }
+        ]
+      },
+      "notes": "Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ..."
+    },
+    {
+      "id": 5,
+      "layoutId": "two-columns-compare",
+      "slots": {
+        "tag": "Comparison",
+        "title": "SwiftUI vs UIKit Architecture",
+        "col1Title": "SwiftUI (Declarative)",
+        "col1Items": [
+          "State drives the UI automatically",
+          "Lightweight immutable structs",
+          "Cross-platform unified API"
+        ],
+        "col2Title": "UIKit (Imperative)",
+        "col2Items": [
+          "Manual view controller manipulation",
+          "Heavyweight class hierarchies",
+          "Explicit event-driven updates"
+        ]
+      },
+      "notes": "Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ..."
+    },
+    {
+      "id": 6,
+      "layoutId": "checkpoint-quiz",
+      "slots": {
+        "tag": "Knowledge Check",
+        "question": "Which SwiftUI modifier is used to observe external observable state objects?",
+        "options": [
+          { "label": "A", "text": "@State" },
+          { "label": "B", "text": "@StateObject / @ObservedObject" },
+          { "label": "C", "text": "@Binding" },
+          { "label": "D", "text": "@Environment" }
+        ],
+        "explanation": "@StateObject manages the lifecycle of reference-type ObservableObjects, while @State is for value types."
+      },
+      "notes": "Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ..."
+    },
+    {
+      "id": 7,
+      "layoutId": "summary-takeaways",
+      "slots": {
+        "tag": "Recap & Next",
+        "title": "Lesson Summary & Key Takeaways",
+        "takeaways": [
+          "Configured complete developer toolchain with Xcode 16+",
+          "Understood SwiftUI declarative lifecycle and @main entry point",
+          "Mastered App State transitions between active, inactive, and background"
+        ],
+        "nextStep": "Lesson 02: State Management & Reactive Data Flow with @State and @Binding"
+      },
+      "notes": "Talk Track: ...\\nCold-Call: ...\\nScaffolding Tip: ..."
+    }
+  ]
+}
+\`\`\`
+
+## \u{1F6AB} STRICT ANTI-SLOP CONSTRAINTS:
+1. NEVER output a raw unstructured string like \`content: "..."\` or \`content: "Concept: ... Code snippet: ..."\`. All slide content MUST be placed inside the \`slots\` object with its specific keys (\`points\`, \`code\`, \`cards\`, \`steps\`, \`options\`, \`takeaways\`).
+2. NEVER use ellipsis \`...\` or placeholder comments in \`code\`. Every code snippet MUST be real, fully typed, syntax-valid, and pedagogical.
+3. NEVER leave \`slots\` empty \`{}\`.
+4. Output 6 to 8 substantive, rich slides covering the lesson plan thoroughly.
 `;
 
 // src/ai/html/tools.ts