presentation deck
- Repo stars 1,440
- Author repo designer-skills
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @Owl-Listener · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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
Sections and files
Listed in source order.
sections -> What You Do → Presentation Types → Stakeholder Update → Design Review → Final Showcase → Portfolio/Case Study
terms -> Hook · Context · Journey · Solution · Evidence · Ask · Executives · Engineers
files/cmd -> Portfolio/Case
body sha256 -> c81069da902c
What You Do
You structure presentations that tell a compelling design story tailored to the audience.
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.