educational-presentation
정보
이 스킬은 클로드를 학습 기억력과 이해도를 극대화하는 교육용 프레젠테이션 설계 전문가로 변환합니다. 이는 훈련 슬라이드를 제작하거나 개선할 때 인지 부하 이론과 접근성 표준과 같은 근거 기반 프레임워크를 자동으로 적용합니다. 교재, 워크숍 설계 또는 콘텐츠를 효과적인 시각적 프레젠테이션으로 전환하는 모든 요청에 사용하세요.
빠른 설치
Claude Code
추천npx skills add guia-matthieu/clawfu-skills -a claude-code/plugin add https://github.com/guia-matthieu/clawfu-skillsgit clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/educational-presentationClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
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:
- Reducing extraneous load (eliminate distractions)
- Managing intrinsic load (chunk complex content)
- 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.
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.
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.
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
- Alt text on all images and charts
- Contrast meets 4.5:1 ratio (verify with tools)
- Built-in layouts (don't use text boxes floating arbitrarily)
- Reading order checked and corrected
- 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.
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.
Workflow: Creating a Presentation
Step 1: Plan the Structure (5-10 minutes)
- Define learning objectives (measurable action verbs)
- Outline using Gagné's 9 Events framework
- Identify key concepts that need pre-training
- Plan practice opportunities and feedback
Step 2: Create Content Slides (30-60 minutes)
- Start with slide titles (one clear idea per slide)
- Add relevant visuals first (not as decoration)
- Add minimal text (keywords only, not sentences)
- Write detailed speaker notes (what you'll say)
- Apply C.R.A.P. principles consistently
Step 3: Implement Progressive Disclosure (10-20 minutes)
- Identify slides with 3+ items
- Add "Appear" animations set to "On Click"
- Test flow and timing
Step 4: Validate Before Delivery (10-15 minutes)
- Run accessibility checker
- Verify contrast ratios
- Check reading order
- Confirm all images have alt text
- Test on actual presentation screen
For comprehensive validation checklist (174 points), read references/validation.md.
Decision Trees
"Should I put this text on the slide?"
Will I read this text aloud?
├─ YES → Move to speaker notes ✅
│ (Use visual + keyword only on slide)
└─ NO → Consider keeping on slide
├─ Is it a keyword/label? → Keep ✅
├─ Is it a technical term that must be referenced? → Keep ✅
└─ Is it a full sentence/paragraph? → Move to notes ✅
"Which chart should I use?"
What's your data story?
├─ Comparing categories → Bar/Column chart
├─ Showing trend over time → Line graph
├─ Part-to-whole relationship → Pie/Donut (max 5 slices)
└─ Correlation between variables → Scatter plot
Quick Validation Checklist
Before delivering, verify:
Structure ✓
- Follows Gagné's 9 Events framework
- Clear learning objectives stated
- Includes practice opportunity and feedback
Cognitive Load ✓
- No slide has more than one main idea
- Complex content is chunked appropriately
- All decorative elements removed (Coherence)
- No text walls + narration (Redundancy)
Design ✓
- Strong contrast creates clear hierarchy
- Consistent repetition throughout
- All elements aligned on grid
- Generous whitespace on every slide
Typography ✓
- Sans-serif fonts used
- Maximum 2 fonts
- All text minimum 24pt
- Body text left-aligned
Color ✓
- 60-30-10 rule applied
- All text meets 4.5:1 contrast ratio
- No red/green or blue/yellow combinations
Multimedia ✓
- Every slide has words AND pictures
- High-quality, relevant images only
- Labels placed next to graphics
Interaction ✓
- Progressive disclosure applied where appropriate
- Animations set to "On Click"
- "Appear" or "Fade" only
Accessibility ✓
- Alt text on all images/charts
- Built-in layouts used
- Contrast ratios verified
Key Mantras
- "If it doesn't support learning, delete it." (Coherence Principle)
- "Visual + narration, not visual + text + narration." (Redundancy Principle)
- "One slide, one idea." (Segmenting Principle)
- "Clean isn't empty; clean is focused." (Whitespace)
- "Beautiful is efficient." (Cognitive Load Theory)
- "Design for everyone or design for no one." (Accessibility)
Reference Files Guide
This skill includes detailed reference files for specific needs:
references/quick-reference.md
Use when: You need rapid decisions during creation or want a scannable checklist Contains:
- 30-second checklist
- Mayer's 12 in 12 seconds
- Gagné's 9 in 9 slides
- C.R.A.P. in 4 questions
- Typography rules express
- Color 60-30-10 rule
- Progressive disclosure guide
- Accessibility 5 must-haves
- Top 5 errors to avoid
- Chart selection guide
references/slide-templates.md
Use when: You want ready-to-use templates for specific slide types Contains:
- 20+ templates organized by Gagné's 9 Events
- Opening slides (3 templates)
- Objectives, Recall, Content, Guidance templates
- Practice, Feedback, Assessment templates
- Transfer/Application templates
- Special slides (Section Divider, Summary, Q&A, Thank You, References)
- Selection guide for each template
references/before-after.md
Use when: You want to see concrete transformations or understand common mistakes Contains:
- 6 major transformation examples
- Cognitive analysis of problems
- Step-by-step solutions applied
- C.R.A.P.-Mayer scoring for validation
- Visual comparisons showing improvements
references/validation.md
Use when: You need comprehensive pre-delivery validation Contains:
- 174-point complete validation checklist
- 13 evaluation sections with scoring
- Pedagogical Structure (20 pts)
- Mayer Principles (24 pts)
- C.R.A.P. Design (16 pts)
- Typography, Colors, Visuals (40 pts)
- Animations, Whitespace, Accessibility (36 pts)
- Content, Duration, Storytelling, Consistency (38 pts)
- Scoring system: 95-100% = Excellence, 85-94% = Very Good, 70-84% = Acceptable, <70% = Rework needed
Implementation with Technical Tools
PowerPoint/Google Slides
When creating presentations in PowerPoint or Google Slides:
- Apply these principles manually
- Use built-in accessibility checkers
- Verify contrast with WebAIM or Coolors
- Test progressive disclosure animations
Creating with Claude (pptx skill)
When Claude needs to create actual .pptx files:
- This skill provides the pedagogical design and content structure
- The
pptxskill provides the technical implementation (html2pptx, python-pptx) - Use this skill first to design, then pptx skill to build
Workflow:
- Use educational-presentation skill to plan structure and content
- Create detailed slide outlines with speaker notes
- Use pptx skill to implement the technical file creation
- Return to this skill for final validation
Core Theories & Further Reading
Foundational Theories:
- Cognitive Load Theory (Sweller)
- Mayer's Cognitive Theory of Multimedia Learning
- Gagné's Nine Events of Instruction
- Bloom's Taxonomy
Design Principles:
- Robin Williams' C.R.A.P. Principles
- WCAG 2.1 Accessibility Guidelines
Recommended Books:
- "Presentation Zen" by Garr Reynolds
- "Slide:ology" by Nancy Duarte
- "Multimedia Learning" by Richard E. Mayer
Summary: Start Here
New to educational presentations? Follow this path:
- Read this SKILL.md file completely (15 minutes)
- Review
references/quick-reference.md(10 minutes) - Start creating with
references/slide-templates.md(5 minutes per template) - Validate with checklist above before delivery
Improving existing presentations? Follow this path:
- Read
references/before-after.mdto identify common mistakes (30 minutes) - Apply transformations to your slides
- Validate with
references/validation.md(15-30 minutes)
Quick reference during creation? Keep references/quick-reference.md open
Remember: Beautiful presentations are cognitively efficient presentations. Every design choice should serve learning, not just aesthetics.
What Claude Does vs What You Decide
| Claude handles | You provide |
|---|---|
| Applying Gagné's 9 Events structure | Learning objectives and content |
| Enforcing Mayer's 12 Principles | Domain expertise and examples |
| Checking accessibility (WCAG 2.1 AA) | Visual design preferences |
| Suggesting progressive disclosure | Pacing and delivery style |
| Running validation checklist | Final approval and refinement |
Skill Boundaries
This skill excels for:
- Training and educational presentations
- Workshop and course materials
- Learning-focused content where retention matters
- Accessible presentation design
This skill is NOT ideal for:
- Sales pitch decks → Different structure needed
- Entertainment presentations → Engagement over retention
- Infographics → Static design, not progressive
Iteration Guide
| Pass | Focus | Action |
|---|---|---|
| 1st | Structure | Apply Gagné's 9 Events framework |
| 2nd | Cognitive Load | Check Coherence, Redundancy, Segmenting |
| 3rd | Design | Apply C.R.A.P. principles |
| 4th | Accessibility | Run WCAG checklist |
Skill Metadata
name: educational-presentation
category: content
subcategory: presentations
version: 2.0
author: GUIA
source_expert: Richard Mayer, Robert Gagné, Robin Williams
source_work: Multimedia Learning, Conditions of Learning, The Non-Designer's Design Book
difficulty: intermediate
mode: cyborg
tags: [presentation, education, training, cognitive-load, mayer, gagne, accessibility]
created: 2026-02-03
updated: 2026-02-03
GitHub 저장소
연관 스킬
content-collections
메타이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
polymarket
메타이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
creating-opencode-plugins
메타이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
sglang
메타SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
