feat: add marp-slides skill to orbitant-marketing

[kevinccbsg]

Summary

Add a new orbitant-marp-slides skill to the orbitant-marketing plugin that enables anyone (dev or non-dev) to create professional presentations using Markdown with the @orbitant/marp-theme package and Claude.

Motivation

Creating presentations is a recurring task across the company — knowledge sharing sessions, client decks, internal updates, conference talks. Today this requires PowerPoint skills or design knowledge. With a Marp skill, anyone can describe what they want and get a brand-consistent slide deck generated as a simple .md file.

This lowers the barrier to creating polished Orbitant-branded presentations to near zero.

Proposed Skill Structure

plugins/orbitant-marketing/skills/marp-slides/
├── SKILL.md                      # Core instructions for Claude
├── README.md                     # Human setup guide (npm install, .marprc.yml)
└── references/
    ├── marp-theme-guide.md       # Available slide classes, frontmatter, layout options
    └── design-system.md          # Orbitant brand: colors, typography, gradients, do's/don'ts

Skill Capabilities

The skill should enable Claude to:

1. Create presentations from scratch — given a topic, outline, or rough idea, generate a complete .md slide deck
2. Convert raw material into slides — meeting notes, Slack threads, documents, bullet points → structured presentation
3. Use correct Marp theme classes — title, section, accent, light, cols, index, lead, end
4. Apply Orbitant brand guidelines — content structure that aligns with the visual rhythm (dark/light alternation, gradient moments for key phrases, technical credibility tone)
5. Handle setup — guide users on installing @orbitant/marp-theme + @marp-team/marp-cli and configuring .marprc.yml if not already present
6. Output ready-to-render files — the .md file should work immediately with npx marp --preview

Trigger Phrases

The skill description should cover broad triggers since the audience is "every dev or non-dev":

• "create a presentation", "make slides", "build a deck"
• "prepare a talk", "knowledge sharing session"
• "convert these notes to slides"
• "marp", "slide deck", "presentation about X"
• Even if they don't explicitly mention Marp — any presentation request should trigger this skill

References to Include

references/marp-theme-guide.md

Source: @orbitant/marp-theme README

Key content:

• Available slide classes and when to use each (title, section, accent, light, light accent, cols, index, lead, end)
• Frontmatter template (marp: true, theme: orbitant, paginate: true)
• Build commands (npx marp --preview, --pdf, --pptx)
• Fonts: Lexend + IBM Plex Sans loaded automatically from Google Fonts

references/design-system.md

Source: Orbitant Design System (generated via Google Stitch by CEO)

Key content:

• Color palette & roles (Orbitant Black #0C0D0E, Blue #4567ED, gradient system)
• Typography rules (IBM Plex Sans, fluid clamp() sizing, weight 500 headings / 300 body)
• Do's and Don'ts (no pure white backgrounds, no drop shadows, gradient reserved for brand moments)
• Component styling patterns
• The overall visual philosophy: "dark, precise, confidently modern"

This helps Claude suggest content and structure that feels on-brand, not just technically correct Marp syntax.

Registration Changes

plugins/orbitant-marketing/.claude-plugin/plugin.json

Add "./skills/marp-slides" to the skills array.

Version bump

Bump orbitant-marketing version in both plugin.json and marketplace.json.

Acceptance Criteria

• SKILL.md with valid frontmatter (passes npm run validate:skills)
• Rich description field with broad trigger phrases
• references/marp-theme-guide.md with all slide classes and setup instructions
• references/design-system.md with Orbitant brand guidelines
• README.md with human-readable setup guide
• Skill registered in plugin.json and version bumped in marketplace.json
• npm run check passes
• Test: asking Claude "create a presentation about X" produces a valid Marp .md file with correct frontmatter, theme classes, and brand-appropriate content structure