markdown-presentation
This skill should be used when creating markdown-based presentations with expandable sections, timing guides, and speaker-friendly formatting. Use for team onboarding, technical deep-dives, and knowledge transfer sessions.
What this skill does
# Markdown Presentation Skill
Create professional, presenter-friendly markdown presentations with timing guidance, expandable details, and clean visual hierarchy.
## When to Use This Skill
- Creating team onboarding presentations
- Technical architecture overviews
- Knowledge transfer sessions
- Sprint demos or retrospectives
- Any presentation that will be viewed in markdown-capable viewers (GitHub, VS Code, Obsidian)
## Presentation Structure
### Standard Template
```markdown
# Presentation Title
## Subtitle or Context
**Duration:** X minutes
**Audience:** Target audience
**Date:** YYYY-MM-DD
---
## Agenda
1. Topic 1 (X min)
2. Topic 2 (X min)
3. Topic 3 (X min)
...
---
## 1. First Section
Content here...
---
## 2. Second Section
Content here...
---
## Questions?
### Contact
- Channel/email
- Resources
---
*Presentation created: YYYY-MM-DD*
*Built with [markdown-presentation@plinde/claude-plugins](https://github.com/plinde/claude-plugins/tree/main/markdown-presentation)*
```
## Key Formatting Patterns
### Horizontal Rules as Slide Breaks
Use `---` to create visual "slide" breaks between sections:
```markdown
## Section 1
Content...
---
## Section 2
Content...
```
### Expandable Details for Dense Content
Use HTML `<details>` tags for content that's too long for a single "slide":
```markdown
<details>
<summary><b>π Click to expand detailed info</b></summary>
Long content here...
- Bullet points
- Code blocks
- Tables
</details>
```
**Best Practices for Details:**
- Use emoji + bold for visual distinction: `<b>π Title</b>`
- Keep summary text short and descriptive
- Use for: command references, configuration examples, troubleshooting guides
- Don't use for: critical information that everyone must see
### Timing Annotations
Include timing in the agenda to help presenters pace themselves:
```markdown
## Agenda
1. Introduction (2 min)
2. Architecture Overview (5 min)
3. Demo (8 min)
4. Q&A (5 min)
**Total: 20 minutes**
```
### ASCII Diagrams (Markdown Only)
Use ASCII art for architecture diagrams in **pure markdown** contexts (GitHub, VS Code preview):
```markdown
```
βββββββββββββββ βββββββββββββββ
β Source ββββββΆβ Processor β
βββββββββββββββ ββββββββ¬βββββββ
β
βΌ
βββββββββββββββ
β Output β
βββββββββββββββ
```
```
**ASCII Box Drawing Characters:**
- Corners: `β β β β`
- Lines: `β β`
- Connectors: `β β€ β¬ β΄ βΌ`
- Arrows: `βΆ βΌ β β² β β β β`
**Warning:** ASCII diagrams often have alignment issues in HTML output due to font rendering. For HTML presentations, use HTML tables/divs instead (see HTML Presentations section below).
### Tables for Comparisons
```markdown
| Feature | Option A | Option B |
|---------|----------|----------|
| Speed | Fast | Slow |
| Cost | High | Low |
```
### Quick Reference Cards
End presentations with a quick reference section:
```markdown
## Quick Reference Card
### Key Commands
| Command | Purpose |
|---------|---------|
| `cmd1` | Does X |
| `cmd2` | Does Y |
### Important Links
- [Doc 1](url)
- [Doc 2](url)
```
## Presentation Length Guidelines
| Duration | Slides/Sections | Content Depth |
|----------|-----------------|---------------|
| 5 min | 3-5 | Overview only |
| 15 min | 6-10 | Key concepts + examples |
| 30 min | 10-15 | Deep dive with demos |
| 60 min | 15-25 | Comprehensive with exercises |
**Rule of thumb:** ~2 minutes per major section (excluding expandable details)
## Viewing Options
### VS Code
```bash
code presentation.md
# Use Ctrl+Shift+V (or Cmd+Shift+V) for preview
```
### GitHub
- Push to repo, view in browser
- Details sections render as expandable
### Obsidian
- Open in vault
- Use presentation plugins for slideshow mode
### Marp (CLI)
Convert to actual slides:
```bash
marp presentation.md -o presentation.pdf
marp presentation.md -o presentation.html
```
## HTML Presentations
For presentations that will be viewed primarily in browsers, consider using HTML instead of pure markdown. HTML provides better control over styling and diagram alignment.
### When to Use HTML vs Markdown
| Use Case | Format | Reason |
|----------|--------|--------|
| GitHub/GitLab viewing | Markdown | Native rendering |
| Browser presentations | HTML | Full CSS control |
| Complex diagrams | HTML | Precise alignment |
| Print/PDF export | Either | Marp for MD, browser for HTML |
| Slideshow mode | Markdown + Marp | Better tooling |
### Dark Theme CSS Template
Use CSS variables for consistent theming (Tokyo Night-inspired palette):
```css
:root {
--bg-primary: #1a1b26;
--bg-secondary: #24283b;
--bg-tertiary: #1f2335;
--text-primary: #c0caf5;
--text-secondary: #a9b1d6;
--text-muted: #565f89;
--accent-blue: #7aa2f7;
--accent-teal: #73daca;
--accent-purple: #bb9af7;
--accent-amber: #e0af68;
--accent-green: #9ece6a;
--accent-coral: #f7768e;
--border-color: #3b4261;
}
body {
background-color: var(--bg-primary);
color: var(--text-primary);
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif;
}
pre, code {
background-color: var(--bg-tertiary);
border: 1px solid var(--border-color);
}
h1, h2, h3 { color: var(--accent-blue); }
a { color: var(--accent-teal); }
```
### HTML Diagrams (Replace ASCII)
**Problem:** ASCII art alignment breaks in HTML due to font rendering differences.
**Solution:** Use HTML divs with flexbox or tables with defined widths.
#### Architecture Box Pattern
```html
<div style="display: flex; gap: 20px; justify-content: center; flex-wrap: wrap;">
<div style="border: 2px solid var(--accent-teal); border-radius: 8px;
padding: 15px; min-width: 200px; background: rgba(115,218,202,0.1);">
<strong style="color: var(--accent-teal);">Component A</strong>
<ul><li>Feature 1</li><li>Feature 2</li></ul>
</div>
<div style="border: 2px solid var(--accent-purple); border-radius: 8px;
padding: 15px; min-width: 200px; background: rgba(187,154,247,0.1);">
<strong style="color: var(--accent-purple);">Component B</strong>
<ul><li>Feature 1</li><li>Feature 2</li></ul>
</div>
</div>
```
#### Flow Diagram Pattern (Flexbox)
```html
<div style="display: flex; align-items: center; justify-content: center;
gap: 10px; flex-wrap: wrap; padding: 20px;">
<div style="background: var(--accent-blue); color: var(--bg-primary);
padding: 10px 20px; border-radius: 8px;">
<strong>Step 1</strong>
</div>
<span style="color: var(--accent-teal); font-size: 1.5em;">β</span>
<div style="background: var(--accent-purple); color: var(--bg-primary);
padding: 10px 20px; border-radius: 8px;">
<strong>Step 2</strong>
</div>
<span style="color: var(--accent-teal); font-size: 1.5em;">β</span>
<div style="background: var(--accent-green); color: var(--bg-primary);
padding: 10px 20px; border-radius: 8px;">
<strong>Step 3</strong>
</div>
</div>
```
#### Comparison Table Pattern
```html
<table style="width: 100%; border-collapse: collapse;">
<thead>
<tr style="background: var(--bg-secondary);">
<th style="padding: 12px; border: 1px solid var(--border-color);">Feature</th>
<th style="padding: 12px; border: 1px solid var(--border-color);">Option A</th>
<th style="padding: 12px; border: 1px solid var(--border-color);">Option B</th>
</tr>
</thead>
<tbody>
<tr>
<td style="padding: 12px; border: 1px solid var(--border-color);">Speed</td>
<td style="padding: 12px; border: 1px solid var(--border-color);
color: var(--accent-green);">Fast</td>
<td style="padding: 12px; border: 1px solid var(--bRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing β use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.