Slide Quality Assessment
This skill should be used when the user asks to "analyze slide quality", "review slide", "check slide design", "optimize slide", "improve slide content", "assess slide clarity", or needs evidence-based quality evaluation using the 12-point checklist for presentation slides.
What this skill does
# Slide Quality Assessment
Evaluate presentation slides using evidence-based quality criteria grounded in cognitive load research, accessibility standards, and presentation best practices from TED, MIT Communication Lab, and technical conference guidelines.
**Research Foundation**: Quality assessment based on working memory limits (Miller's Law), David JP Phillips' cognitive load studies, WCAG accessibility standards, and analysis of effective technical presentations.
**IMPORTANT**: Before analyzing slides, use the Read tool to load the style guide from the plugin directory:
```
${CLAUDE_PLUGIN_ROOT}/references/presentation-best-practices.md
```
This contains the complete research-backed guidelines and validation criteria supporting the 12-point checklist.
## The 12-Point Quality Checklist
Use this systematic framework to evaluate any presentation slide:
### 1. ✓ One Idea Per Slide (CRITICAL)
**Criterion**: Does the slide communicate exactly ONE central idea, finding, or question?
**Why this matters**:
- Prevents cognitive overload
- Maintains audience focus during narration
- Enables clear narrative progression
**How to assess**:
- Can slide be explained in ~90 seconds?
- Does all content support only the title's assertion?
- Are there multiple unrelated concepts?
**Red flags**:
- ✗ Covering multiple independent topics
- ✗ Requires >2 minutes to explain
- ✗ Content diverges from title
**Fix**: Split into multiple slides, one concept each
---
### 2. ✓ Meaningful Title (CRITICAL)
**Criterion**: Is the title an assertion (subject + verb + finding) rather than a label?
**Why this matters**:
- Titles act as "topic sentences"
- Reading titles in sequence tells the story
- Helps distracted viewers catch up
- Audience should understand main point from title alone
**Good vs Bad**:
- ❌ Bad (labels): "Results", "Background", "Performance"
- ✅ Good (assertions): "Experiment X demonstrates 2x gain", "Current solutions fail at scale"
**How to assess**:
- Does title state a takeaway (not just a topic)?
- Subject + verb + finding format?
- Would titles in sequence tell a coherent story?
**Fix**: Convert labels to complete assertions
---
### 3. ✓ Element Count ≤6 (CRITICAL)
**Criterion**: Total distinct elements ≤6 (bullets + images + diagrams + charts + code blocks)
**Why this matters**:
- Working memory: 7±2 items (Miller's Law)
- >6 elements exponentially increases cognitive load (Phillips research)
- Audience cannot process >6 simultaneous information chunks
**What counts as elements**:
- Each bullet point = 1
- Each image/diagram = 1
- Each code block = 1
- Each chart/graph = 1
- Nested bullets count separately
**Exceptions**:
- Progressive builds (v-click) revealing elements incrementally = OK
- Diagrams with integrated labels (count as 1 if cohesive)
**How to assess**:
Count all visual and textual chunks the audience must process simultaneously
**Red flags**:
- ✗ 8+ bullet points
- ✗ Multiple diagrams + bullets
- ✗ Dense content without progressive disclosure
**Fix**: Reduce elements, split slides, or use v-click for progressive builds
---
### 4. ✓ Word Count <50 (CRITICAL)
**Criterion**: Body text <50 words (excluding title)
**Why this matters**:
- Audience cannot read and listen simultaneously
- >50 words = audience stops listening to speaker
- Slides support speaker, not replace them
**How to assess**:
- Count all words excluding title
- Include bullet text, captions, labels
- Exclude code (assess separately)
**Red flags**:
- ✗ Full sentences in bullets
- ✗ Paragraph text
- ✗ Long explanatory captions
**Fix**:
- Convert sentences to phrases (3-6 words per bullet)
- Move detailed explanations to presenter notes
- Split content across multiple slides
---
### 5. ✓ Visual Element Present
**Criterion**: At least one visual element (diagram, chart, image, code, or graphic)
**Why this matters**:
- Dual-channel processing (visual + audio) improves retention
- Visuals convey complex relationships better than text
- Almost never text-only slides
**Exceptions allowing text-only**:
- Quote slides
- Definition slides
- Bold statements for emphasis
- Section dividers
**How to assess**:
Is there a diagram, chart, image, code block, or other visual?
**Red flags**:
- ✗ Only title + bullets
- ✗ Dense text without supporting visual
- ✗ Missed opportunity for diagram
**Fix**: Add mermaid diagram, chart, image, or code example
---
### 6. ✓ Font Sizes (Body ≥18pt, Heading ≥24pt)
**Criterion**: Body text ≥18pt, headings ≥24pt (accessibility requirement)
**Why this matters**:
- WCAG accessibility standards
- Readability from back of room
- Accommodates vision impairments
**How to assess**:
- Check Slidev theme defaults
- Verify no custom CSS reducing sizes
- Test: Can text be read from 20 feet away?
**Red flags**:
- ✗ Tiny code fonts (<14pt)
- ✗ Compressed text to fit content
- ✗ Caption text <16pt
**Fix**: Use proper font sizes, split slides if content doesn't fit
---
### 7. ✓ Contrast Ratio (≥4.5:1)
**Criterion**: Text contrast ≥4.5:1 for normal text, ≥3:1 for large text (>24pt)
**Why this matters**:
- WCAG Level AA accessibility requirement
- Readability under projection conditions
- Accommodates vision impairments
**How to assess**:
- Check dark text on light backgrounds (or inverse)
- Avoid: gray-on-gray, yellow-on-white, light-blue-on-white
- Test: Is text clearly readable at a glance?
**Red flags**:
- ✗ Low-contrast color schemes
- ✗ Light text on light backgrounds
- ✗ Colored text without sufficient contrast
**Fix**: Use high-contrast color pairs, test with contrast checker
---
### 8. ✓ Colorblind-Safe (Not Color-Only)
**Criterion**: Meaning not conveyed by color alone (use patterns, labels, shapes)
**Why this matters**:
- ~8% of males have color vision deficiency
- Projected colors appear differently than on screen
- Print/grayscale versions must be understandable
**How to assess**:
- Can information be understood in grayscale?
- Are chart lines distinguished by style (solid/dashed) not just color?
- Do diagrams use labels, not just color coding?
**Red flags**:
- ✗ "Green = good, red = bad" without labels
- ✗ Chart with only color-differentiated lines
- ✗ Diagrams relying solely on color
**Fix**: Add patterns, labels, shapes, or text alongside color
---
### 9. ✓ Standalone Comprehension
**Criterion**: Can viewer grasp main point from title + visual alone (without narration)?
**Why this matters**:
- Distracted viewers can catch up mid-presentation
- Slides work for async review
- Conclusions highlighted, not buried
**How to assess**:
- 5-second test: Show slide without context - is point clear?
- Does visual reinforce the title's assertion?
- Could someone skimming slides get the story?
**Red flags**:
- ✗ Title + content don't align
- ✗ Visual unrelated to title
- ✗ Requires full narration to understand
**Fix**: Strengthen title-visual connection, add clarifying labels
---
### 10. ✓ Phrases Not Sentences
**Criterion**: Bullets are short phrases (3-6 words), not full sentences
**Why this matters**:
- Prevents audience from reading ahead
- Keeps focus on speaker
- Avoids reading-while-listening conflict
- Garr Reynolds principle: slides support, don't replace speaker
**Good vs Bad**:
- ❌ Bad: "Kubernetes orchestrates containerized applications across a cluster of machines"
- ✅ Good: "Container orchestration across clusters"
**How to assess**:
Are bullets short keyword phrases or full grammatical sentences?
**Red flags**:
- ✗ Bullets with periods at the end
- ✗ Multi-clause sentences
- ✗ Explanatory prose in bullets
**Fix**: Extract keywords, move details to presenter notes
---
### 11. ✓ White Space (≥10% Margins)
**Criterion**: Adequate white space around content (≥10% margins, well-distributed)
**Why this matters**:
- Prevents claustrophobic feeling
- Improves visual hierarchy
- Directs attention to content
- Professional appearance
**How to assess**:
- Is content distributed across slideRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.