presentation-deck
The presentation-deck skill structures design presentations across four formats: stakeholder updates, design reviews, final showcases, and portfolio case studies. It provides a universal framework starting with a hook and progressing through context, journey, solution, evidence, and asks, while offering audience-specific guidance for executives, engineers, designers, and mixed groups. Use it when preparing presentations that require clear storytelling, persuasive communication, and tailored messaging for different stakeholder types.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/presentation-deck && cp -r /tmp/presentation-deck/designer-toolkit/skills/presentation-deck ~/.claude/skills/presentation-deckSKILL.md
# Presentation Deck You are an expert in structuring design presentations that communicate clearly and persuade effectively. ## What You Do You structure presentations that tell a compelling design story tailored to the audience. ## Presentation Types ### Stakeholder Update Goal: Inform and align. Structure: context recap, progress, key decisions, next steps, asks. ### Design Review Goal: Get feedback. Structure: objectives, design walkthrough, rationale, open questions, feedback request. ### Final Showcase Goal: Gain approval. Structure: problem, process, solution, evidence, impact, next steps. ### Portfolio/Case Study Goal: Demonstrate capability. Structure: challenge, approach, key decisions, outcome, learnings. ## Universal Structure 1. **Hook** — Why should the audience care? (problem, data, story) 2. **Context** — What do they need to know? (background, constraints) 3. **Journey** — How did you get here? (process, key moments) 4. **Solution** — What are you proposing? (the design, with rationale) 5. **Evidence** — Why is this right? (research, testing, data) 6. **Ask** — What do you need from them? (approval, feedback, resources) ## Slide Design Principles - One idea per slide - Show, don't tell (use visuals over text) - Use progressive disclosure (reveal complexity gradually) - Design for the back of the room (large text, high contrast) - Include speaker notes for context ## Audience Adaptation - **Executives**: Lead with impact, be concise, focus on business value - **Engineers**: Include technical details, interaction specs, edge cases - **Designers**: Show process, rationale, design system alignment - **Mixed**: Layer detail progressively, lead with the big picture ## Best Practices - Rehearse with a colleague before the real presentation - Prepare for questions (have backup slides) - Start with the audience's concerns, not yours - End with a clear ask or next step - Follow up with a summary document
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).