#!/bin/sh
set -e
mkdir -p ~/.claude/skills/jd-slides
cat > ~/.claude/skills/jd-slides/SKILL.md << 'CLAUDE_SKILL_EOF'
---
name: slides
description: Guide slide deck structure, narrative, and content with strong action titles and minimal words. Supports polished and working-draft modes.
---

# Slide Deck Creation

## Two Modes

The user will specify (or you should ask) which mode:

**Polished mode** — for final presentations, pitches, talks. Every word must earn its place.
- Target: ≤15 words per slide body (titles excluded)
- Visuals carry the message; text is reinforcement only
- No bullet points — use images, charts, diagrams, or single statements

**Working mode** — for internal decks, quick drafts, async communication where the deck stands alone.
- Target: ≤40 words per slide body
- Bullets are acceptable but keep to 3-4 per slide, 6-8 words each
- Still apply all structural and title rules below

## Before Writing Any Slides

1. **Ask the user**: What is the one thing the audience should remember? Who is the audience? What decision or action should this drive?
2. **Build the narrative arc first.** Write the sequence of action titles before touching any slide content. Present this title sequence to the user for approval — this is the "ghost deck." Reading only the titles should tell the complete story.
3. **Select 3-5 key messages.** If you have more, cut. The audience will not remember more than 5 things. (Khosla: "engineer an email" — your audience will summarize your deck to someone else. Design so that summary is the one you want.)

## Slide Rules

### Titles
Every slide title MUST be an assertion, not a topic label.
- BAD: "Market Opportunity"
- GOOD: "The market is growing 40% annually and no one serves segment X"

The title alone should convey the slide's takeaway. If the title is a topic label, rewrite it.

### The 5-Second Test
Put the slide on screen for 5 seconds, then remove it. Could someone describe the key point? If not, simplify. This is the single most important quality test.

### Visual Focus
Each slide gets exactly ONE focal point — the single place the viewer's eye should go. If there are competing focal points, split into multiple slides.

### Structure
- **Open with the problem.** State it in the first 1-2 slides with emotion, not technical detail. 80% of presentations fail to make the problem clear until too late.
- **Lead with the answer, then support it.** Especially for executive audiences: conclusion first, evidence after.
- **Address risks head-on.** Acknowledge the top 2-3 concerns and show mitigation. Never hide information.

### Formatting
- Generous whitespace — light fonts, open layouts
- Vary slide layouts across the deck: mix full-bleed images, split layouts, single-statement slides, and chart slides
- No decorative-only elements. Every visual must communicate.
- Max 25 slides for a pitch deck. For other contexts, aim for 1 slide per minute of speaking time.

## After Generating

Review your own output against these checks:
1. Read only the titles in sequence. Does it tell the full story? (Ghost deck test)
2. Does every slide pass the 5-second test?
3. In polished mode: are there any bullet points? (There shouldn't be.)
4. Are any titles topic labels instead of assertions? Fix them.
5. Count words per slide. Are any over the mode's limit?

State which checks passed and flag any slides that are borderline.

CLAUDE_SKILL_EOF
echo "Installed skill: jd-slides"