presentation-design
Design and evaluate presentations that communicate effectively. Use when designing a presentation, creating slides, getting presentation feedback, structuring a talk, or reviewing slides. Keywords: presentation, slides, talk, PowerPoint, Keynote, reveal.js.
What this skill does
# Presentation Design Diagnostic ## Purpose Design and evaluate presentations that communicate effectively. Provides frameworks for planning, visual design, cognitive load management, and evaluation. Applicable to any presentation tool (reveal.js, PowerPoint, Keynote, Google Slides). ## Core Principle **Audience-centered design.** Every decision should serve audience understanding, not presenter convenience. --- ## Quick Reference: Common Problems | Problem | Symptom | Fix | |---------|---------|-----| | Wall of Text | Slides are paragraphs | Assertion-evidence structure | | Bullet Point Disease | Lists instead of visuals | One concept + visual evidence | | Kitchen Sink | Everything included | Essential vs. expandable content | | Pretty but Empty | Design without substance | Message-first design | | Cognitive Overload | Too much per slide | One key concept per slide | --- ## Phase 1: Audience & Content Planning ### Key Questions 1. **Who specifically is my audience?** What's their knowledge level? 2. **What's the ONE main message?** What should they remember? 3. **What are 3-5 supporting points?** How do they reinforce the message? 4. **What evidence supports each point?** Visual, data, examples? 5. **What action should they take?** What's the call to action? 6. **What are time constraints?** What's essential vs. optional? ### Actions - [ ] Create audience persona(s) - [ ] Write one-sentence main message - [ ] Organize supporting points in logical flow - [ ] Identify evidence for each point - [ ] Define essential vs. expandable content - [ ] Sketch presentation flow --- ## Phase 2: Visual Strategy ### Assertion-Evidence Structure **Replace bullet points with:** - **Assertion:** Clear, complete sentence stating the point - **Evidence:** Visual that supports the assertion **Instead of:** ``` Key findings: • Data shows increase • Users engaged more • Revenue improved ``` **Use:** ``` "User engagement increased 43% after redesign" [Graph showing the increase] ``` ### Visual Principles - **Limited palette:** 3-5 colors maximum - **Typography hierarchy:** 2-3 fonts with clear roles - **Whitespace:** Let content breathe - **Consistency:** Same layouts, same treatment - **Visual progress:** Help audience track where they are --- ## Phase 3: Cognitive Load Management ### One Concept Per Slide Each slide should answer: "What's the ONE thing I want them to take from this?" ### Progressive Disclosure Reveal information sequentially instead of all at once: 1. Show initial state 2. Add first element with context 3. Add second element building on first ### Spoken vs. Shown | Show on Slide | Speak Aloud | |---------------|-------------| | Key assertion | Elaboration | | Visual evidence | Context and explanation | | Critical data | Interpretation | | Next step | Why it matters | ### Code Examples (Technical Talks) - Syntax highlighting always - Highlight the critical line - Build up complex examples - Remove boilerplate when possible --- ## Phase 4: Structure Patterns ### Horizontal vs. Vertical (Multi-Level Navigation) **Horizontal slides:** Main narrative flow **Vertical slides:** Supporting details (optional deep dives) Example: - Horizontal: "Three Key Factors in Customer Retention" - Vertical (under that): Detailed slide for each factor ### Time Flexibility Mark content as: - **Essential:** Must cover in any version - **Standard:** Include with normal time - **Expandable:** Include only with extra time --- ## Evaluation Framework ### 1. Audience-Centered Design (Rate 1-5) | Criterion | Score | Notes | |-----------|-------|-------| | Content matches audience knowledge level | | | | Clear value proposition for audience | | | | Adaptable to time constraints | | | | Navigation structure aids understanding | | | **Red Flags:** - Presenter-focused rather than audience-focused - No consideration of audience's existing knowledge ### 2. Visual Clarity (Rate 1-5) | Criterion | Score | Notes | |-----------|-------|-------| | Assertion-evidence structure used | | | | Visual elements balance text | | | | Visual hierarchy guides attention | | | | Consistent design elements | | | | Thoughtful whitespace | | | **Red Flags:** - Bullet-point overuse - Text-heavy slides - Cluttered layouts ### 3. Cognitive Load (Rate 1-5) | Criterion | Score | Notes | |-----------|-------|-------| | One key concept per slide | | | | Appropriate text density | | | | Judicious animations/transitions | | | | Code properly formatted (if applicable) | | | | Supporting details accessible, not distracting | | | **Red Flags:** - Multiple complex concepts per slide - Excessive text competing with speech - Animation overuse ### 4. Accessibility (Rate 1-5) | Criterion | Score | Notes | |-----------|-------|-------| | Works across display sizes | | | | Sufficient color contrast | | | | Inclusive imagery and language | | | | Font sizes appropriate | | | **Red Flags:** - Poor contrast - Too-small fonts - Non-inclusive content --- ## Implementation Checklist ### Structure - [ ] Main message clear in first 2 minutes - [ ] Supporting points organized logically - [ ] Essential vs. expandable content marked - [ ] Navigation aids understanding ### Content - [ ] Assertion-evidence structure used - [ ] Visual evidence supports assertions - [ ] One concept per slide - [ ] Code examples properly formatted ### Visual - [ ] Consistent color palette - [ ] Typography hierarchy - [ ] Sufficient whitespace - [ ] Elements aligned ### Accessibility - [ ] Color contrast verified - [ ] Font sizes appropriate - [ ] Alternative text for key images --- ## Improvement Prioritization After evaluation: **1. Critical Issues (Fix immediately):** - Blocks audience understanding - Accessibility failures - Core message unclear **2. Important Enhancements (Second priority):** - Cognitive load issues - Visual consistency problems - Structure improvements **3. Nice-to-Have Refinements:** - Advanced animations - Custom styling - Polish details --- ## Anti-Patterns ### 1. The Data Dump **Pattern:** Every slide full of data, charts, and statistics without interpretation or hierarchy. **Why it fails:** Audiences can't process raw data in real-time. Without interpretation, they're left doing analysis instead of learning. Most data is forgotten immediately. **Fix:** One insight per slide with visual evidence supporting the insight. State the conclusion; show the proof. The audience should understand your point before seeing the data. ### 2. The Script Reader **Pattern:** Slides that contain the speaker's full script—bullet points that are really paragraphs. **Why it fails:** Audiences read faster than speakers talk. They read ahead, then tune out when you say what they already read. The slides become teleprompter, not communication tool. **Fix:** Slides show what you can't say; you say what you can't show. Visuals, diagrams, and key assertions on screen. Context, explanation, and elaboration spoken. ### 3. The Template Trap **Pattern:** Dropping content into a generic template without considering how the design serves the message. **Why it fails:** Design should support comprehension, not just look professional. Generic templates create generic communication. One-size-fits-all fits no one well. **Fix:** Design serves message. Ask: what visual structure helps this specific audience understand this specific content? Start from communication need, not template options. ### 4. The Animation Circus **Pattern:** Transitions, builds, and effects everywhere—flying text, spinning images, fade after fade. **Why it fails:** Animation is attention. Every effect says "look at this." When everything animates, nothing stands out. Audiences become overwhelmed or numbed. **Fix:** Animation only for progressive disclosure (building complex ideas step by step) or emphasis (highlighting the key point). Default to no animation; add only with purpose. ### 5. The Bullet Point Disease **Pattern:** Sli
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.