Presentation Design
This skill should be used when the user asks to "design a presentation", "structure presentation content", "improve presentation flow", "create presentation outline", "make slides more engaging", or needs guidance on storytelling, visual hierarchy, audience engagement, or presentation best practices.
What this skill does
# Presentation Design Effective presentations combine research-backed design principles, storytelling, and audience understanding. Create compelling narratives that engage audiences and communicate ideas clearly. **Research Basis**: These guidelines are based on cognitive load studies (Miller's Law), TED presentation research, MIT Communication Lab recommendations, and analysis of effective technical conference talks. They prevent common mistakes that make presentations hard to follow. See `references/presentation-best-practices.md` for detailed research citations. ## HARD LIMITS (Never Violate) These are research-backed **maximum limits** that should NEVER be exceeded. If content exceeds these limits, you MUST split into multiple slides: ๐ด **MAX 6 elements** per slide (bullets + images + diagrams + code blocks combined) ๐ด **MAX 50 words** body text per slide (excluding title) ๐ด **MAX 1-2 code blocks** per slide (8-10 lines each) ๐ด **ONE idea** per slide (if multiple ideas โ split slides) **Why these are hard limits:** - Cognitive load research: >6 elements exponentially increases audience confusion - Reading vs listening interference: >50 words means audience stops listening - Code complexity: >2 code examples creates comparison overhead **When content doesn't fit:** - โ **NEVER** compress or shrink to fit - โ **NEVER** reduce font size below 18pt - โ **ALWAYS** split into additional slides - โ **ALWAYS** move details to presenter notes or backup slides ## Core Principles ### 1. One Idea Per Slide **Critical Rule**: Each slide communicates exactly ONE central idea, finding, or question. **Why this matters:** - Prevents cognitive overload - Maintains audience focus - Enables clear narrative progression **In practice:** - If a slide requires >2 minutes to explain โ split it - Each slide title should state one clear point - No tangential information on slides - Content supports only the title's assertion **Example:** - โ Bad: One "Background" slide covering problem + impact + existing solutions - โ Good: Three slides โ "Problem X costs $Y annually" โ "Existing solutions fail at scale" โ "No current approach handles edge case Z" ### 2. Meaningful Titles (Assertions, Not Labels) **Critical Rule**: Slide titles should state the TAKEAWAY, not just the topic. **Why this matters:** - Titles act as "topic sentences" for slides - Reading titles in sequence tells the story - Helps distracted audience members catch up - Prevents speaker from losing train of thought **Format:** Use complete assertion (subject + verb + finding), not one-word labels **Examples:** - โ Weak: "Results" / "Background" / "Thermal Images" - โ Strong: "Experiment X demonstrates 2x performance gain" / "Current solutions fail under high-load conditions" / "Thermal images show electronics overheating" **Validation**: Could audience understand main point from title alone? ### 3. Cognitive Load Management **Critical Rule**: Limit distinct elements to ~6 items per slide maximum. **Scientific basis:** - Working memory: 7ยฑ2 items (Miller's Law) - David JP Phillips research: >6 objects exponentially increases cognitive load **Elements to count:** 1. Bullet points 2. Images/photos 3. Diagrams 4. Text blocks 5. Charts/graphs 6. Callout boxes **If >6 elements needed:** Use progressive builds, split across slides, or simplify ### 4. Design for the Distracted Viewer **Critical Rule**: Each slide must convey its message even if viewer doesn't hear your narration. **Why this matters:** - Audience zones out momentarily (long sessions, after lunch) - Slides may be reviewed later without audio - Someone glancing mid-explanation should grasp the point **Implementation:** - Meaningful title + clear visual = standalone message - Highlight conclusions, not just raw data - Use annotations (arrows, labels) to guide attention - Don't bury insights in details **Test**: Show slide to someone without context. Can they identify main point in 5 seconds? ### 5. Minimal Text (Keywords, Not Sentences) **Critical Rule**: Aside from title, use short phrases. Slides are visual aids, not scripts. **Why this matters:** - Audience cannot read and listen simultaneously (dual-channel interference) - Reading text aloud loses engagement - Text should guide, not duplicate speech **Guidelines:** - Word count per slide (excluding title): <50 words - No paragraphs or full sentences in body - Bullets are phrases, not complete sentences - **Detailed text belongs in presenter notes** **Example:** - โ Good: "Key benefits: โข 40% faster โข 2x throughput โข Zero downtime" - โ Bad: "The key benefits of this approach are that it is 40% faster than the previous solution, provides twice the throughput, and enables zero-downtime deployments." ### 6. Backup Slides Strategy **Rule**: Prepare "backup" slides for Q&A, but keep separate from main deck. **What to include:** - Detailed data tables - Extended methodology - Statistical details - Alternative approaches considered - Related work comparison **Benefits:** - Keeps main presentation focused - Maintains timing discipline - Shows thoroughness without cluttering talk **Implementation:** Place after "Questions?" slide, don't count toward timing ## Presentation Structure ### Three-Act Structure Every presentation follows a narrative arc: **Act 1: Setup** (15-20% of time) - Hook the audience immediately - State the problem or opportunity - Establish credibility - Preview what's coming **Act 2: Confrontation** (60-70% of time) - Present main content - Build tension or complexity - Provide evidence and examples - Address counterarguments **Act 3: Resolution** (15-20% of time) - Synthesize key points - Provide clear takeaways - Call to action - Leave lasting impression ### Slide Sequence Pattern ``` 1. Title/Cover - Who, what, when 2. Hook - Compelling question or statistic 3. Problem - Why this matters 4. Agenda - What to expect 5-N. Content - Main material N+1. Summary - Key takeaways N+2. Next Steps - What to do N+3. Q&A - Questions ``` ## Storytelling Principles ### Start with Why Lead with purpose, not process: โ **Wrong:** ``` Slide 1: About Our Company Slide 2: Our Technology Slide 3: How It Works Slide 4: Why You Should Care ``` โ **Right:** ``` Slide 1: The Problem Everyone Faces Slide 2: Why Current Solutions Fail Slide 3: Our Approach Slide 4: How It Works ``` ### Use Concrete Examples Abstract concepts need grounding: โ **Abstract:** "Our platform improves efficiency by 50%" โ **Concrete:** "Sarah used to spend 4 hours on reports. Now it takes 2 hours." ### Create Contrast Highlight differences to make points memorable: - Before vs After - Problem vs Solution - Old Way vs New Way - Competitor vs Us ## Visual Hierarchy ### Text Density Guidelines **Title slides:** 5-7 words maximum **Content slides:** 20-30 words maximum **Data slides:** Let visualizations speak, minimal text **The 6x6 rule:** - Maximum 6 bullet points per slide - Maximum 6 words per bullet - If you need more, split into multiple slides ### Typography **Heading sizes:** - H1 (Title): 44-60pt - H2 (Section): 32-40pt - H3 (Subsection): 24-28pt - Body text: 18-24pt **Font choices:** - Sans-serif for screens (Arial, Helvetica, Open Sans) - Limit to 2 font families maximum - Use font weight for hierarchy (bold for emphasis) ### Color Strategy **Color roles:** - Primary: Main brand color (headlines, key elements) - Secondary: Supporting color (accents, highlights) - Neutral: Background and body text (black, white, gray) - Accent: Call-to-action, warnings (sparingly) **Contrast ratios:** - Text on background: Minimum 4.5:1 ratio - Large text (>24pt): Minimum 3:1 ratio - Test readability from back of room ### White Space Empty space is not wasted space: - Margins: Minimum 10% of slide on all sides - Between elements: At least 20-30px - Around text blocks: Breathing room improves comprehension - Resist urge to fill every pixel ## Slide Types ### Data Slides
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.