Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
Create zero-dependency, animation-rich HTML presentations that run entirely in the browser.
When to Use This Skill
Use when the user asks to create a presentation, slide deck, or pitch from scratch.
Use when the user wants to convert an existing PPT or PPTX file into a web-based presentation.
Use when designing visually rich, animated HTML content that needs to fit exactly within the viewport.
Core Principles
Zero Dependencies — Single HTML files with inline CSS/JS. No npm, no build tools.
Show, Don't Tell — Generate visual previews, not abstract choices. People discover what they want by seeing it.
Distinctive Design — No generic "AI slop." Every presentation must feel custom-crafted.
Viewport Fitting (NON-NEGOTIABLE) — Every slide MUST fit exactly within 100vh. No scrolling within slides, ever. Content overflows? Split into multiple slides.
Design Aesthetics
You tend to converge toward generic, "on distribution" outputs. In frontend design, this creates what users call the "AI slop" aesthetic. Avoid this: make creative, distinctive frontends that surprise and delight.
Focus on:
Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics.
Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. Draw from IDE themes and cultural aesthetics for inspiration.
Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions.
Backgrounds: Create atmosphere and depth rather than defaulting to solid colors. Layer CSS gradients, use geometric patterns, or add contextual effects that match the overall aesthetic.
Avoid generic AI-generated aesthetics:
Overused font families (Inter, Roboto, Arial, system fonts)
Cliched color schemes (particularly purple gradients on white backgrounds)
Predictable layouts and component patterns
Cookie-cutter design that lacks context-specific character
Interpret creatively and make unexpected choices that feel genuinely designed for the context. Vary between light and dark themes, different fonts, different aesthetics. You still tend to converge on common choices (Space Grotesk, for example) across generations. Avoid this: it is critical that you think outside the box!
Viewport Fitting Rules
These invariants apply to EVERY slide in EVERY presentation:
Every .slide must have height: 100vh; height: 100dvh; overflow: hidden;
ALL font sizes and spacing must use clamp(min, preferred, max) — never fixed px/rem
Content containers need max-height constraints
Images: max-height: min(50vh, 400px)
Breakpoints required for heights: 700px, 600px, 500px
Include prefers-reduced-motion support
Never negate CSS functions directly (-clamp(), -min(), -max() are silently ignored) — use calc(-1 * clamp(...)) instead
When generating, read viewport-base.css and include its full contents in every presentation.
Content exceeds limits? Split into multiple slides. Never cram, never scroll.
Phase 0: Detect Mode
Determine what the user wants:
Mode A: New Presentation — Create from scratch. Go to Phase 1.
Mode B: PPT Conversion — Convert a .pptx file. Go to Phase 4.
Mode C: Enhancement — Improve an existing HTML presentation. Read it, understand it, enhance. Follow Mode C modification rules below.
Mode C: Modification Rules
When enhancing existing presentations, viewport fitting is the biggest risk:
Before adding content: Count existing elements, check against density limits
Adding images: Must have max-height: min(50vh, 400px). If slide already has max content, split into two slides
Adding text: Max 4-6 bullets per slide. Exceeds limits? Split into continuation slides
After ANY modification, verify:.slide has overflow: hidden, new elements use clamp(), images have viewport-relative max-height, content fits at 1280x720
Proactively reorganize: If modifications will cause overflow, automatically split content and inform the user. Don't wait to be asked
When adding images to existing slides: Move image to new slide or reduce other content first. Never add images without checking if existing content already fills the viewport.
Phase 1: Content Discovery (New Presentations)
Ask ALL questions in a single AskUserQuestion call so the user fills everything out at once:
Question 1 — Purpose (header: "Purpose"):
What is this presentation for? Options: Pitch deck / Teaching-Tutorial / Conference talk / Internal presentation
Question 2 — Length (header: "Length"):
Approximately how many slides? Options: Short 5-10 / Medium 10-20 / Long 20+
Question 3 — Content (header: "Content"):
Do you have content ready? Options: All content ready / Rough notes / Topic only
Question 4 — Inline Editing (header: "Editing"):
Do you need to edit text directly in the browser after generation? Options:
"Yes (Recommended)" — Can edit text in-browser, auto-save to localStorage, export file
"No" — Presentation only, keeps file smaller
Remember the user's editing choice — it determines whether edit-related code is included in Phase 3.
If user has content, ask them to share it.
Step 1.2: Image Evaluation (if images provided)
If user selected "No images" → skip to Phase 2.
If user provides an image folder:
Scan — List all image files (.png, .jpg, .svg, .webp, etc.)
View each image — Use the Read tool (Claude is multimodal)
Evaluate — For each: what it shows, USABLE or NOT USABLE (with reason), what concept it represents, dominant colors
Co-design the outline — Curated images inform slide structure alongside text. This is NOT "plan slides then add images" — design around both from the start (e.g., 3 screenshots → 3 feature slides, 1 logo → title/closing slide)
Confirm via AskUserQuestion (header: "Outline"): "Does this slide outline and image selection look right?" Options: Looks good / Adjust images / Adjust outline
Logo in previews: If a usable logo was identified, embed it (base64) into each style preview in Phase 2 — the user sees their brand styled three different ways.
Phase 2: Style Discovery
This is the "show, don't tell" phase. Most people can't articulate design preferences in words.
Step 2.0: Style Path
Ask how they want to choose (header: "Style"):
"Show me options" (recommended) — Generate 3 previews based on mood
"I know what I want" — Pick from preset list directly
If direct selection: Show preset picker and skip to Phase 3. Available presets are defined in STYLE_PRESETS.md.
Step 2.1: Mood Selection (Guided Discovery)
Ask (header: "Vibe", multiSelect: true, max 2):
What feeling should the audience have? Options:
Impressed/Confident — Professional, trustworthy
Excited/Energized — Innovative, bold
Calm/Focused — Clear, thoughtful
Inspired/Moved — Emotional, memorable
Step 2.2: Generate 3 Style Previews
Based on mood, generate 3 distinct single-slide HTML previews showing typography, colors, animation, and overall aesthetic. Read STYLE_PRESETS.md for available presets and their specifications.
Mood
Suggested Presets
Impressed/Confident
Bold Signal, Electric Studio, Dark Botanical
Excited/Energized
Creative Voltage, Neon Cyber, Split Pastel
Calm/Focused
Notebook Tabs, Paper & Ink, Swiss Modern
Inspired/Moved
Dark Botanical, Vintage Editorial, Pastel Geometry
Save previews to .claude-design/slide-previews/ (style-a.html, style-b.html, style-c.html). Each should be self-contained, ~50-100 lines, showing one animated title slide.
Open each preview automatically for the user.
Step 2.3: User Picks
Ask (header: "Style"):
Which style preview do you prefer? Options: Style A: [Name] / Style B: [Name] / Style C: [Name] / Mix elements
If "Mix elements", ask for specifics.
Phase 3: Generate Presentation
Generate the full presentation using content from Phase 1 (text, or text + curated images) and style from Phase 2.
If images were provided, the slide outline already incorporates them from Step 1.2. If not, CSS-generated visuals (gradients, shapes, patterns) provide visual interest — this is a fully supported first-class path.