educational-presentation
Transform Claude into an expert in evidence-based educational presentation design. Use when designing presentations for teaching, training, or learning contexts where retention and comprehension matter. Applies Cognitive Load Theory, Mayer's 12 Principles of Multimedia Learning, Gagné's 9 Events of Instruction, C.R.A.P. design principles, and WCAG 2.1 AA accessibility standards. Triggers on requests to (1) create educational or training presentations, (2) design slides for teaching or workshops, (3) improve existing educational presentations, (4) convert content into visual presentations, (5) ensure accessible and inclusive presentations, or (6) apply learning science to presentation design.
What this skill does
# Educational Presentation Design Transform any presentation into a cognitively-optimized learning tool based on evidence from learning science. ## Core Philosophy: Minimize Cognitive Load **Prime Directive**: Every design decision must serve learning by: 1. Reducing extraneous load (eliminate distractions) 2. Managing intrinsic load (chunk complex content) 3. Optimizing germane load (maximize mental resources for actual learning) **Critical Rule**: If a design element doesn't directly support learning, remove it. --- ## Essential Principles (Non-Negotiable) ### Mayer's 3 Most Critical Principles #### 1. Coherence Principle ⭐ MOST IMPORTANT **Rule**: Exclude all extraneous material - no decorative clipart, busy backgrounds, or irrelevant details. **Application**: Every slide element must have a clear instructional purpose. #### 2. Redundancy Principle ⭐ CRITICAL **Rule**: Do NOT put paragraphs of text on slides that will be read aloud. **Why**: Creates "cognitive channel war" - audience can't read and listen simultaneously. **Solution**: - Visuals + narration = GOOD ✅ - Visuals + text wall + narration = COGNITIVE OVERLOAD ❌ - Move all paragraph text to speaker notes - Slides should have: keywords, graphics, or charts only #### 3. Segmenting Principle ⭐ ESSENTIAL **Rule**: Break content into user-paced chunks using progressive disclosure or multiple slides. **Application**: Never overwhelm with one dense slide - chunk across 3-5 slides instead. **For all 12 Mayer principles with detailed applications**, read [`references/quick-reference.md`](references/quick-reference.md). --- ## Macro-Structure: Gagné's 9 Events Framework Every educational presentation MUST follow this structure: ### Event 1: Gain Attention - Thought-provoking question, surprising statistic, or compelling case study - Stimulates curiosity and focus ### Event 2: Inform Learners of Objectives - "By the end of this session, you will be able to..." - Use measurable action verbs (Analyze, Compare, Apply, Evaluate, Create) ### Event 3: Stimulate Recall of Prior Learning - Poll question: "What do you already know about X?" - Activates existing knowledge as foundation ### Event 4: Present the Content - Main content slides with visuals + narration (not text walls) - Break into digestible 3-5 minute chunks - Apply progressive disclosure ### Event 5: Provide Learning Guidance - Worked examples, non-examples, analogies, case studies - Graphic organizers and mnemonics ### Event 6: Elicit Performance - "Try this problem" or "Discuss with your neighbor" - Interactive quiz or application exercise (non-graded) ### Event 7: Provide Feedback - Correct answer with explanation - Model of ideal response and common mistakes to avoid ### Event 8: Assess Performance - Formal quiz, project prompt, or final presentation request - Measures if objective was met ### Event 9: Enhance Retention and Transfer - Final summary and transfer question: "How will you use this in your work?" - Real-world problem to solve **For detailed templates for each event**, read [`references/slide-templates.md`](references/slide-templates.md). --- ## Micro-Design: C.R.A.P. Principles ### 1. Contrast Create visual hierarchy with strong differences: - Large title (36-44pt) vs. smaller body (24-32pt) - Bright accent color on neutral background - Bold vs. regular weight ### 2. Repetition Reuse same fonts, colors, and layouts: - Consistent title placement - Same color palette on every slide - Maximum 2 fonts for entire deck ### 3. Alignment Nothing is placed arbitrarily: - Use invisible grid (turn on guides) - Left-align body text (never center paragraphs) - Connect every element to another ### 4. Proximity Group related items close together: - Place labels directly next to graphics - Use whitespace to separate unrelated groups **For detailed C.R.A.P. applications**, read [`references/quick-reference.md`](references/quick-reference.md). --- ## Typography & Color Essentials ### Typography Rules - **Font Choice**: Sans-serif only (Arial, Calibri, Verdana, Helvetica) - **Size**: Main Title 36-44pt, Body Text 24-32pt minimum - **Alignment**: Left-align all body text, never center - **Emphasis**: Use bold, never underline or ALL CAPS ### Color Strategy **60-30-10 Rule**: - 60% Primary (neutral background: white, off-white, dark gray) - 30% Secondary (structural elements: title bars, sidebars) - 10% Accent (key words, buttons, arrows - bright, contrasting) **Accessibility (WCAG 2.1 AA)**: - 4.5:1 contrast ratio for normal text - 3:1 contrast ratio for large text (18pt+) - Never use red/green or blue/yellow combinations **Tools**: WebAIM Contrast Checker, Adobe Color, Coolors --- ## Visual Elements & Multimedia ### Images & Icons - ✅ High-quality, relevant photographs - ✅ Professional icons (Noun Project, Flaticon, Iconoir) - ✅ Icons can replace bullet points - ❌ No decorative clipart or "seductive details" ### Charts & Diagrams - Simplify to one clear message per chart - Use progressive disclosure for complex diagrams - Label directly on elements (not separate legend) **Free Legal Resources**: - Images: Unsplash, Wikimedia Commons - Icons: Noun Project, Flaticon, Iconoir --- ## Progressive Disclosure & Animations ### When to Use - 3+ bullet points or list items - Complex diagrams or processes - Step-by-step explanations ### How to Implement **PowerPoint**: Animations > Add Animation > Appear > Effect Options: On Click **Google Slides**: Insert > Animation > Appear/Fade In > On Click **Critical Rules**: - Use "Appear" or "Fade" only (no distracting effects) - Set to "On Click" not "After Previous" - Build diagrams piece-by-piece --- ## Accessibility (WCAG 2.1 AA) ### Must-Have Requirements 1. **Alt text** on all images and charts 2. **Contrast** meets 4.5:1 ratio (verify with tools) 3. **Built-in layouts** (don't use text boxes floating arbitrarily) 4. **Reading order** checked and corrected 5. **Color independence** (don't rely on color alone for meaning) ### Tools **PowerPoint**: File > Info > Check for Issues > Check Accessibility **Google Slides**: Grackle Slides add-on **For complete accessibility checklist**, read [`references/validation.md`](references/validation.md). --- ## Common Mistakes to Avoid ### ❌ The Bullet Point Slide of Death **Problem**: 8+ bullet points with full sentences, presented all at once **Fix**: Chunk across 3-4 slides, one clear message per slide, use progressive disclosure ### ❌ The Text Wall **Problem**: Paragraphs of text on slide while presenter reads aloud **Fix**: Move ALL paragraph text to speaker notes, leave only keywords/graphics ### ❌ The Clipart Catastrophe **Problem**: Generic clipart that doesn't illustrate the concept **Fix**: Use high-quality, relevant photographs or professional icons ### ❌ The Overwhelming Diagram **Problem**: Complex flowchart revealed all at once **Fix**: Build piece-by-piece using progressive disclosure ### ❌ The Centered Everything **Problem**: All text centered on slide **Fix**: Left-align all body text, use invisible grid **For detailed before/after transformations**, read [`references/before-after.md`](references/before-after.md). --- ## Workflow: Creating a Presentation ### Step 1: Plan the Structure (5-10 minutes) 1. Define learning objectives (measurable action verbs) 2. Outline using Gagné's 9 Events framework 3. Identify key concepts that need pre-training 4. Plan practice opportunities and feedback ### Step 2: Create Content Slides (30-60 minutes) 1. Start with slide titles (one clear idea per slide) 2. Add relevant visuals first (not as decoration) 3. Add minimal text (keywords only, not sentences) 4. Write detailed speaker notes (what you'll say) 5. Apply C.R.A.P. principles consistently ### Step 3: Implement Progressive Disclosure (10-20 minutes) 1. Identify slides with 3+ items 2. Add "Appear" animations set to "On Click" 3. Test flow and timing ### Step 4: Validate Before Delivery (10-
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.