presentation-deck — Claude Code skill: structure a design deck
The skill lays out a design presentation around one audience and one decision, from hook to the ask. Handy before an internal design review.
npx skills add Owl-Listener/designer-skills --skill presentation-deck -a claude-codeWhat presentation-deck does
The skill gives you a structure and picks it by the goal of the talk. A stakeholder update runs context recap, progress, key decisions, next steps and asks. A design review runs objectives, a design walkthrough, rationale, open questions and a feedback request. A final showcase runs problem, process, solution, evidence, impact and next steps.
There is also a universal six-part sequence: hook, context, journey, solution, evidence, ask. Slide rules cover one idea per slide, visuals over text, progressive disclosure, large text for the back of the room and speaker notes. Audience adaptation is spelled out too: lead with impact for executives, add interaction specs and edge cases for engineers, show process and design system alignment for designers.
Reach for it when the deck goes to your own team or a client. For a portfolio narrative the author points to case-study, and for the written argument to design-rationale. Install runs through npx skills add, and the skill file lands at ~/.claude/skills/presentation-deck/SKILL.md.
What it helps with
- shape a stakeholder update deck
- prepare a design review with open questions
- build a final showcase with evidence and impact
- adapt one deck for executives and engineers
- plan speaker notes and backup slides for Q&A
Example prompts for the agent
- structure my design review deck for Friday
- build a final showcase: problem, process, solution, evidence, impact, next steps
- draft a stakeholder update with key decisions and next steps
How to install presentation-deck
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill presentation-deck -a claude-code2Manually: put the files in place
~/.claude/skills/presentation-deck/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/presentation-deck/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill presentation-deck -a codex2Manually: put the files in place
.agents/skills/presentation-deck/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill presentation-deck -a cursor2Manually: put the files in place
.cursor/skills/presentation-deck/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills presentation-deck2Manually: put the files in place
.github/skills/presentation-deck/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill presentation-deck -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path designer-toolkit/skills/presentation-deckManually: put the files in place
.devin/skills/presentation-deck/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill presentation-deck -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about presentation-deck
How do I install presentation-deck in Claude?
Run npx skills add Owl-Listener/designer-skills --skill presentation-deck -a claude-code. The skill file lands at ~/.claude/skills/presentation-deck/SKILL.md.
What does presentation-deck do?
It structures a design presentation for a specific audience and decision: presentation types, a universal six-part outline and slide design rules.
How is presentation-deck different from case-study and design-rationale?
The author points to case-study for a portfolio narrative and to design-rationale for the written argument. presentation-deck is for presenting internally.
Source text
SKILL.md · MIT
--- 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
© Owl-Listener · MIT · Owl-Listener/designer-skills
