marp-slide

davila7/claude-code-templates · updated Apr 15, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/davila7/claude-code-templates --skill marp-slide
0 commentsdiscussion
summary

Create professional, visually appealing Marp presentation slides with 7 pre-designed themes and built-in best practices.

skill.md

Marp Slide Creator

Create professional, visually appealing Marp presentation slides with 7 pre-designed themes and built-in best practices.

When to Use This Skill

Use this skill when the user:

  • Requests to create presentation slides or Marp documents
  • Asks to "make slides look good" or "improve slide design"
  • Provides vague instructions like "良い感じにして" (make it nice) or "かっこよく" (make it cool)
  • Wants to create lecture or seminar materials
  • Needs bullet-point focused slides with occasional images

Quick Start

Step 1: Select Theme

First, determine the appropriate theme based on the user's request and content.

Quick theme selection:

  • Technical/Developer content → tech theme
  • Business/Corporate → business theme
  • Creative/Event → colorful or gradient theme
  • Academic/Simple → minimal theme
  • General/Unsure → default theme
  • Dark background preferred → dark or tech theme

For detailed theme selection guidance, read references/theme-selection.md.

Step 2: Create Slides

  1. Read relevant references first:

    • Always start by reading references/marp-syntax.md for basic syntax
    • For images: references/image-patterns.md (official Marpit image syntax)
    • For advanced features (math, emoji): references/advanced-features.md
    • For custom themes: references/theme-css-guide.md
  2. Copy content from the appropriate template file:

    • assets/template-basic.md - Default theme (most common)
    • assets/template-minimal.md - Minimal theme
    • assets/template-colorful.md - Colorful theme
    • assets/template-dark.md - Dark mode theme
    • assets/template-gradient.md - Gradient theme
    • assets/template-tech.md - Tech/code theme
    • assets/template-business.md - Business theme
  3. Read references/best-practices.md for quality guidelines

  4. Structure content following best practices:

    • Title slide with <!-- _class: lead -->
    • Concise h2 titles (5-7 characters in Japanese)
    • 3-5 bullet points per slide
    • Adequate whitespace
  5. Add images if needed using patterns from references/image-patterns.md

  6. Save to the project output directory with .md extension

Available Themes

1. Default Theme

Colors: Beige background, navy text, blue headings Style: Clean, sophisticated with decorative lines Use for: General seminars, lectures, presentations Template: template-basic.md

2. Minimal Theme

Colors: White background, gray text, black headings Style: Minimal decoration, wide margins, light fonts Use for: Content-focused presentations, academic talks Template: template-minimal.md

3. Colorful & Pop Theme

Colors: Pink gradient background, multi-color accents Style: Vibrant gradients, bold fonts, rainbow accents Use for: Youth-oriented events, creative projects Template: template-colorful.md

4. Dark Mode Theme

Colors: Black background, cyan/purple accents Style: Dark theme with glow effects, eye-friendly Use for: Tech presentations, evening talks, modern look Template: template-dark.md

5. Gradient Background Theme

Colors: Purple/pink/blue/green gradients (varies per slide) Style: Different gradient per slide, white text, shadows Use for: Visual-focused, creative presentations Template: template-gradient.md

6. Tech/Code Theme

Colors: GitHub-style dark background, blue/green accents Style: Code fonts, Markdown-style headers with # symbols Use for: Programming tutorials, tech meetups, developer content Template: template-tech.md

7. Business Theme

Colors: White background, navy headings, blue accents Style: Corporate presentation style, top border, table support Use for: Business presentations, proposals, reports Template: template-business.md

Creating Slides Process

Basic Workflow

  1. Understand requirements

    • Identify content: title, topics, key points
    • Determine target audience
    • Assess formality level
  2. Select theme

    • Use quick selection rules above
    • If uncertain, consult references/theme-selection.md
    • Default to default theme if still unsure
  3. Apply template

    • Load appropriate template from assets/
    • CSS is already embedded - no external files needed
    • Maintain template structure
  4. Structure content

    • Title slide: <!-- _class: lead --> + h1
    • Content slides: h2 title + bullet points
    • Keep titles to 5-7 characters (Japanese)
    • Use 3-5 bullet points per slide
  5. Refine quality

    • Read references/best-practices.md
    • Ensure adequate whitespace
    • Maintain consistency
    • Keep text concise (15-25 chars per line)
  6. Add images

    • If needed, consult references/image-patterns.md
    • Common: ![bg right:40%](image.png) for side images
    • Use proper Marp image syntax
  7. Output file

    • Save to the project output directory
    • Use descriptive filename like presentation.md

