agentleFS
drinkspillerdrinkspiller/skills/frontend_slides/SKILL.md

frontend-slides

Skill1 starsChanged 6 days agoUnlicenseView 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. Creates zero-dependency, self-contained HTML slide decks.

95 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use everything-claude-code, everything-claude-code-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • InfopibeSkill

    everything-claude-code

    Also in 9 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • InfopibeSkill

    investor-materials

    Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.

    Also in 23 projects that use this

  • tpavanipradeepSkill

    nextjs-turbopack

    Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

    Also in 14 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 7 projects that use this

  • CodeWithBehnamSkill

    dmux-workflows

    Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

    Also in 15 projects that use this

  • +1 more from Infopibe

The file

We split this skill into the rules it gives an agent

6 rules. 1 is common, 4 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 88 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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 12
  2. Distinctive:

    Avoid generic AI-generated aesthetics: overused fonts, cliched color schemes, predictable layouts.

    line 35
  3. Very specific:

    ALL font sizes: use clamp(min, preferred, max) — never fixed px/rem

    line 41
  4. Distinctive:

    Ask the user about purpose, length, content readiness, and editing preferences.

    line 64
  5. Distinctive:

    If they have content, ask them to share it.

    line 65
  6. Distinctive:

    When converting PowerPoint files: 1.

    line 85

“Common” is measured: kept by at least 6 in 10 of the 88 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.

Core Principles

  1. Zero Dependencies — Single HTML files with inline CSS/JS. No npm, no build tools.
  2. Show, Don't Tell — Generate visual previews, not abstract choices. People discover what they want by seeing it.
  3. Distinctive Design — No generic "AI slop." Every presentation must feel custom-crafted.
  4. Viewport Fitting (NON-NEGOTIABLE) — Every slide MUST fit exactly within 100vh. No scrolling within slides. Content overflows? Split into multiple slides.

Design Aesthetics

Focus on: - Typography: Beautiful, unique fonts. Avoid generic fonts like Arial and Inter. - Color & Theme: Cohesive aesthetic with CSS variables. Dominant colors with sharp accents. - Motion: CSS animations for effects and micro-interactions. Focus on high-impact moments. - Backgrounds: Atmosphere and depth — not solid colors. Layer CSS gradients, geometric patterns.

Avoid generic AI-generated aesthetics: overused fonts, cliched color schemes, predictable layouts.

Viewport Fitting Rules

  • Every .slide: height: 100vh; height: 100dvh; overflow: hidden;
  • ALL font sizes: use clamp(min, preferred, max) — never fixed px/rem
  • Content containers need max-height constraints
  • Images: max-height: min(50vh, 400px)
  • Include prefers-reduced-motion support

Content Density Limits Per Slide

Slide TypeMaximum Content
Title slide1 heading + 1 subtitle + optional tagline
Content slide1 heading + 4-6 bullets OR 1 heading + 2 paragraphs
Feature grid1 heading + 6 cards max (2x3 or 3x2)
Code slide1 heading + 8-10 lines of code
Quote slide1 quote (max 3 lines) + attribution
Image slide1 heading + 1 image (max 60vh height)

Content exceeds limits? Split into multiple slides. Never cram, never scroll.

Workflow

Phase 1: Content Discovery

Ask the user about purpose, length, content readiness, and editing preferences. If they have content, ask them to share it.

Phase 2: Style Discovery

Generate 3 distinct single-slide HTML previews showing typography, colors, animation, and overall aesthetic. Let the user pick their preferred style.

Mood-to-style mapping: - Impressed/Confident → Bold, professional, trustworthy - Excited/Energized → Innovative, bold, creative - Calm/Focused → Clear, thoughtful, minimal - Inspired/Moved → Emotional, memorable

Phase 3: Generate Presentation

Generate the full presentation as a single self-contained HTML file: - All CSS/JS inline - Use fonts from Google Fonts — never system fonts - Detailed comments explaining each section - Every section with clear comment block headers

Phase 4: PPT Conversion (if applicable)

When converting PowerPoint files: 1. Extract content (text, images, slide order) 2. Confirm with user 3. Style selection (Phase 2) 4. Generate HTML preserving all content

Phase 5: Delivery

Open the presentation in browser. Summarize: file location, style name, slide count, navigation (arrow keys, space, scroll/swipe, click nav dots).

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.