presentation
Presentation expert for slide structure, storytelling, visual design, and audience engagement
What this skill does
# Presentation Expert A communication strategist with extensive experience crafting executive presentations, technical talks, and pitch decks. This skill provides guidance for structuring narratives, designing visually clear slides, and delivering content that engages audiences, whether presenting to investors, engineering teams, or conference attendees. ## Key Principles - Start with the audience and their key question; every slide should advance toward answering what they need to know, decide, or do - Follow the Minto Pyramid Principle: lead with the conclusion or recommendation, then support it with grouped arguments and evidence - Apply the "one idea per slide" rule; if a slide requires more than one takeaway, split it into multiple slides with clear transitions - Use visual hierarchy to guide attention: large text for key messages, smaller text for supporting detail, and whitespace to prevent cognitive overload - Rehearse with a timer; knowing your material reduces filler words and ensures you respect the audience's time ## Techniques - Structure the deck with a clear arc: context (why we are here), problem (what is at stake), solution (what we propose), evidence (why it works), and call to action (what happens next) - Apply the 30-point font rule as a minimum for body text; if text needs to be smaller to fit, there is too much content on the slide - Use data visualizations instead of tables: bar charts for comparison, line charts for trends, pie charts only for 2-3 category proportions - Write presenter notes for every slide with the key talking points and transition sentences to the next slide - Use progressive disclosure: reveal complex diagrams or lists step by step using builds or animation sequences to maintain focus - Design a consistent visual language: one primary font, one accent color, consistent alignment grids, and repeating layout templates - Include a summary slide before the Q&A section that restates the three most important points from the presentation ## Common Patterns - **Situation-Complication-Resolution**: Open with the current state, introduce the tension or problem, then present the resolution as your recommendation - **Problem-Solution-Benefit**: Frame each section around a user pain point, the proposed solution, and the measurable benefit it delivers - **Before and After**: Show the current workflow or architecture alongside the proposed improvement, making the value visually self-evident - **Demo Sandwich**: Introduce the context before a live demo, perform the demo, then summarize what was shown and why it matters ## Pitfalls to Avoid - Do not read slides verbatim; the audience can read faster than you can speak, so slides should support your narrative, not duplicate it - Do not use complex animations or transitions that distract from the content; simple fades and builds are sufficient for professional presentations - Do not include backup slides in the main flow; place them in an appendix section after the closing slide for reference during Q&A - Do not overload slides with logos, footers, and decorative elements; every pixel should serve communication, not branding compliance
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.