Handling "Make It Look Good" Requests

When users give vague instructions like "良い感じにして", "かっこよく", or "make it cool":

  1. Infer theme from content:

    • Business content → business theme
    • Technical content → tech or dark theme
    • Creative content → gradient or colorful theme
    • General → default theme
  2. Apply best practices automatically:

    • Shorten titles to 5-7 characters
    • Limit bullet points to 3-5 items
    • Add adequate whitespace
    • Use consistent structure
  3. Enhance visual hierarchy:

    • Use h3 for sub-sections when appropriate
    • Break up dense text into multiple slides
    • Ensure logical flow (intro → body → conclusion)
  4. Maintain professional tone:

    • Match formality to content
    • Use parallel structure in lists
    • Keep technical terms consistent

Image Integration

For slides with images, consult references/image-patterns.md for detailed syntax.

Common patterns:

  • Side image: ![bg right:40%](image.png) - Image on right, text on left
  • Centered: ![w:600px](image.png) - Centered with specific width
  • Full background: ![bg](image.png) - Full-screen background
  • Multiple images: Multiple ![bg] declarations

Example lecture pattern:

## Slide Title

![bg right:40%](diagram.png)

- Explanation point 1
- Explanation point 2
- Explanation point 3

File Output

Always save the final Marp file to the project output directory with .md extension:

  • presentation.md
  • seminar-slides.md
  • lecture-materials.md

Quality Checklist

Before delivering slides, verify:

  • Theme selected appropriately for content
  • CSS theme is embedded in the file
  • Title slide uses <!-- _class: lead -->
  • All h2 titles are concise (5-7 chars)
  • Bullet points are 3-5 items per slide
  • Images use proper Marp syntax
  • File saved to outputs directory
  • Content follows best practices

References

Core Documentation

  • Marp syntax: references/marp-syntax.md - Basic Marp/Marpit syntax (directives, frontmatter, pagination, etc.)
  • Image patterns: references/image-patterns.md - Official image syntax (bg, filters, split backgrounds)
  • Theme CSS guide: references/theme-css-guide.md - How to create custom themes based on Marpit specification
  • Advanced features: references/advanced-features.md - Math, emoji, fragmented lists, Marp CLI, VS Code
  • Official themes: references/official-themes.md - default, gaia, uncover themes documentation

Quality & Selection Guides

  • Theme selection: references/theme-selection.md - How to choose the right theme for content
  • Best practices: references/best-practices.md - Quality guidelines for "cool" slides

Templates & Assets

  • Templates: assets/template-*.md - Starting points with embedded CSS for each theme (7 themes)
  • Standalone CSS: assets/theme-*.css - CSS files for reference (already embedded in templates)

Official External Links

how to use marp-slide

How to use marp-slide on Cursor

AI-first code editor with Composer

1

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 marp-slide
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/davila7/claude-code-templates --skill marp-slide

The skills CLI fetches marp-slide from GitHub repository davila7/claude-code-templates and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/marp-slide

Reload or restart Cursor to activate marp-slide. Access the skill through slash commands (e.g., /marp-slide) 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

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.552 reviews
  • Diya Srinivasan· Dec 20, 2024

    Useful defaults in marp-slide — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ava Diallo· Dec 16, 2024

    marp-slide has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Dev Thomas· Dec 12, 2024

    We added marp-slide from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Yash Thakker· Dec 8, 2024

    Useful defaults in marp-slide — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mia Haddad· Dec 8, 2024

    marp-slide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mia Garcia· Nov 27, 2024

    marp-slide has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Dev Jackson· Nov 7, 2024

    marp-slide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Meera Thomas· Nov 3, 2024

    Solid pick for teams standardizing on skills: marp-slide is focused, and the summary matches what you get after install.

  • William Diallo· Oct 26, 2024

    We added marp-slide from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ama Srinivasan· Oct 22, 2024

    marp-slide has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 52

1 / 6