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 (credit: @zarazhangrui).
When to Activate
- Creating a talk deck, pitch deck, workshop deck, or internal presentation
- Converting
.ppt or .pptx slides 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
.ppt or .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.
Otherwise:
- Ask what feeling the deck should create: impressed, energized, focused, inspired.
- Generate 3 single-slide preview files in
.ecc-design/slide-previews/.
- Each preview must be self-contained, show typography/color/motion clearly, and stay under roughly 100 lines of slide content.
- Ask the user which preview to keep or what elements to mix.
Use the preset guide in STYLE_PRESETS.md when mapping mood to style.
4. Build the Presentation
Output either:
presentation.html
[presentation-name].html
Use an assets/ folder only when the deck contains extracted or user-supplied images.
Required structure:
- semantic slide sections
- a viewport-safe CSS base from
STYLE_PRESETS.md
- CSS custom properties for theme values
- a presentation controller class for keyboard, wheel, and touch navigation
- Intersection Observer for reveal animations
- reduced-motion support
5. Enforce Viewport Fit
Treat this as a hard gate.
Rules:
- every
.slide must use height: 100vh; height: 100dvh; overflow: hidden;
- all type and spacing must scale with
clamp()
- when content does not fit, split into multiple slides
- never solve overflow by shrinking text below readable sizes
- never allow scrollbars inside a slide
Use the density limits and mandatory CSS block in STYLE_PRESETS.md.
6. Validate
Check the finished deck at these sizes:
- 1920x1080
- 1280x720
- 768x1024
- 375x667
- 667x375
If browser automation is available, use it to verify no slide overflows and that keyboard navigation works.
7. Deliver
At handoff:
- delete temporary preview files unless the user wants to keep them
- open the deck with the platform-appropriate opener when useful
- summarize file path, preset used, slide count, and easy theme customization points
Use the correct opener for the current OS:
- macOS:
open file.html
- Linux:
xdg-open file.html
- Windows:
start "" file.html
PPT / PPTX Conversion
For PowerPoint conversion:
- Prefer
python3 with python-pptx to extract text, images, and notes.
- If
python-pptx is unavailable, ask whether to install it or fall back to a manual/export-based workflow.
- Preserve slide order, speaker notes, and extracted assets.
- After extraction, run the same style-selection workflow as a new presentation.
Keep conversion cross-platform. Do not rely on macOS-only tools when Python can do the job.
Implementation Requirements
HTML / CSS
- Use inline CSS and JS unless the user explicitly wants a multi-file project.
- Fonts may come from Google Fonts or Fontshare.
- Prefer atmospheric backgrounds, strong type hierarchy, and a clear visual direction.
- Use abstract shapes, gradients, grids, noise, and geometry rather than illustrations.
JavaScript
Include:
- keyboard navigation
- touch / swipe navigation
- mouse wheel navigation
- progress indicator or slide index
- reveal-on-enter animation triggers
Accessibility
- use semantic structure (
main, section, nav)
- keep contrast readable
- support keyboard-only navigation
- respect
prefers-reduced-motion
Content Density Limits
Use these maxima unless the user explicitly asks for denser slides and readability still holds:
| Slide type |
Limit |
| Title |
1 heading + 1 subtitle + optional tagline |
| Content |
1 heading + 4-6 bullets or 2 short paragraphs |
| Feature grid |
6 cards max |
| Code |
8-10 lines max |
| Quote |
1 quote + attribution |
| Image |
1 image constrained by viewport |
Anti-Patterns
- generic startup gradients with no visual identity
- system-font decks unless intentionally editorial
- long bullet walls
- code blocks that need scrolling
- fixed-height content boxes that break on short screens
- invalid negated CSS functions like
-clamp(...)
Related ECC Skills
frontend-patterns for component and interaction patterns around the deck
liquid-glass-design when a presentation intentionally borrows Apple glass aesthetics
e2e-testing if you need automated browser verification for the final deck
Deliverable Checklist
- presentation runs from a local file in a browser
- every slide fits the viewport without scrolling
- style is distinctive and intentional
- animation is meaningful, not noisy
- reduced motion is respected
- file paths and customization points are explained at handoff
1---
2name: frontend-slides-2
3description: 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.
4origin: ECC
5metadata:
6 source: https://skillmd.com/skills/affaan-m/frontend-slides-2
7---
8
9# Frontend Slides
10
11Create zero-dependency, animation-rich HTML presentations that run entirely in the browser.
12
13Inspired by the visual exploration approach showcased in work by zarazhangrui (credit: @zarazhangrui).
14
15## When to Activate
16
17- Creating a talk deck, pitch deck, workshop deck, or internal presentation
18- Converting `.ppt` or `.pptx` slides into an HTML presentation
19- Improving an existing HTML presentation's layout, motion, or typography
20- Exploring presentation styles with a user who does not know their design preference yet
21
22## Non-Negotiables
23
241. **Zero dependencies**: default to one self-contained HTML file with inline CSS and JS.
252. **Viewport fit is mandatory**: every slide must fit inside one viewport with no internal scrolling.
263. **Show, don't tell**: use visual previews instead of abstract style questionnaires.
274. **Distinctive design**: avoid generic purple-gradient, Inter-on-white, template-looking decks.
285. **Production quality**: keep code commented, accessible, responsive, and performant.
29
30Before generating, read `STYLE_PRESETS.md` for the viewport-safe CSS base, density limits, preset catalog, and CSS gotchas.
31
32## Workflow
33
34### 1. Detect Mode
35
36Choose one path:
37- **New presentation**: user has a topic, notes, or full draft
38- **PPT conversion**: user has `.ppt` or `.pptx`
39- **Enhancement**: user already has HTML slides and wants improvements
40
41### 2. Discover Content
42
43Ask only the minimum needed:
44- purpose: pitch, teaching, conference talk, internal update
45- length: short (5-10), medium (10-20), long (20+)
46- content state: finished copy, rough notes, topic only
47
48If the user has content, ask them to paste it before styling.
49
50### 3. Discover Style
51
52Default to visual exploration.
53
54If the user already knows the desired preset, skip previews and use it directly.
55
56Otherwise:
571. Ask what feeling the deck should create: impressed, energized, focused, inspired.
582. Generate **3 single-slide preview files** in `.ecc-design/slide-previews/`.
593. Each preview must be self-contained, show typography/color/motion clearly, and stay under roughly 100 lines of slide content.
604. Ask the user which preview to keep or what elements to mix.
61
62Use the preset guide in `STYLE_PRESETS.md` when mapping mood to style.
63
64### 4. Build the Presentation
65
66Output either:
67- `presentation.html`
68- `[presentation-name].html`
69
70Use an `assets/` folder only when the deck contains extracted or user-supplied images.
71
72Required structure:
73- semantic slide sections
74- a viewport-safe CSS base from `STYLE_PRESETS.md`
75- CSS custom properties for theme values
76- a presentation controller class for keyboard, wheel, and touch navigation
77- Intersection Observer for reveal animations
78- reduced-motion support
79
80### 5. Enforce Viewport Fit
81
82Treat this as a hard gate.
83
84Rules:
85- every `.slide` must use `height: 100vh; height: 100dvh; overflow: hidden;`
86- all type and spacing must scale with `clamp()`
87- when content does not fit, split into multiple slides
88- never solve overflow by shrinking text below readable sizes
89- never allow scrollbars inside a slide
90
91Use the density limits and mandatory CSS block in `STYLE_PRESETS.md`.
92
93### 6. Validate
94
95Check the finished deck at these sizes:
96- 1920x1080
97- 1280x720
98- 768x1024
99- 375x667
100- 667x375
101
102If browser automation is available, use it to verify no slide overflows and that keyboard navigation works.
103
104### 7. Deliver
105
106At handoff:
107- delete temporary preview files unless the user wants to keep them
108- open the deck with the platform-appropriate opener when useful
109- summarize file path, preset used, slide count, and easy theme customization points
110
111Use the correct opener for the current OS:
112- macOS: `open file.html`
113- Linux: `xdg-open file.html`
114- Windows: `start "" file.html`
115
116## PPT / PPTX Conversion
117
118For PowerPoint conversion:
1191. Prefer `python3` with `python-pptx` to extract text, images, and notes.
1202. If `python-pptx` is unavailable, ask whether to install it or fall back to a manual/export-based workflow.
1213. Preserve slide order, speaker notes, and extracted assets.
1224. After extraction, run the same style-selection workflow as a new presentation.
123
124Keep conversion cross-platform. Do not rely on macOS-only tools when Python can do the job.
125
126## Implementation Requirements
127
128### HTML / CSS
129
130- Use inline CSS and JS unless the user explicitly wants a multi-file project.
131- Fonts may come from Google Fonts or Fontshare.
132- Prefer atmospheric backgrounds, strong type hierarchy, and a clear visual direction.
133- Use abstract shapes, gradients, grids, noise, and geometry rather than illustrations.
134
135### JavaScript
136
137Include:
138- keyboard navigation
139- touch / swipe navigation
140- mouse wheel navigation
141- progress indicator or slide index
142- reveal-on-enter animation triggers
143
144### Accessibility
145
146- use semantic structure (`main`, `section`, `nav`)
147- keep contrast readable
148- support keyboard-only navigation
149- respect `prefers-reduced-motion`
150
151## Content Density Limits
152
153Use these maxima unless the user explicitly asks for denser slides and readability still holds:
154
155| Slide type | Limit |
156|------------|-------|
157| Title | 1 heading + 1 subtitle + optional tagline |
158| Content | 1 heading + 4-6 bullets or 2 short paragraphs |
159| Feature grid | 6 cards max |
160| Code | 8-10 lines max |
161| Quote | 1 quote + attribution |
162| Image | 1 image constrained by viewport |
163
164## Anti-Patterns
165
166- generic startup gradients with no visual identity
167- system-font decks unless intentionally editorial
168- long bullet walls
169- code blocks that need scrolling
170- fixed-height content boxes that break on short screens
171- invalid negated CSS functions like `-clamp(...)`
172
173## Related ECC Skills
174
175- `frontend-patterns` for component and interaction patterns around the deck
176- `liquid-glass-design` when a presentation intentionally borrows Apple glass aesthetics
177- `e2e-testing` if you need automated browser verification for the final deck
178
179## Deliverable Checklist
180
181- presentation runs from a local file in a browser
182- every slide fits the viewport without scrolling
183- style is distinctive and intentional
184- animation is meaningful, not noisy
185- reduced motion is respected
186- file paths and customization points are explained at handoff
187