agentleFS
Sign inStart free
InfopibeInfopibe/everything-claude-code/.cursor/skills/frontend-slides/SKILL.md

frontend-slides

Skill8 starsChanged 8 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

36 rules. 1 is common, 26 are distinctive, and 9 are very specific to this project.

  • 1

    Common

    Most of the 63 edited versions we read keep these.

  • 26

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Create zero-dependency, animation-rich HTML presentations that run entirely in the browser.

    line 9
  2. Distinctive:

    Zero dependencies: default to one self-contained HTML file with inline CSS and JS.

    line 22
  3. Distinctive:

    Viewport fit is mandatory: every slide must fit inside one viewport with no internal scrolling.

    line 23
  4. Distinctive:

    Show, don't tell: use visual previews instead of abstract style questionnaires.

    line 24
  5. Distinctive:

    Distinctive design: avoid generic purple-gradient, Inter-on-white, template-looking decks.

    line 25
  6. Distinctive:

    Production quality: keep code commented, accessible, responsive, and performant.

    line 26
  7. Very specific:

    Before generating, read STYLE_PRESETS.md for the viewport-safe CSS base, density limits, preset catalog, and CSS gotchas.

    line 28
  8. Distinctive:

    Ask only the minimum needed:

    line 41
  9. Distinctive:

    If the user has content, ask them to paste it before styling.

    line 46
  10. Distinctive:

    Default to visual exploration.

    line 50
  11. Distinctive:

    If the user already knows the desired preset, skip previews and use it directly.

    line 52
  12. Distinctive:

    Ask what feeling the deck should create: impressed, energized, focused, inspired.

    line 55
  13. Distinctive:

    Ask the user which preview to keep or what elements to mix.

    line 58
  14. Very specific:

    Use the preset guide in STYLE_PRESETS.md when mapping mood to style.

    line 60
  15. Very specific:

    Use an assets/ folder only when the deck contains extracted or user-supplied images.

    line 68
  16. Distinctive:

    Treat this as a hard gate.

    line 80
  17. Very specific:

    every .slide must use height: 100vh.

    line 83
  18. Very specific:

    all type and spacing must scale with clamp()

    line 84
  19. Distinctive:

    when content does not fit, split into multiple slides

    line 85
  20. Distinctive:

    never solve overflow by shrinking text below readable sizes

    line 86
  21. Distinctive:

    never allow scrollbars inside a slide

    line 87
  22. Very specific:

    Use the density limits and mandatory CSS block in STYLE_PRESETS.md.

    line 89
  23. Distinctive:

    Check the finished deck at these sizes:

    line 93
  24. Distinctive:

    If browser automation is available, use it to verify no slide overflows and that keyboard navigation works.

    line 100
  25. Distinctive:

    delete temporary preview files unless the user wants to keep them

    line 105
  26. Distinctive:

    Use the correct opener for the current OS:

    line 109
  27. Very specific:

    Prefer python3 with python-pptx to extract text, images, and notes.

    line 117
  28. Very specific:

    If python-pptx is unavailable, ask whether to install it or fall back to a manual/export-based workflow.

    line 118
  29. Distinctive:

    After extraction, run the same style-selection workflow as a new presentation.

    line 120
  30. Distinctive:

    Keep conversion cross-platform.

    line 122
  31. Distinctive:

    Use inline CSS and JS unless the user explicitly wants a multi-file project.

    line 128
  32. Distinctive:

    Prefer atmospheric backgrounds, strong type hierarchy, and a clear visual direction.

    line 130
  33. Distinctive:

    Use abstract shapes, gradients, grids, noise, and geometry rather than illustrations.

    line 131
  34. Very specific:

    use semantic structure (main, section, nav)

    line 144
  35. Distinctive:

    Use these maxima unless the user explicitly asks for denser slides and readability still holds:

    line 151
  36. Distinctive:

    every slide fits the viewport without scrolling

    line 180

“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 .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

  1. Zero dependencies: default to one self-contained HTML file with inline CSS and JS.
  2. Viewport fit is mandatory: every slide must fit inside one viewport with no internal scrolling.
  3. Show, don't tell: use visual previews instead of abstract style questionnaires.
  4. Distinctive design: avoid generic purple-gradient, Inter-on-white, template-looking decks.
  5. 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:

  1. Ask what feeling the deck should create: impressed, energized, focused, inspired.
  2. Generate 3 single-slide preview files in .ecc-design/slide-previews/.
  3. Each preview must be self-contained, show typography/color/motion clearly, and stay under roughly 100 lines of slide content.
  4. 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:

  1. Prefer python3 with python-pptx to extract text, images, and notes.
  2. If python-pptx is unavailable, ask whether to install it or fall back to a manual/export-based workflow.
  3. Preserve slide order, speaker notes, and extracted assets.
  4. 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 typeLimit
Title1 heading + 1 subtitle + optional tagline
Content1 heading + 4-6 bullets or 2 short paragraphs
Feature grid6 cards max
Code8-10 lines max
Quote1 quote + attribution
Image1 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

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free