From creator-skills
Comprehensive guide for creating effective academic presentation slides for STEM fields. Use this skill when users ask to create scientific presentations, review slide design, need guidance on slide content density, bullet point limits, text vs visuals, equation presentation, figure adaptation, or want to avoid common presentation mistakes. Applies to conference talks, lab meetings, journal clubs, and all academic presentation contexts.
npx claudepluginhub aeghnnsw/cc-toolkit --plugin creator-skillsThis skill uses the workspace's default tool permissions.
Evidence-based guidelines for creating effective academic presentations in STEM that respect cognitive principles and enhance audience comprehension.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
Evidence-based guidelines for creating effective academic presentations in STEM that respect cognitive principles and enhance audience comprehension.
This skill provides research-backed guidance for creating scientific presentation slides that communicate complex STEM content effectively. The guidelines are grounded in cognitive load theory, multimedia learning research, and empirical studies of presentation effectiveness.
Key insight: 100% of analyzed academic presentations violated basic cognitive principles. Following evidence-based guidelines provides significant competitive advantage while better serving scientific communication.
When to use this skill:
Replace topic headings with full-sentence assertions that state findings.
Traditional approach (avoid):
Evidence-based approach:
Why this works:
Rule: Each slide should communicate ONE clear message supported by visual evidence, not bullet points.
| Element | Specification |
|---|---|
| Minimum size | 24 pt (28 pt for challenging conditions) |
| Font family | Sans-serif only (Arial, Helvetica, Calibri) |
| Contrast | Dark gray text on white backgrounds |
Test: Every slide must be readable from the farthest seat in the presentation room.
| Element | Maximum |
|---|---|
| Lines per slide | 6-9 lines |
| Bulleted items per list | 5 items |
| Lines per bullet | 2 lines |
| Words per bullet | 2-10 words (not complete sentences) |
Key principle: Audiences read faster than speakers talk. Text-heavy slides create unsolvable cognitive conflict.
Critical distinction: Journal figures can include extensive detail because readers control viewing duration. Presentation figures must communicate key findings in seconds.
Adaptation workflow:
Common error: Copying complex multi-panel figures directly from papers into slides. Audiences lack time to decipher them.
Strongly prefer graphs (processed 60,000x faster than text)
Use graphs for:
Reserve tables only for: Exact numerical lookup requirements
Do:
Avoid:
Golden rule: Only include equations explicitly explained during the presentation.
Best practices:
For short talks: Minimize equation density. Displaying complex equations without decomposition and explanation fails to communicate.
Key constraint: Humans can hold only 3-4 chunks of information simultaneously in working memory.
Implication: Text-heavy slides + narration = cognitive overload on the same mental resources.
Solution: Employ dual modality by combining visual graphics (processed by visual channel) with auditory narration (processed by verbal channel).
After three days:
Mayer's Key Principles:
Problem: Creates cognitive conflict - audiences read in 10 seconds, then face boredom or divided attention.
Solution: Limit to 6-9 lines maximum, or replace with visual evidence.
Problem: Signals poor preparation; written prose sounds pompous when read aloud.
Solution: Use conversational language in delivery; slides should support, not script, the talk.
Problems:
Solution: Test readability from the farthest seat. Never present unreadable content.
Problem: "Seductive details" (clip art, background patterns, sound effects) interfere with message retention. Audiences remember decoration instead of findings.
Solution: Remove all elements that don't convey scientific information.
Problem: Using jargon or acronyms without definition, even at specialized conferences.
Solution: Define technical terms on first use. Mixed expertise levels exist in all audiences.
When helping users create or review scientific presentations:
A well-designed scientific presentation: