agentleFS
joaoguirunasjoaoguirunas/team-os/.claude/skills/presentation-design/SKILL.md

presentation-design

Skill6 starsChanged 2 days agoMITView on GitHub

Desenhar e avaliar apresentações que comunicam bem. Use ao desenhar uma apresentação, criar slides, pedir feedback, estruturar uma palestra ou revisar slides (presentation, slides, talk, PowerPoint, Keynote, reveal.js).

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chart-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AvinavaSkill

    chart-design

    Design honest, accessible charts of quantitative data as inline SVG — bar and column charts, line and time series, limit ledgers, distributions, scatter plots, small multiples, and waterfall bridges. Use when visualizing measured values, choosing a chart type, picking or fixing chart colors, building a categorical palette from design tokens, setting axes and scales, labelling series, or making an existing chart readable in grayscale and in print. Do not use for diagrams of structure or process such as architecture or flows (use diagram-design), for the surrounding report narrative and metric semantics (use analytical-document-design), or for interactive dashboards that require a client-side charting library.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Audience-centered design: Every decision should serve audience understanding, not presenter convenience.

    line 23
  2. Distinctive:

    Add first element with context

    line 103
  3. Distinctive:

    Add second element building on first

    line 104
  4. Distinctive:

    Remove boilerplate when possible

    line 120
  5. Distinctive:

    Essential: Must cover in any version

    line 138
  6. Distinctive:

    No consideration of audience's existing knowledge

    line 157
  7. Distinctive:

    Pattern: Every slide full of data, charts, and statistics without interpretation or hierarchy.

    line 256
  8. Distinctive:

    Fix: Use assertion-evidence structure.

    line 278

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

ProblemSymptomFix
Wall of TextSlides are paragraphsAssertion-evidence structure
Bullet Point DiseaseLists instead of visualsOne concept + visual evidence
Kitchen SinkEverything includedEssential vs. expandable content
Pretty but EmptyDesign without substanceMessage-first design
Cognitive OverloadToo much per slideOne key concept per slide

Phase 1: Audience & Content Planning

Key Questions

  1. Who specifically is my audience? What's their knowledge level?
  2. What's the ONE main message? What should they remember?
  3. What are 3-5 supporting points? How do they reinforce the message?
  4. What evidence supports each point? Visual, data, examples?
  5. What action should they take? What's the call to action?
  6. 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:

  1. Show initial state
  2. Add first element with context
  3. Add second element building on first

Spoken vs. Shown

Show on SlideSpeak Aloud
Key assertionElaboration
Visual evidenceContext and explanation
Critical dataInterpretation
Next stepWhy 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)

CriterionScoreNotes
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)

CriterionScoreNotes
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)

CriterionScoreNotes
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)

CriterionScoreNotes
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)

SkillWhat it provides
speech-adaptationSpoken content structure to coordinate with visuals
story-senseNarrative structure for presentation flow
(content expertise)Subject matter to communicate

Outbound (this skill enables)

SkillWhat this provides
(implementation)Design principles for any presentation tool
(delivery)Slides designed to support effective speaking

Complementary

SkillRelationship
speech-adaptationPresentation-design handles visuals; speech-adaptation handles spoken content. Design together for coordination
voice-analysisUnderstanding the presenter's voice helps design slides that match their natural delivery style

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.