
HTML Slide Decks
Build animated HTML presentations or convert PowerPoint files to web slides.
Install
npx skills add affaan-m/ECC --skill frontend-slides -g -a claude-code -y- Repository
- affaan-m/ECC295k
- Category
- Design
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,548 tokens
- Runs scripts
- No, instructions only
What it does
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.
Frontend Slides
Create zero-dependency, animation-rich HTML presentations that run entirely in the browser.
Inspired by the visual exploration approach showcased in work by zarazhangrui.
When to Activate
- Creating a talk deck, pitch deck, workshop deck, or internal presentation
- Converting
.pptor.pptxslides into an HTML presentation - Improving an existing HTML presentation's layout, motion, or typography
- Exploring presentation styles with a user who does not know their design preference yet
Non-Negotiables
- Zero dependencies: default to one self-contained HTML file with inline CSS and JS.
- Viewport fit is mandatory: every slide must fit inside one viewport with no internal scrolling.
- Show, don't tell: use visual previews instead of abstract style questionnaires.
- Distinctive design: avoid generic purple-gradient, Inter-on-white, template-looking decks.
- Production quality: keep code commented, accessible, responsive, and performant.
Before generating, read STYLE_PRESETS.md for the viewport-safe CSS base, density limits, preset catalog, and CSS gotchas.
Workflow
1. Detect Mode
Choose one path:
- New presentation: user has a topic, notes, or full draft
- PPT conversion: user has
.pptor.pptx - Enhancement: user already has HTML slides and wants improvements
2. Discover Content
Ask only the minimum needed:
- purpose: pitch, teaching, conference talk, internal update
- length: short (5-10), medium (10-20), long (20+)
- content state: finished copy, rough notes, topic only
If the user has content, ask them to paste it before styling.
3. Discover Style
Default to visual exploration.
If the user already knows the desired preset, skip previews and use it directly.


