演示文稿

设计与多媒体 社区

技能解读

当前原文的自动摘译,尚未人工审校。

你做什么

您构建演示文稿,讲述为观众量身定制的引人入胜的设计故事。

利益相关者更新

目标:通知并协调。结构:背景回顾、进展、关键决策、后续步骤、询问。

设计评审

目标:获得反馈。结构:目标、设计演练、基本原理、开放性问题、反馈请求。

最终展示

目标:获得认可。结构:问题、过程、解决方案、证据、影响、后续步骤。

作品集/案例研究

目标:展示能力。结构:挑战、方法、关键决策、成果、经验教训。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
设计与多媒体
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@Owl-Listener · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
需简单配置
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
  • 命令执行
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.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

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。