← ClaudeAtlas

scaffold-presentationlisted

Scaffold a new slide deck in the user's central presentations repo (~/dev/personal/presentations), sourcing content from the current code repo, the current conversation, or material in the Obsidian vault, and matching or creating a brand theme. Works from any directory. Use when the user says "make a presentation about X", "scaffold a deck", "turn this into slides", "lag en presentasjon om X", "create a talk from this repo/conversation", or wants to present something they have been working on.
magnusrodseth/dotfiles · ★ 0 · Code & Development · score 62
Install: claude install-skill magnusrodseth/dotfiles
# Scaffold Presentation Create a new presentation in the central presentations repo. All decks live in **one** repo: ``` PRES="$HOME/dev/personal/presentations" ``` This skill is a thin orchestrator. The repo's own `AGENTS.md` and project skills are the source of truth for structure, components, themes, and deployment. Your job here: gather the content, pick the brand, then follow the repo's instructions. ## Workflow ### 1. Read the repo's instructions first Read `$PRES/AGENTS.md` before anything else. It defines the route scaffold, the `presentations.ts` manifest, available themes, slide variants, and key rules (bun not npm, lucide-react not emojis, "Magnus Rødseth" with ø, Norwegian content by default, no scrolling within slides). The repo also has project skills under `$PRES/.claude/skills/` that activate when working inside it: - `presentation-theming`: full workflow for adding a new token-driven theme - `brand-designer`: deriving a brand identity from scratch - `<company>-brand-guidelines` (capra, reitan, multiconsult, eden-stack, wispr-flow, ...): existing brand systems - `deploy-presentation`: shipping to Vercel ### 2. Gather content (pick the source the user implies) **From the current code repo** (e.g. "make a deck about this project"): - Read README, docs/, architecture notes, CONTEXT.md if present - Skim recent git history for the narrative arc (what was built, in what order, what was hard) - Note the project's brand signals: design tokens, Tailwind config