Skip to content
Design
Skill

/presentation-deck

Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.

BOOST
From plugin
designer-skills
2.9k111 skills33 commands
Install
$ npx -y skills add Owl-Listener/designer-skills --skill presentation-deck --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/presentation-deck

Context preview

The summary Claude sees to decide when to auto-load this skill.

Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.

SKILL.md

presentation-deck.SKILL.md
name: presentation-deck
description: Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.

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
Read more
Ships withdesigner-skills

Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?

Get the whole plugin

Other skills on designer-skills.