presentation-design by jwynia/agent-skills
npx skills add https://github.com/jwynia/agent-skills --skill presentation-design设计并评估能有效传达信息的演示文稿。提供用于规划、视觉设计、认知负荷管理和评估的框架。适用于任何演示工具(reveal.js、PowerPoint、Keynote、Google Slides)。
以受众为中心的设计。 每个决策都应服务于受众的理解,而非讲者的便利。
| 问题 | 症状 | 修复方法 |
|---|---|---|
| 文字墙 | 幻灯片上全是段落 | 采用断言-证据结构 |
| 要点病 | 使用列表而非视觉元素 | 一个概念 + 视觉证据 |
| 面面俱到 | 包含所有内容 | 区分核心内容与可扩展内容 |
| 华而不实 | 设计精美但内容空洞 | 信息优先的设计 |
| 认知超载 | 每张幻灯片内容过多 | 每张幻灯片只讲一个关键概念 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
用以下内容替代要点列表:
不要这样:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
应该这样:
"User engagement increased 43% after redesign"
[Graph showing the increase]
每张幻灯片都应回答:"我希望他们从这张幻灯片中带走哪一件事?"
按顺序逐步揭示信息,而非一次性全部展示:
| 幻灯片上展示 | 口头讲述 |
|---|---|
| 关键断言 | 详细阐述 |
| 视觉证据 | 背景和解释 |
| 关键数据 | 解读 |
| 下一步 | 其重要性 |
水平幻灯片: 主要叙事流程 垂直幻灯片: 支撑细节(可选深入探讨)
示例:
将内容标记为:
| 标准 | 分数 | 备注 |
|---|---|---|
| 内容与受众知识水平匹配 | ||
| 为受众提供清晰的价值主张 | ||
| 能适应时间限制 | ||
| 导航结构有助于理解 |
危险信号:
| 标准 | 分数 | 备注 |
|---|---|---|
| 使用了断言-证据结构 | ||
| 视觉元素与文本平衡 | ||
| 视觉层次能引导注意力 | ||
| 设计元素一致 | ||
| 留白得当 |
危险信号:
| 标准 | 分数 | 备注 |
|---|---|---|
| 每张幻灯片一个关键概念 | ||
| 文本密度适中 | ||
| 动画/过渡效果使用得当 | ||
| 代码格式正确(如适用) | ||
| 支撑细节易于获取,不分散注意力 |
危险信号:
| 标准 | 分数 | 备注 |
|---|---|---|
| 适用于不同尺寸的显示屏 | ||
| 色彩对比度足够 | ||
| 使用包容性的图像和语言 | ||
| 字体大小合适 |
危险信号:
评估后:
1. 关键问题(立即修复):
2. 重要改进(第二优先级):
3. 锦上添花的优化:
模式: 每张幻灯片都塞满了未经解释或分层的图表和统计数据。失败原因: 受众无法实时处理原始数据。没有解读,他们只能自己分析而无法学习。大多数数据会立即被遗忘。修复方法: 每张幻灯片展示一个见解,并用视觉证据支持该见解。先陈述结论;再展示证据。受众应在看到数据前就理解你的观点。
模式: 幻灯片包含讲者的完整脚本——要点列表实际上是段落。失败原因: 受众阅读速度比讲者说话快。他们会提前读完,然后在你讲述他们已经读过的内容时走神。幻灯片变成了提词器,而不是沟通工具。修复方法: 幻灯片展示你无法口头表达的内容;你讲述你无法展示的内容。屏幕上展示视觉元素、图表和关键断言。口头提供背景、解释和阐述。
模式: 将内容塞进通用模板,而不考虑设计如何服务于信息。失败原因: 设计应支持理解,而不仅仅是看起来专业。通用模板产生通用沟通。一刀切无法很好地适应任何人。修复方法: 设计服务于信息。提问:什么样的视觉结构能帮助这个特定受众理解这个特定内容?从沟通需求出发,而非模板选项。
模式: 到处都是过渡、构建和特效——飞入的文字、旋转的图片、一个接一个的淡入淡出。失败原因: 动画就是注意力。每个效果都在说"看这里"。当所有东西都在动时,就没有东西突出。受众会变得不知所措或麻木。修复方法: 动画仅用于渐进式披露(逐步构建复杂想法)或强调(突出关键点)。默认不使用动画;仅在必要时有目的地添加。
模式: 一张接一张的要点列表幻灯片——所有内容的默认结构。失败原因: 要点列表适用于文档,而非演示文稿。它们鼓励对不等同的想法给予同等权重,导致文本繁多的幻灯片,以及被动阅读而非主动观看。修复方法: 使用断言-证据结构。用清晰的断言和视觉证据替代要点列表。如果你需要一个列表,请质疑它是否真的需要成为一张幻灯片。
| 技能 | 提供内容 |
|---|---|
| speech-adaptation | 与视觉内容协调的口头内容结构 |
| story-sense | 用于演示流程的叙事结构 |
| (内容专业知识) | 需要传达的主题内容 |
| 技能 | 提供内容 |
|---|---|
| (实施) | 适用于任何演示工具的设计原则 |
| (交付) | 旨在支持有效演讲的幻灯片设计 |
| 技能 | 关系 |
|---|---|
| speech-adaptation | presentation-design 处理视觉内容;speech-adaptation 处理口头内容。协同设计以实现协调 |
| voice-analysis | 了解讲者的声音有助于设计与其自然表达风格相匹配的幻灯片 |
每周安装量
685
仓库
GitHub 星标
37
首次出现
Jan 20, 2026
安全审计
安装于
opencode607
codex590
gemini-cli589
github-copilot555
cursor541
amp502
Design and evaluate presentations that communicate effectively. Provides frameworks for planning, visual design, cognitive load management, and evaluation. Applicable to any presentation tool (reveal.js, PowerPoint, Keynote, Google Slides).
Audience-centered design. Every decision should serve audience understanding, not presenter convenience.
| Problem | Symptom | Fix |
|---|---|---|
| Wall of Text | Slides are paragraphs | Assertion-evidence structure |
| Bullet Point Disease | Lists instead of visuals | One concept + visual evidence |
| Kitchen Sink | Everything included | Essential vs. expandable content |
| Pretty but Empty | Design without substance | Message-first design |
| Cognitive Overload | Too much per slide | One key concept per slide |
Replace bullet points with:
Instead of:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
Use:
"User engagement increased 43% after redesign"
[Graph showing the increase]
Each slide should answer: "What's the ONE thing I want them to take from this?"
Reveal information sequentially instead of all at once:
| Show on Slide | Speak Aloud |
|---|---|
| Key assertion | Elaboration |
| Visual evidence | Context and explanation |
| Critical data | Interpretation |
| Next step | Why it matters |
Horizontal slides: Main narrative flow Vertical slides: Supporting details (optional deep dives)
Example:
Mark content as:
| Criterion | Score | Notes |
|---|---|---|
| Content matches audience knowledge level | ||
| Clear value proposition for audience | ||
| Adaptable to time constraints | ||
| Navigation structure aids understanding |
Red Flags:
| Criterion | Score | Notes |
|---|---|---|
| Assertion-evidence structure used | ||
| Visual elements balance text | ||
| Visual hierarchy guides attention | ||
| Consistent design elements | ||
| Thoughtful whitespace |
Red Flags:
| Criterion | Score | Notes |
|---|---|---|
| One key concept per slide | ||
| Appropriate text density | ||
| Judicious animations/transitions | ||
| Code properly formatted (if applicable) | ||
| Supporting details accessible, not distracting |
Red Flags:
| Criterion | Score | Notes |
|---|---|---|
| Works across display sizes | ||
| Sufficient color contrast | ||
| Inclusive imagery and language | ||
| Font sizes appropriate |
Red Flags:
After evaluation:
1. Critical Issues (Fix immediately):
2. Important Enhancements (Second priority):
3. Nice-to-Have Refinements:
Pattern: Every slide full of data, charts, and statistics without interpretation or hierarchy. Why it fails: Audiences can't process raw data in real-time. Without interpretation, they're left doing analysis instead of learning. Most data is forgotten immediately. Fix: One insight per slide with visual evidence supporting the insight. State the conclusion; show the proof. The audience should understand your point before seeing the data.
Pattern: Slides that contain the speaker's full script—bullet points that are really paragraphs. Why it fails: Audiences read faster than speakers talk. They read ahead, then tune out when you say what they already read. The slides become teleprompter, not communication tool. Fix: Slides show what you can't say; you say what you can't show. Visuals, diagrams, and key assertions on screen. Context, explanation, and elaboration spoken.
Pattern: Dropping content into a generic template without considering how the design serves the message. Why it fails: Design should support comprehension, not just look professional. Generic templates create generic communication. One-size-fits-all fits no one well. Fix: Design serves message. Ask: what visual structure helps this specific audience understand this specific content? Start from communication need, not template options.
Pattern: Transitions, builds, and effects everywhere—flying text, spinning images, fade after fade. Why it fails: Animation is attention. Every effect says "look at this." When everything animates, nothing stands out. Audiences become overwhelmed or numbed. Fix: Animation only for progressive disclosure (building complex ideas step by step) or emphasis (highlighting the key point). Default to no animation; add only with purpose.
Pattern: Slide after slide of bullet point lists—the default structure for everything. Why it fails: Bullet points are for documents, not presentations. They encourage equal weight for unequal ideas, text-heavy slides, and passive reading instead of active viewing. Fix: Use assertion-evidence structure. Replace bullet lists with clear assertions supported by visual evidence. If you need a list, question whether it needs to be a slide.
| Skill | What it provides |
|---|---|
| speech-adaptation | Spoken content structure to coordinate with visuals |
| story-sense | Narrative structure for presentation flow |
| (content expertise) | Subject matter to communicate |
| Skill | What this provides |
|---|---|
| (implementation) | Design principles for any presentation tool |
| (delivery) | Slides designed to support effective speaking |
| Skill | Relationship |
|---|---|
| speech-adaptation | Presentation-design handles visuals; speech-adaptation handles spoken content. Design together for coordination |
| voice-analysis | Understanding the presenter's voice helps design slides that match their natural delivery style |
Weekly Installs
685
Repository
GitHub Stars
37
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode607
codex590
gemini-cli589
github-copilot555
cursor541
amp502
Python PDF处理教程:合并拆分、提取文本表格、创建PDF文件
53,300 周安装
Amazon Aurora DSQL 技能:无服务器分布式SQL数据库,支持MCP工具查询与模式管理
合作与业务拓展指南:9位产品负责人教你建立战略伙伴关系,达成业务交易
656 周安装
企业级智能体运维指南:云端AI系统生命周期管理、可观测性与安全控制
657 周安装
Amazon Aurora DSQL 技能:无服务器分布式 SQL 数据库管理与 MCP 工具集成
SQL查询优化指南:PostgreSQL、Snowflake、BigQuery高性能SQL编写技巧与方言参考
657 周安装
Gemini Live API 开发指南:实时语音视频交互、WebSockets集成与SDK使用
657 周安装