CodeRaven · Flow Map · Speculative Adaptation

From Class Topic to HTML Slide Deck — A Speculative Pipeline

This is a speculative mirror of CodeRaven’s existing Ideation → Design Studio pipeline, retargeted for developing class sessions, workshop segments, and presentation decks (with HTML slide graphics as the final artifact). Each node parallels a real node in the current app. Updated: the slide rendering at the end now leverages CodeRaven’s existing Mockup Lab — the per-surface conversational HTML generation engine already shipping in Design Studio — so most of that infrastructure already exists rather than needing to be built from scratch. See the footer notes for the extraction audit.

Static content User input User reaction AI call AI synthesis (handoff) Branch point

Context Inspector

Click a data field to highlight every node that produces (solid green) or consumes (dashed blue) it. Makes the “one answer amplified across five prompts” problem visible.

Produces Consumes

Notes. Every node in this map is a speculative adaptation of a real node in CodeRaven’s Ideation → Design Studio flow. Prompts shown in the detail panel are rewrites of the existing verbatim prompts (in IdeationSessionManager.swift, IdeationPromptLibrary.swift, DesignBriefContextBuilder.swift, VisionSynthesisContextBuilder.swift) with the subject swapped from “product” to “class session” and the output artifact swapped from “design brief” to “slide outline / HTML deck.”

What’s new territory vs. what’s reuse. Only two nodes have no current parallel: slideOutlineSynthesis (the deck-spine LLM call) and deckExport (assembly/export, which mostly extends MockupHTMLWrapper). The rest is either a retargeting of existing Ideation/Design Studio machinery or — in the case of slideSurfaceGeneration — a direct reuse of Mockup Lab’s per-surface HTML engine.

Mockup Lab extraction audit. The per-slide HTML generation node would adapt Mockup Lab’s existing engine rather than being built from scratch. What stays unchanged: streaming callback architecture, ClaudeDirectInvoker.invoke plumbing, extractHTMLFromResponse, revision history, CSS token injection via MockupFoundationBridge.generateCSSTokens + MockupHTMLWrapper.wrapMockupHTML, annotation overlay, WebView preview. Three coupling points to parameterize: (1) system prompt vocabulary (“screen”/“mockup” → “slide”) — the biggest friction; (2) TargetZone presets (add 16:9 1920×1080); (3) minor annotation copy. Recommended extraction shape: HTMLSurfaceRenderer protocol with MockupSurfaceSpec and SlideSurfaceSpec conformances; add SlideSession alongside MockupSession rather than renaming the latter (safer refactor). Estimated ~4–6 hrs concentrated work. There are no device-frame or hardware-specific assumptions baked into Mockup Lab — that was the key finding that moves this from “probably reusable” to “yes, reusable.”

Source files this map mirrors: IdeationStudioContainerView.swift, IdeationSessionManager.swift, IdeationPromptLibrary.swift, Beat1ProvocationsView.swift, Beat2MirrorGapView.swift, Beat3CreativeBriefView.swift, QuestionBank.swift, PressureTestService.swift, DeepDiveAIService.swift, VisionSynthesisView.swift, VisionSynthesisContextBuilder.swift, DesignBriefReviewView.swift, DesignBriefContextBuilder.swift, DesignStudioLandingView.swift, DesignStudioSessionManager.swift, MockupAIService.swift, MockupFoundationBridge.swift, MockupHTMLWrapper.swift, MockupSession.swift, DesignMockupConversationPane.swift, MockupPreviewPane.swift.