presentation-design▌
jwynia/agent-skills · updated Apr 28, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Audience-centered presentation design framework covering planning, visual strategy, cognitive load, and evaluation.
- ›Provides assertion-evidence structure to replace bullet points with clear claims supported by visual evidence, reducing cognitive overload
- ›Includes four evaluation phases: audience and content planning, visual strategy, cognitive load management, and structure patterns with scoring rubrics
- ›Covers five common anti-patterns (data dumps, script reading, template traps, ani
Presentation Design Diagnostic
Purpose
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).
Core Principle
Audience-centered design. Every decision should serve audience understanding, not presenter convenience.
Quick Reference: Common Problems
| 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 |
Phase 1: Audience & Content Planning
Key Questions
- Who specifically is my audience? What's their knowledge level?
- What's the ONE main message? What should they remember?
- What are 3-5 supporting points? How do they reinforce the message?
- What evidence supports each point? Visual, data, examples?
- What action should they take? What's the call to action?
- What are time constraints? What's essential vs. optional?
Actions
- Create audience persona(s)
- Write one-sentence main message
- Organize supporting points in logical flow
- Identify evidence for each point
- Define essential vs. expandable content
- Sketch presentation flow
Phase 2: Visual Strategy
Assertion-Evidence Structure
Replace bullet points with:
- Assertion: Clear, complete sentence stating the point
- Evidence: Visual that supports the assertion
Instead of:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
Use:
"User engagement increased 43% after redesign"
[Graph showing the increase]
Visual Principles
- Limited palette: 3-5 colors maximum
- Typography hierarchy: 2-3 fonts with clear roles
- Whitespace: Let content breathe
- Consistency: Same layouts, same treatment
- Visual progress: Help audience track where they are
Phase 3: Cognitive Load Management
One Concept Per Slide
Each slide should answer: "What's the ONE thing I want them to take from this?"
Progressive Disclosure
Reveal information sequentially instead of all at once:
- Show initial state
- Add first element with context
- Add second element building on first
Spoken vs. Shown
| Show on Slide | Speak Aloud |
|---|---|
| Key assertion | Elaboration |
| Visual evidence | Context and explanation |
| Critical data | Interpretation |
| Next step | Why it matters |
Code Examples (Technical Talks)
- Syntax highlighting always
- Highlight the critical line
- Build up complex examples
- Remove boilerplate when possible
Phase 4: Structure Patterns
Horizontal vs. Vertical (Multi-Level Navigation)
Horizontal slides: Main narrative flow Vertical slides: Supporting details (optional deep dives)
Example:
- Horizontal: "Three Key Factors in Customer Retention"
- Vertical (under that): Detailed slide for each factor
Time Flexibility
Mark content as:
- Essential: Must cover in any version
- Standard: Include with normal time
- Expandable: Include only with extra time
Evaluation Framework
1. Audience-Centered Design (Rate 1-5)
| Criterion | Score | Notes |
|---|---|---|
| Content matches audience knowledge level | ||
| Clear value proposition for audience | ||
| Adaptable to time constraints | ||
| Navigation structure aids understanding |
Red Flags:
- Presenter-focused rather than audience-focused
- No consideration of audience's existing knowledge
2. Visual Clarity (Rate 1-5)
| Criterion | Score | Notes |
|---|---|---|
| Assertion-evidence structure used | ||
| Visual elements balance text | ||
| Visual hierarchy guides attention | ||
| Consistent design elements | ||
| Thoughtful whitespace |
Red Flags:
- Bullet-point overuse
- Text-heavy slides
- Cluttered layouts
3. Cognitive Load (Rate 1-5)
| 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:
- Multiple complex concepts per slide
- Excessive text competing with speech
- Animation overuse
4. Accessibility (Rate 1-5)
| Criterion | Score | Notes |
|---|---|---|
| Works across display sizes | ||
| Sufficient color contrast | ||
| Inclusive imagery and language | ||
| Font sizes appropriate |
Red Flags:
- Poor contrast
- Too-small fonts
- Non-inclusive content
Implementation Checklist
Structure
- Main message clear in first 2 minutes
- Supporting points organized logically
- Essential vs. expandable content marked
- Navigation aids understanding
Content
- Assertion-evidence structure used
- Visual evidence supports assertions
- One concept per slide
- Code examples properly formatted
Visual
- Consistent color palette
- Typography hierarchy
- Sufficient whitespace
- Elements aligned
Accessibility
- Color contrast verified
- Font sizes appropriate
- Alternative text for key images
Improvement Prioritization
After evaluation:
1. Critical Issues (Fix immediately):
- Blocks audience understanding
- Accessibility failures
- Core message unclear
2. Important Enhancements (Second priority):
- Cognitive load issues
- Visual consistency problems
- Structure improvements
3. Nice-to-Have Refinements:
- Advanced animations
- Custom styling
- Polish details
Anti-Patterns
1. The Data Dump
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.
2. The Script Reader
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.
3. The Template Trap
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.
4. The Animation Circus
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.
5. The Bullet Point Disease
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.
Integration
Inbound (feeds into this skill)
| 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 |
Outbound (this skill enables)
| Skill | What this provides |
|---|---|
| (implementation) | Design principles for any presentation tool |
| (delivery) | Slides designed to support effective speaking |
Complementary
| 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 |
How to use presentation-design on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add presentation-design
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches presentation-design from GitHub repository jwynia/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate presentation-design. Access the skill through slash commands (e.g., /presentation-design) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★27 reviews- ★★★★★Mateo Patel· Dec 28, 2024
Solid pick for teams standardizing on skills: presentation-design is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Dec 16, 2024
I recommend presentation-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Arya Robinson· Nov 27, 2024
Registry listing for presentation-design matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ama Martinez· Nov 19, 2024
presentation-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Yash Thakker· Nov 7, 2024
Useful defaults in presentation-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Maya Gonzalez· Nov 7, 2024
Keeps context tight: presentation-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Oct 26, 2024
presentation-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Zaid Farah· Oct 26, 2024
presentation-design has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Valentina Zhang· Oct 18, 2024
presentation-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ama Zhang· Oct 10, 2024
Keeps context tight: presentation-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 27