Slide Docs - Presentation Review and Creation

Overview

Comprehensive review and creation support for Markdown-based presentation slides. Evaluate slide quality across storytelling, visual design, message clarity, and presentation effectiveness. Apply industry best practices with actionable improvements.

Tool-Specific Syntax: Use Context7 MCP for up-to-date documentation:

• •Marp: /marp-team/marp-cli (64 snippets, score 82.6)
• •reveal.js: /hakimel/reveal.js (131 snippets, score 94.5)
• •Deckset: /websites/deckset_english_lproj (96 snippets, score 71.1)

5-Level Quality Assessment

⭐⭐⭐⭐⭐ (5/5) Excellent

• •Perfect storytelling with compelling narrative
• •Visually stunning and professional
• •Clear, memorable messaging
• •Professional-grade quality

⭐⭐⭐⭐☆ (4/5) Good

• •Strong narrative structure
• •Visually well-organized
• •Clear messaging
• •Minor improvements only

⭐⭐⭐☆☆ (3/5) Standard

• •Basic structure present
• •Visually acceptable
• •Message communicated
• •Several improvements needed

⭐⭐☆☆☆ (2/5) Needs Improvement

• •Structural issues present
• •Visual improvements needed
• •Unclear messaging
• •Significant revisions required

⭐☆☆☆☆ (1/5) Requires Reconstruction

• •Broken narrative flow
• •Multiple visual problems
• •Message unclear
• •Complete overhaul needed

Evaluation Criteria

1. Slide Structure

• •Clear narrative arc: Introduction → body → conclusion
• •Logical flow: Ideas progress naturally
• •One message per slide: Each slide communicates single concept
• •Appropriate slide count: Total number relative to presentation length
• •Section clarity: Clear delineation of major sections

2. Content and Messaging

• •Conciseness: Short, impactful statements (6×6 rule: max 6 lines, 6 words/line)
• •Impact: Memorable phrases, effective data presentation
• •Readability: Adequate font size (minimum 24pt body), color contrast, whitespace
• •Key point emphasis: Important information stands out
• •Clear call-to-action: Explicit next steps

3. Visual Design

• •Visual hierarchy: Clear title/body distinction, consistent layout
• •Image quality: High-resolution, professional images with proper attribution
• •Color design: Limited palette (3-4 colors), brand consistency, accessibility
• •Balance and alignment: Proper positioning, embrace whitespace

4. Technical Elements

• •Code display: Syntax highlighting, readable font size, key section emphasis
• •Data visualization: Appropriate chart selection, clear labeling, purposeful animation
• •Asset management: Verified paths, consistent encoding (UTF-8)

5. Presentation Utility

• •Speaker support: Comprehensive notes, timing indicators, Q&A preparation
• •Audience consideration: Technical term definitions, cultural awareness, accessibility

Review Workflow

1. •Assess overall structure: Evaluate narrative flow and organization
2. •Review each slide: Check individual slide quality
3. •Evaluate visual design: Assess consistency and aesthetics
4. •Check technical elements: Verify code, data, media
5. •Test presentation utility: Review speaker notes and audience considerations
6. •Provide rating: Assign 5-level quality score per category
7. •Suggest improvements: Offer specific, actionable recommendations
8. •Prioritize changes: Identify critical vs. optional improvements

Creation Workflow

1. •Understand objectives: Clarify purpose and audience
2. •Outline structure: Plan narrative arc (Rule of three: focus on 3 main points)
3. •Draft content: Create slide content following best practices
4. •Design visuals: Apply consistent, professional design
5. •Add speaker notes: Provide comprehensive presenter guidance
6. •Review and iterate: Evaluate against quality criteria
7. •Prepare for delivery: Finalize timing and transitions

Common Issues and Quick Fixes

Structural Problems

• •Issue: Lack of clear narrative, illogical flow
• •Fix: Establish clear beginning/middle/end, add transition slides

Visual Problems

• •Issue: Text too small, information overload, inconsistent design
• •Fix: Increase font sizes (≥24pt), one-message-per-slide, consistent template

Message Problems

• •Issue: Unclear main points, excessive jargon, no call-to-action
• •Fix: Emphasize key messages, define technical terms, include explicit next steps

Technical Problems

• •Issue: Broken layouts, missing images, encoding errors
• •Fix: Test on target platform, verify asset paths, use UTF-8 consistently

Best Practices Summary

• •Start with "why": Begin with problem statement
• •Rule of three: Focus on three main points
• •Story arc: Follow clear narrative structure
• •End with action: Conclude with specific next steps
• •High-resolution assets: Use quality images
• •Embrace whitespace: Avoid cluttered slides
• •Minimal animation: Use sparingly and purposefully
• •Rehearse thoroughly: Practice delivery multiple times

Integration with Context7 MCP

For tool-specific syntax and features, query Context7 directly:

Example queries:

- "Marp markdown syntax for slides, themes, and directives"
- "reveal.js markdown syntax and configuration"
- "Deckset markdown syntax and slide customization"
- "Code highlighting in [tool-name]"
- "Custom backgrounds and transitions in [tool-name]"

Always verify syntax with Context7 when working with specific presentation tools to ensure up-to-date, accurate implementation details.