Repository: zarazhangrui/frontend-slides Branch: main Commit: 384d1a07ba1f Files: 8 Total size: 46.5 KB Directory structure: gitextract_obgy7a0m/ ├── LICENSE ├── README.md ├── SKILL.md ├── STYLE_PRESETS.md ├── animation-patterns.md ├── html-template.md ├── scripts/ │ └── extract-pptx.py └── viewport-base.css ================================================ FILE CONTENTS ================================================ ================================================ FILE: LICENSE ================================================ MIT License Copyright (c) 2025 Zara Zhang Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ================================================ FILE: README.md ================================================ # Frontend Slides A Claude Code skill for creating stunning, animation-rich HTML presentations — from scratch or by converting PowerPoint files. ## What This Does **Frontend Slides** helps non-designers create beautiful web presentations without knowing CSS or JavaScript. It uses a "show, don't tell" approach: instead of asking you to describe your aesthetic preferences in words, it generates visual previews and lets you pick what you like. Here is a deck about the skill, made through the skill: https://github.com/user-attachments/assets/ef57333e-f879-432a-afb9-180388982478 ### Key Features - **Zero Dependencies** — Single HTML files with inline CSS/JS. No npm, no build tools, no frameworks. - **Visual Style Discovery** — Can't articulate design preferences? No problem. Pick from generated visual previews. - **PPT Conversion** — Convert existing PowerPoint files to web, preserving all images and content. - **Anti-AI-Slop** — Curated distinctive styles that avoid generic AI aesthetics (bye-bye, purple gradients on white). - **Production Quality** — Accessible, responsive, well-commented code you can customize. ## Installation ### For Claude Code Users Copy the skill files to your Claude Code skills directory: ```bash # Create the skill directory mkdir -p ~/.claude/skills/frontend-slides/scripts # Copy all files (or clone this repo directly) cp SKILL.md STYLE_PRESETS.md viewport-base.css html-template.md animation-patterns.md ~/.claude/skills/frontend-slides/ cp scripts/extract-pptx.py ~/.claude/skills/frontend-slides/scripts/ ``` Or clone directly: ```bash git clone https://github.com/zarazhangrui/frontend-slides.git ~/.claude/skills/frontend-slides ``` Then use it by typing `/frontend-slides` in Claude Code. ## Usage ### Create a New Presentation ``` /frontend-slides > "I want to create a pitch deck for my AI startup" ``` The skill will: 1. Ask about your content (slides, messages, images) 2. Ask about the feeling you want (impressed? excited? calm?) 3. Generate 3 visual style previews for you to compare 4. Create the full presentation in your chosen style 5. Open it in your browser ### Convert a PowerPoint ``` /frontend-slides > "Convert my presentation.pptx to a web slideshow" ``` The skill will: 1. Extract all text, images, and notes from your PPT 2. Show you the extracted content for confirmation 3. Let you pick a visual style 4. Generate an HTML presentation with all your original assets ## Included Styles ### Dark Themes - **Bold Signal** — Confident, high-impact, vibrant card on dark - **Electric Studio** — Clean, professional, split-panel - **Creative Voltage** — Energetic, retro-modern, electric blue + neon - **Dark Botanical** — Elegant, sophisticated, warm accents ### Light Themes - **Notebook Tabs** — Editorial, organized, paper with colorful tabs - **Pastel Geometry** — Friendly, approachable, vertical pills - **Split Pastel** — Playful, modern, two-color vertical split - **Vintage Editorial** — Witty, personality-driven, geometric shapes ### Specialty - **Neon Cyber** — Futuristic, particle backgrounds, neon glow - **Terminal Green** — Developer-focused, hacker aesthetic - **Swiss Modern** — Minimal, Bauhaus-inspired, geometric - **Paper & Ink** — Literary, drop caps, pull quotes ## Architecture This skill uses **progressive disclosure** — the main `SKILL.md` is a concise map (~180 lines), with supporting files loaded on-demand only when needed: | File | Purpose | Loaded When | |------|---------|-------------| | `SKILL.md` | Core workflow and rules | Always (skill invocation) | | `STYLE_PRESETS.md` | 12 curated visual presets | Phase 2 (style selection) | | `viewport-base.css` | Mandatory responsive CSS | Phase 3 (generation) | | `html-template.md` | HTML structure and JS features | Phase 3 (generation) | | `animation-patterns.md` | CSS/JS animation reference | Phase 3 (generation) | | `scripts/extract-pptx.py` | PPT content extraction | Phase 4 (conversion) | This design follows [OpenAI's harness engineering](https://openai.com/index/harness-engineering/) principle: "give the agent a map, not a 1,000-page instruction manual." ## Philosophy This skill was born from the belief that: 1. **You don't need to be a designer to make beautiful things.** You just need to react to what you see. 2. **Dependencies are debt.** A single HTML file will work in 10 years. A React project from 2019? Good luck. 3. **Generic is forgettable.** Every presentation should feel custom-crafted, not template-generated. 4. **Comments are kindness.** Code should explain itself to future-you (or anyone else who opens it). ## Requirements - [Claude Code](https://claude.ai/claude-code) CLI - For PPT conversion: Python with `python-pptx` library ## Credits Created by [@zarazhangrui](https://github.com/zarazhangrui) with Claude Code. Inspired by the "Vibe Coding" philosophy — building beautiful things without being a traditional software engineer. ## License MIT — Use it, modify it, share it. ================================================ FILE: SKILL.md ================================================ --- name: frontend-slides description: 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. ## 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, 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 Density Limits Per Slide | Slide Type | Maximum Content | |------------|-----------------| | Title slide | 1 heading + 1 subtitle + optional tagline | | Content slide | 1 heading + 4-6 bullet points OR 1 heading + 2 paragraphs | | Feature grid | 1 heading + 6 cards maximum (2x3 or 3x2) | | Code slide | 1 heading + 8-10 lines of code | | Quote slide | 1 quote (max 3 lines) + attribution | | Image slide | 1 heading + 1 image (max 60vh height) | **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: 1. **Before adding content:** Count existing elements, check against density limits 2. **Adding images:** Must have `max-height: min(50vh, 400px)`. If slide already has max content, split into two slides 3. **Adding text:** Max 4-6 bullets per slide. Exceeds limits? Split into continuation slides 4. **After ANY modification, verify:** `.slide` has `overflow: hidden`, new elements use `clamp()`, images have viewport-relative max-height, content fits at 1280x720 5. **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: 1. **Scan** — List all image files (.png, .jpg, .svg, .webp, etc.) 2. **View each image** — Use the Read tool (Claude is multimodal) 3. **Evaluate** — For each: what it shows, USABLE or NOT USABLE (with reason), what concept it represents, dominant colors 4. **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) 5. **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](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](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. **Before generating, read these supporting files:** - [html-template.md](html-template.md) — HTML architecture and JS features - [viewport-base.css](viewport-base.css) — Mandatory CSS (include in full) - [animation-patterns.md](animation-patterns.md) — Animation reference for the chosen feeling **Key requirements:** - Single self-contained HTML file, all CSS/JS inline - Include the FULL contents of viewport-base.css in the `

