slide-creator
Use when creating slide decks with Marp/Marpit Markdown (marp), including authoring slide content, designing slide color schemes, and building SVG diagrams or illustrations for the deck.
What this skill does
# Slide Creation Toolkit Create professional Marp/Marpit presentations, diagrams, and color systems with a consistent design language. ## Core rules - **Use `bg` (background) syntax for all images** - Reduces manual resizing with `fit` modifier - Define one 7-role color palette and reuse it in slides and SVGs. - Define one spacing unit (e.g., 8px or 16px) and reuse it across layouts. - Define text hierarchy tiers (title/section/body) with sizes and weights; use them consistently. - For SVGs, use one stroke width and one corner radius across shapes. ## Design guidance (non-enforceable) - Aim for clear visual hierarchy with size, weight, and saturation. - Prefer one visual language (fill vs outline, emphasis rules). - Minimize visual noise; keep one primary visual anchor per section. ## Working directory This umbrella skill does not own module assets or scripts. Use the focused skills (`marp-authoring`, `slide-color-design`, `svg-illustration`) for paths and commands. ## Start here (task entry) **Entry skills (fast routing)**: - `marp-authoring` → Marp/Marpit authoring rules, layouts, themes - `slide-color-design` → palette workflow and color roles - `svg-illustration` → SVG diagram rules, patterns, embedding Pick one task and follow the exact reading path: - **Color palette only** → `slide-color-design` - **Slides only (no diagrams)** → `marp-authoring` - **Diagram only** → `svg-illustration` - **Slides + diagrams** → `marp-authoring` → `svg-illustration` - **Full deck (colors + slides + diagrams)** → `slide-color-design` → `marp-authoring` → `svg-illustration` ## One-page quick reference **Minimal steps (fast path)**: 1. Pick a palette → `slide-color-design`. 2. Draft slides → `marp-authoring`. 3. Add SVG diagrams → `svg-illustration`. 4. Validate via the module skills. **Common commands**: - `slide-color-design` → palette scripts - `marp-authoring` → Marp validation/preview - `svg-illustration` → SVG linting **Output summary**: Use module-specific output examples via the entry skills. ## Quick Start ### Two Ways to Start **Option 1: Use scripts** (automated): ```bash uv run skills/marp-authoring/scripts/init_presentation.py technical-dark my-deck.md "My Title" "Author" ``` **Option 2: Work manually** (full control): - Copy a template from `marp-authoring` → `assets/templates/` → customize - Design colors via `slide-color-design` - Write slides via `marp-authoring` - Add diagrams via `svg-illustration` **Study examples first**: Read `marp-authoring` → `assets/examples/` to see working presentations before starting. ### Script Commands Use `slide-color-design` for palette scripts and outputs. **Templates** (starting points - copy and fill in your content): - Use `marp-authoring` → `assets/templates/`. **Examples** (learning references - study patterns and copy techniques): - `marp-authoring` → `assets/examples/` for slide patterns. - `svg-illustration` → `assets/examples/` for diagram examples. - `slide-color-design` → `assets/examples/` for palette examples. **Common icons** (ready to use in slides): - `marp-authoring` → `assets/icons/`. ## Quick index (where to look) - **Reference hub**: `references/index.md` - **Color design**: `slide-color-design` - **Marpit authoring**: `marp-authoring` - **SVG illustration**: `svg-illustration` - **Decision guide**: `references/decision-guide.md` ## Modules Use the focused skills for module-specific rules and references: - **Color design** → `slide-color-design` - **Marpit authoring** → `marp-authoring` - **SVG illustration** → `svg-illustration` ## Workflow ### Single tasks Draw a diagram: 1. Use `svg-illustration` for core rules and patterns. 2. Choose colors via `slide-color-design` or existing palette. Design slide colors: 1. Use `slide-color-design` for workflow and templates. Write slides: 1. Use `marp-authoring` for syntax and layout patterns. 2. Apply a palette from `slide-color-design`. ### Full presentation 1. Establish a palette with the color module. 2. Outline slides and author via `marp-authoring`. 3. Add diagrams via `svg-illustration`. 4. Keep palette, spacing, and hierarchy consistent. ## Decision guide See [references/decision-guide.md](references/decision-guide.md) for a flowchart and loading strategy. Quick rules: ``` Slides or deck -> marp-authoring Slides + colors -> slide-color-design -> marp-authoring Slides + diagrams -> marp-authoring + svg-illustration Diagram only -> svg-illustration ``` Scale reference loading: ``` Simple request -> core rules only Complex request -> add patterns and best-practices ``` ## Output formats Use the focused skills for module-specific output formats: - `slide-color-design` → `references/output-examples.md` - `marp-authoring` → `references/output-examples.md` - `svg-illustration` → `references/output-examples.md` ## Integration rules - Use palette hex values in SVG `fill` and `stroke`. - Keep border radius and stroke widths consistent between Marpit and SVG. - Embed SVGs with Markdown images or file references. ## Troubleshooting Common cross-cutting issues: - [references/troubleshooting-common.md](references/troubleshooting-common.md) - [svg-illustration](../svg-illustration/SKILL.md) → `references/troubleshooting.md` ## Common mistakes - Using absolute paths instead of relative paths for assets. - Using multiple palettes across one deck or between slides and SVGs. - Skipping validation checks (Marp, SVG lint, contrast). See `marp-authoring`, `slide-color-design`, and `svg-illustration` for module-specific mistakes. ## Quick check (minimal) Use module-specific quick checks: - `marp-authoring` → validation/preview workflow - `svg-illustration` → SVG lint checks - `slide-color-design` → contrast checks ## Validation Use the module-specific validation guides: - `marp-authoring` → `references/preview-workflow.md` - `svg-illustration` → `references/troubleshooting.md` - `slide-color-design` → `references/color-design/workflow.md` (validation checklist) Always validate before committing files using the focused skills. ## Constraints - Output Marpit Markdown only; do not generate PowerPoint/Keynote files. - Output SVG only; do not generate raster images. - Avoid interactive animations; keep slides static. - Preserve provided brand colors; adapt them into the palette.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.