slidev-deck-pipeline

# Slidev Deck Pipeline The single, repeatable path for turning content into a published OpenCoven Slidev deck. Optimize for **determinism**: same inputs → same deck → same verified `dist` → same deploy. Author by writing a real `.md` file with Node's `fs.writeFileSync`, then run the repo's own scripts to verify and build. Never eyeball-ship. ## When to use | Scenario | Use this skill | |----------|----------------| | Weekly Open Coven / Show'n Spells deck | ✅ (the canonical path) | | One-off launch / explainer deck in the same house style | ✅ | | Rebuilding an existing deck "the standard way" | ✅ | | Exporting a deck to PDF | ✅ | | Deploying a deck to Vercel (`show.opencoven.ai`) | ✅ | | Non-Slidev copy (tweets, Discord posts) | ❌ use the voice/social skills instead | ## Repo facts (canonical) - **Repo:** `/Users/buns/Documents/GitHub/OpenCoven/open-coven-weekly` - **Decks:** `slides/YYYY-MM-DD.md` (a `-slug` suffix is allowed: `YYYY-MM-DD-slug.md`) - **Template:** `slides/template.md` - **Theme:** `theme/` = `@opencoven/slidev-theme-coven`; referenced from a deck as `theme: ../theme` - **Static assets:** `slides/public/` → served at `/` (images live in `slides/public/img/`, referenced as `/img/<name>`) - **Package manager:** `pnpm` - **Deploy:** Vercel project `open-coven-weekly`, aliased to `show.opencoven.ai`, auto-deploys on push to `main` ### The scripts (this is the deterministic core — always use them) | Command | What it does | |---------|--------------| | `pnp...