Presentation Title

Subtitle or author

Slide Title

Content...

``` ## Required JavaScript Features Every presentation must include: 1. **SlidePresentation Class** — Main controller with: - Keyboard navigation (arrows, space, page up/down) - Touch/swipe support - Mouse wheel navigation - Progress bar updates - Navigation dots 2. **Intersection Observer** — For scroll-triggered animations: - Add `.visible` class when slides enter viewport - Trigger CSS transitions efficiently 3. **Optional Enhancements** (match to chosen style): - Custom cursor with trail - Particle system background (canvas) - Parallax effects - 3D tilt on hover - Magnetic buttons - Counter animations 4. **Inline Editing** (only if user opted in during Phase 1 — skip entirely if they said No): - Edit toggle button (hidden by default, revealed via hover hotzone or `E` key) - Auto-save to localStorage - Export/save file functionality - See "Inline Editing Implementation" section below ## Inline Editing Implementation (Opt-In Only) **If the user chose "No" for inline editing in Phase 1, do NOT generate any edit-related HTML, CSS, or JS.** **Do NOT use CSS `~` sibling selector for hover-based show/hide.** The CSS-only approach (`edit-hotzone:hover ~ .edit-toggle`) fails because `pointer-events: none` on the toggle button breaks the hover chain: user hovers hotzone -> button becomes visible -> mouse moves toward button -> leaves hotzone -> button disappears before click. **Required approach: JS-based hover with 400ms delay timeout.** HTML: ```html
``` CSS (visibility controlled by JS classes only): ```css /* Do NOT use CSS ~ sibling selector for this! pointer-events: none breaks the hover chain. Must use JS with delay timeout. */ .edit-hotzone { position: fixed; top: 0; left: 0; width: 80px; height: 80px; z-index: 10000; cursor: pointer; } .edit-toggle { opacity: 0; pointer-events: none; transition: opacity 0.3s ease; z-index: 10001; } .edit-toggle.show, .edit-toggle.active { opacity: 1; pointer-events: auto; } ``` JS (three interaction methods): ```javascript // 1. Click handler on the toggle button document.getElementById('editToggle').addEventListener('click', () => { editor.toggleEditMode(); }); // 2. Hotzone hover with 400ms grace period const hotzone = document.querySelector('.edit-hotzone'); const editToggle = document.getElementById('editToggle'); let hideTimeout = null; hotzone.addEventListener('mouseenter', () => { clearTimeout(hideTimeout); editToggle.classList.add('show'); }); hotzone.addEventListener('mouseleave', () => { hideTimeout = setTimeout(() => { if (!editor.isActive) editToggle.classList.remove('show'); }, 400); }); editToggle.addEventListener('mouseenter', () => { clearTimeout(hideTimeout); }); editToggle.addEventListener('mouseleave', () => { hideTimeout = setTimeout(() => { if (!editor.isActive) editToggle.classList.remove('show'); }, 400); }); // 3. Hotzone direct click hotzone.addEventListener('click', () => { editor.toggleEditMode(); }); // 4. Keyboard shortcut (E key, skip when editing text) document.addEventListener('keydown', (e) => { if ((e.key === 'e' || e.key === 'E') && !e.target.getAttribute('contenteditable')) { editor.toggleEditMode(); } }); ``` ## Image Pipeline (Skip If No Images) If user chose "No images" in Phase 1, skip this entirely. If images were provided, process them before generating HTML. **Dependency:** `pip install Pillow` ### Image Processing ```python from PIL import Image, ImageDraw # Circular crop (for logos on modern/clean styles) def crop_circle(input_path, output_path): img = Image.open(input_path).convert('RGBA') w, h = img.size size = min(w, h) left, top = (w - size) // 2, (h - size) // 2 img = img.crop((left, top, left + size, top + size)) mask = Image.new('L', (size, size), 0) ImageDraw.Draw(mask).ellipse([0, 0, size, size], fill=255) img.putalpha(mask) img.save(output_path, 'PNG') # Resize (for oversized images that inflate HTML) def resize_max(input_path, output_path, max_dim=1200): img = Image.open(input_path) img.thumbnail((max_dim, max_dim), Image.LANCZOS) img.save(output_path, quality=85) ``` | Situation | Operation | |-----------|-----------| | Square logo on rounded aesthetic | `crop_circle()` | | Image > 1MB | `resize_max(max_dim=1200)` | | Wrong aspect ratio | Manual crop with `img.crop()` | Save processed images with `_processed` suffix. Never overwrite originals. ### Image Placement **Use direct file paths** (not base64) — presentations are viewed locally: ```html Screenshot ``` ```css .slide-image { max-width: 100%; max-height: min(50vh, 400px); object-fit: contain; border-radius: 8px; } .slide-image.screenshot { border: 1px solid rgba(255, 255, 255, 0.1); border-radius: 12px; box-shadow: 0 8px 32px rgba(0, 0, 0, 0.3); } .slide-image.logo { max-height: min(30vh, 200px); } ``` **Adapt border/shadow colors to match the chosen style's accent.** Never repeat the same image on multiple slides (except logos on title + closing). **Placement patterns:** Logo centered on title slide. Screenshots in two-column layouts with text. Full-bleed images as slide backgrounds with text overlay (use sparingly). --- ## Code Quality **Comments:** Every section needs clear comments explaining what it does and how to modify it. **Accessibility:** - Semantic HTML (`
`, `