Slides
Design a narrative first and a visual deck second. Resolve skill-dir to this folder before using bundled search and validation tools.
Workflow
- Define audience, decision, time limit, slide count, evidence, brand, and output format.
- Write a one-sentence narrative and a slide-by-slide argument before layout.
- Choose one strategy and layout family.
- Use one message per slide; move supporting detail to notes or appendix.
- Build from design tokens and reusable slide patterns.
- Turn data into a stated insight, not decoration.
- Validate sequence, evidence, readability, overflow, contrast, and export behavior.
Read only the needed reference:
- references/slide-strategies.md for narrative structures;
- references/layout-patterns.md for composition;
- references/copywriting-formulas.md for concise persuasion;
- references/html-template.md for HTML deck structure;
- references/create.md for the complete creation flow.
Search the bundled slide library
python "<skill-dir>/scripts/search-slides.py" "investor pitch" -d strategy
python "<skill-dir>/scripts/search-slides.py" "metrics dashboard" -d layout
python "<skill-dir>/scripts/search-slides.py" "problem urgency" -d copy --json
Use returned patterns as candidates; adapt them to the audience and evidence.
Implementation rules
- Use semantic design tokens for color, type, spacing, and chart styling.
- Keep text within safe margins and test the smallest intended viewport.
- Provide alt text or a text summary for charts and meaningful images.
- Label axes, units, dates, samples, and sources.
- Prefer editable text and vector shapes over text baked into images.
- Keep animation optional, purposeful, and reduced-motion compatible.
Output contract
Provide:
- narrative and slide outline;
- final deck or implementation files;
- source list and chart-data provenance;
- speaker notes when requested;
- validation results for overflow, links, contrast, and export.
Guardrails
- Do not invent metrics, testimonials, citations, or customer logos.
- Do not shrink body text to force excessive copy onto one slide.
- Do not use a chart without stating its takeaway.
- Do not hardcode a provider, model, or host-specific path.
1---2name: slides3description: Plan, write, build, and validate strategic presentations and HTML slide decks with clear narrative, responsive layouts, design tokens, data visualization, speaker-ready copy, and accessible exports. Use for pitch decks, research presentations, product narratives, training decks, or slide-system reviews.4---56# Slides78Design a narrative first and a visual deck second. Resolve skill-dir to this folder before using bundled search and validation tools.910## Workflow11121. Define audience, decision, time limit, slide count, evidence, brand, and output format.132. Write a one-sentence narrative and a slide-by-slide argument before layout.143. Choose one strategy and layout family.154. Use one message per slide; move supporting detail to notes or appendix.165. Build from design tokens and reusable slide patterns.176. Turn data into a stated insight, not decoration.187. Validate sequence, evidence, readability, overflow, contrast, and export behavior.1920Read only the needed reference:2122- references/slide-strategies.md for narrative structures;23- references/layout-patterns.md for composition;24- references/copywriting-formulas.md for concise persuasion;25- references/html-template.md for HTML deck structure;26- references/create.md for the complete creation flow.2728## Search the bundled slide library2930~~~text31python "<skill-dir>/scripts/search-slides.py" "investor pitch" -d strategy32python "<skill-dir>/scripts/search-slides.py" "metrics dashboard" -d layout33python "<skill-dir>/scripts/search-slides.py" "problem urgency" -d copy --json34~~~3536Use returned patterns as candidates; adapt them to the audience and evidence.3738## Implementation rules3940- Use semantic design tokens for color, type, spacing, and chart styling.41- Keep text within safe margins and test the smallest intended viewport.42- Provide alt text or a text summary for charts and meaningful images.43- Label axes, units, dates, samples, and sources.44- Prefer editable text and vector shapes over text baked into images.45- Keep animation optional, purposeful, and reduced-motion compatible.4647## Output contract4849Provide:5051- narrative and slide outline;52- final deck or implementation files;53- source list and chart-data provenance;54- speaker notes when requested;55- validation results for overflow, links, contrast, and export.5657## Guardrails5859- Do not invent metrics, testimonials, citations, or customer logos.60- Do not shrink body text to force excessive copy onto one slide.61- Do not use a chart without stating its takeaway.62- Do not hardcode a provider, model, or host-specific path.
yigityildiz0 