Skip to content

coreyhaines31/makerskills / skills/slide-deck

slide-deck

Verified

When you want to draft, update, convert, or export a slide deck for a React/Next.js slide system (${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/src/app/slides/). Writes TypeScript Slide[] arrays using your primitives (Eyebrow, Heading, Accent, Body, BulletList, Divider, TwoCol, GradientText), 12 cycling brand gradients, optional sections for "where am I" context, and speaker notes. Inspired by zarazhangrui/frontend-slides — "show, don't tell" for narrative (presents 3 angles, you pick) plus density modes (speaker-led vs reading-first). Four modes — new (draft from brief), update (modify existing, with overflow guards), ppt (convert legacy PPTX → React deck), export (Playwright snapshot existing React deck to standalone HTML, PDF, or Vercel URL — keeps brand). Triggers on "/slide-deck," "/slides new," "/slides export," "/slides update," "/slides ppt," "draft a deck," "deck for [topic]," "talk on [topic]," "keynote on [topic]," "internal deck for [audience]," "convert this pptx," "export this deck."

FileKindSize
SKILL.mdskill md17.0 KB
references/export.mdmarkdown6.6 KB
references/narrative-and-voice.mdmarkdown11.1 KB
references/ppt-conversion.mdmarkdown5.4 KB
references/system.mdmarkdown5.9 KB
references/template.mdmarkdown6.4 KB

references/export.md

View on GitHub
# Export reference

Snapshot a rendered React deck to portable HTML / PDF / Vercel URL via Playwright. Output is brand-perfect because it's actual screenshots of the deck rendered in the dev server.

## Prerequisites

| Tool | Install | Check |
|---|---|---|
| Playwright | `npm install -g playwright && npx playwright install chromium` | `npx playwright --version` |
| ImageMagick (for PDF) | `brew install imagemagick` | `magick --version` |
| img2pdf (PDF alternative, simpler) | `pip install img2pdf` | `img2pdf --version` |
| Vercel CLI | `npm install -g vercel` | `vercel --version` |

If any are missing on first run, surface the install command to the user; don't try to install silently.

## Step 1 — Verify dev server

```bash
# Ping the dev server (portless-compatible — set SLIDE_DECK_DEV_HOST to e.g. yoursite.localhost:1355)
curl -sf -o /dev/null -w "%{http_code}" http://${SLIDE_DECK_DEV_HOST:-localhost:3000}/slides/<slug> && echo " OK" || echo " not running"
```

If not running:

```
Dev server isn't running. Start it with:
  cd ${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site} && npm run dev

Then re-run /slide-deck export <slug> <html|pdf|vercel>.
```

Don't auto-start — `npm run dev` is long-running.

## Step 2 — Count slides

```bash
# Counts top-level objects in the `slides: Slide[]` array
grep -E "^\s+\{$" ${SLIDE_DECK_REPO:-$HOME/code/your-slide-deck-site}/src/app/slides/<slug>/page.tsx | wc -l
```

Better: open the file and count `id:` entries in the slides array. Don't trust grep for production decks — verify by reading the file.

## Step 3 — Snapshot script

Save as `~/Documents/slide-exports/_scripts/snapshot.mjs` (create on first run):

```javascript
import { chromium } from 'playwright';
import { mkdir } from 'node:fs/promises';
import path from 'node:path';

const [, , slug, slideCountStr, outDir] = process.argv;
const slideCount = parseInt(slideCountStr, 10);
const host = process.env.SLIDE_DECK_DEV_HOST || 'localhost:3000';
const baseUrl = `http://${host}/slides/${slug}`;

await mkdir(outDir, { recursive: true });

const browser = await chromium.launch();
const ctx = await browser.newContext({ viewport: { width: 1920, height: 1080 } });
const page = await ctx.newPage();

// Reset persisted slide index so we start at slide 0
await page.addInitScript(({ slug }) => {
  localStorage.setItem(`slides:/slides/${slug}`, '0');
}, { slug });

// Load presenter-stripped view
await page.goto(`${baseUrl}?present=0`, { waitUntil: 'networkidle' });
await page.waitForTimeout(500);

for (let i = 0; i < slideCount; i++) {
  const filename = path.join(outDir, `slide-${String(i).padStart(3, '0')}.png`);
  await page.screenshot({ path: filename, fullPage: false });
  console.log(`Saved ${filename}`);
  if (i < slideCount - 1) {
    await page.keyboard.press('ArrowRight');
    await page.waitForTimeout(400); // let any animation settle
  }
}

await browser.close();
console.log(`Done: ${slideCount} slides`);
```

Run:

```bash
mkdir -p ~/Documents/slide-exports/<slug>-$(date +%Y-%m-%d)
node ~/Documents/slide-exports/_scripts/snapshot.mjs <slug> <count> ~/Documents/slide-exports/<slug>-$(date +%Y-%m-%d)
```

## Step 4 — Combine per output type

### html (standalone, portable, with arrow-key nav)

Generate a single `index.html` next to the PNGs:

```html
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <title><DECK_TITLE></title>
  <style>
    html, body { margin: 0; padding: 0; height: 100%; background: #fff; overflow: hidden; }
    .stage { display: flex; align-items: center; justify-content: center; height: 100vh; }
    .stage img { max-width: 100%; max-height: 100%; object-fit: contain; display: none; }
    .stage img.active { display: block; }
    .nav { position: fixed; bottom: 1rem; right: 1rem; font: 14px/1 system-ui; color: #4d4d4d; opacity: 0.5; }
  </style>
</head>
<body>
  <div class="stage" id="stage">
    <!-- Inject one <img src="slide-000.png" class="active"> per slide -->
  </div>
  <div class="nav"><span id="n">1</span> / <span id="t">N</span></div>
  <script>
    const slides = document.querySelectorAll('.stage img');
    let i = 0;
    document.getElementById('t').textContent = slides.length;
    function go(n) {
      i = Math.max(0, Math.min(slides.length - 1, n));
      slides.forEach((s, j) => s.classList.toggle('active', j === i));
      document.getElementById('n').textContent = i + 1;
    }
    document.addEventListener('keydown', (e) => {
      if (e.key === 'ArrowRight' || e.key === ' ' || e.key === 'PageDown') go(i + 1);
      if (e.key === 'ArrowLeft' || e.key === 'PageUp') go(i - 1);
      if (e.key === 'Home') go(0);
      if (e.key === 'End') go(slides.length - 1);
    });
    go(0);
  </script>
</body>
</html>
```

Inject the `<img>` tags by iterating the PNG filenames in the directory.

### pdf

Simplest: `img2pdf` (preserves aspect, smaller output than ImageMagick):

```bash
img2pdf ~/Documents/slide-exports/<slug>-<date>/slide-*.png \
  -o ~/Documents/slide-exports/<slug>-<date>/<slug>.pdf
```

Alternative: ImageMagick (more flexible, larger output):

```bash
magick ~/Documents/slide-exports/<slug>-<date>/slide-*.png \
  ~/Documents/slide-exports/<slug>-<date>/<slug>.pdf
```

Open after generation:

```bash
open ~/Documents/slide-exports/<slug>-<date>/<slug>.pdf   # xdg-open on Linux
```

### vercel (shareable URL)

1. Ensure the standalone `html` has been generated (see html section above)
2. Deploy:
   ```bash
   cd ~/Documents/slide-exports/<slug>-<date>/ && vercel --prod --yes
   ```
3. Report the URL Vercel returns.

First-time only: the user needs to be logged in (`vercel login`). The skill should check `vercel whoami` and prompt if needed.

To take a deployed deck down later: `vercel rm <project-name>`.

## Caveats to surface to the user

- **Animations are not preserved.** Exports are static slide snapshots — any micro-interactions, presenter view, or animations live only in the React version.
- **For interactive demos, present the React version live.** Exports are for sharing, sending, printing, archiving.
- **File sizes**: a 20-slide deck at 1920×1080 PNG is ~30–50 MB before PDF compression. PDF output is usually 5–15 MB depending on content.
- **Snapshot quality requires the dev server to render fonts and gradients correctly.** If a slide looks wrong in the PNG, it'll look wrong in the export. First-time export of a brand-new deck: open the dev server and eyeball every slide first.

## Optional: low-resolution preview

For quick previews / Slack thumbnails, snapshot at 1280×720 instead of 1920×1080. Halves the file size at minimal visual loss:

```javascript
// In snapshot.mjs, change:
viewport: { width: 1280, height: 720 }
```
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall