[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZH62CGP6PCHEGQNFJB6FZ":3,"skill-same:01M72ZH62CGP6PCHEGQNFJB6FZ":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M72ZH62CGP6PCHEGQNFJB6FZ","frontend-slides",null,"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\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","SriramGandhiS\u002FSkills","SriramGandhiS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211849986?v=4","01M72WQCW12BYX71C6WN584TTA","Sriram S","01M72WQCWTJ2RD0ET1X31AF1RC",1,"MIT","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Ffrontend-slides\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: frontend-slides\ndescription: 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\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.\n---\n\n# Frontend Slides\n\nCreate zero-dependency, animation-rich HTML presentations that run entirely in the browser.\n\nInspired by the visual exploration approach showcased in work by [zarazhangrui](https:\u002F\u002Fgithub.com\u002Fzarazhangrui).\n\n## When to Activate\n\n- Creating a talk deck, pitch deck, workshop deck, or internal presentation\n- Converting `.ppt` or `.pptx` slides into an HTML presentation\n- Improving an existing HTML presentation's layout, motion, or typography\n- Exploring presentation styles with a user who does not know their design preference yet\n\n## Non-Negotiables\n\n1. **Zero dependencies**: default to one self-contained HTML file with inline CSS and JS.\n2. **Viewport fit is mandatory**: every slide must fit inside one viewport with no internal scrolling.\n3. **Show, don't tell**: use visual previews instead of abstract style questionnaires.\n4. **Distinctive design**: avoid generic purple-gradient, Inter-on-white, template-looking decks.\n5. **Production quality**: keep code commented, accessible, responsive, and performant.\n\nBefore generating, read `STYLE_PRESETS.md` for the viewport-safe CSS base, density limits, preset catalog, and CSS gotchas.\n\n## Workflow\n\n### 1. Detect Mode\n\nChoose one path:\n- **New presentation**: user has a topic, notes, or full draft\n- **PPT conversion**: user has `.ppt` or `.pptx`\n- **Enhancement**: user already has HTML slides and wants improvements\n\n### 2. Discover Content\n\nAsk only the minimum needed:\n- purpose: pitch, teaching, conference talk, internal update\n- length: short (5-10), medium (10-20), long (20+)\n- content state: finished copy, rough notes, topic only\n\nIf the user has content, ask them to paste it before styling.\n\n### 3. Discover Style\n\nDefault to visual exploration.\n\nIf the user already knows the desired preset, skip previews and use it directly.\n\nOtherwise:\n1. Ask what feeling the deck should create: impressed, energized, focused, inspired.\n2. Generate **3 single-slide preview files** in `.ecc-design\u002Fslide-previews\u002F`.\n3. Each preview must be self-contained, show typography\u002Fcolor\u002Fmotion clearly, and stay under roughly 100 lines of slide content.\n4. Ask the user which preview to keep or what elements to mix.\n\nUse the preset guide in `STYLE_PRESETS.md` when mapping mood to style.\n\n### 4. Build the Presentation\n\nOutput either:\n- `presentation.html`\n- `[presentation-name].html`\n\nUse an `assets\u002F` folder only when the deck contains extracted or user-supplied images.\n\nRequired structure:\n- semantic slide sections\n- a viewport-safe CSS base from `STYLE_PRESETS.md`\n- CSS custom properties for theme values\n- a presentation controller class for keyboard, wheel, and touch navigation\n- Intersection Observer for reveal animations\n- reduced-motion support\n\n### 5. Enforce Viewport Fit\n\nTreat this as a hard gate.\n\nRules:\n- every `.slide` must use `height: 100vh; height: 100dvh; overflow: hidden;`\n- all type and spacing must scale with `clamp()`\n- when content does not fit, split into multiple slides\n- never solve overflow by shrinking text below readable sizes\n- never allow scrollbars inside a slide\n\nUse the density limits and mandatory CSS block in `STYLE_PRESETS.md`.\n\n### 6. Validate\n\nCheck the finished deck at these sizes:\n- 1920x1080\n- 1280x720\n- 768x1024\n- 375x667\n- 667x375\n\nIf browser automation is available, use it to verify no slide overflows and that keyboard navigation works.\n\n### 7. Deliver\n\nAt handoff:\n- delete temporary preview files unless the user wants to keep them\n- open the deck with the platform-appropriate opener when useful\n- summarize file path, preset used, slide count, and easy theme customization points\n\nUse the correct opener for the current OS:\n- macOS: `open file.html`\n- Linux: `xdg-open file.html`\n- Windows: `start \"\" file.html`\n\n## PPT \u002F PPTX Conversion\n\nFor PowerPoint conversion:\n1. Prefer `python3` with `python-pptx` to extract text, images, and notes.\n2. If `python-pptx` is unavailable, ask whether to install it or fall back to a manual\u002Fexport-based workflow.\n3. Preserve slide order, speaker notes, and extracted assets.\n4. After extraction, run the same style-selection workflow as a new presentation.\n\nKeep conversion cross-platform. Do not rely on macOS-only tools when Python can do the job.\n\n## Implementation Requirements\n\n### HTML \u002F CSS\n\n- Use inline CSS and JS unless the user explicitly wants a multi-file project.\n- Fonts may come from Google Fonts or Fontshare.\n- Prefer atmospheric backgrounds, strong type hierarchy, and a clear visual direction.\n- Use abstract shapes, gradients, grids, noise, and geometry rather than illustrations.\n\n### JavaScript\n\nInclude:\n- keyboard navigation\n- touch \u002F swipe navigation\n- mouse wheel navigation\n- progress indicator or slide index\n- reveal-on-enter animation triggers\n\n### Accessibility\n\n- use semantic structure (`main`, `section`, `nav`)\n- keep contrast readable\n- support keyboard-only navigation\n- respect `prefers-reduced-motion`\n\n## Content Density Limits\n\nUse these maxima unless the user explicitly asks for denser slides and readability still holds:\n\n| Slide type | Limit |\n|------------|-------|\n| Title | 1 heading + 1 subtitle + optional tagline |\n| Content | 1 heading + 4-6 bullets or 2 short paragraphs |\n| Feature grid | 6 cards max |\n| Code | 8-10 lines max |\n| Quote | 1 quote + attribution |\n| Image | 1 image constrained by viewport |\n\n## Anti-Patterns\n\n- generic startup gradients with no visual identity\n- system-font decks unless intentionally editorial\n- long bullet walls\n- code blocks that need scrolling\n- fixed-height content boxes that break on short screens\n- invalid negated CSS functions like `-clamp(...)`\n\n## Related ECC Skills\n\n- `frontend-patterns` for component and interaction patterns around the deck\n- `liquid-glass-design` when a presentation intentionally borrows Apple glass aesthetics\n- `e2e-testing` if you need automated browser verification for the final deck\n\n## Deliverable Checklist\n\n- presentation runs from a local file in a browser\n- every slide fits the viewport without scrolling\n- style is distinctive and intentional\n- animation is meaningful, not noisy\n- reduced motion is respected\n- file paths and customization points are explained at handoff\n","# Frontend Slides\n\nCreate zero-dependency, animation-rich HTML presentations that run entirely in the browser.\n\nInspired by the visual exploration approach showcased in work by [zarazhangrui](https:\u002F\u002Fgithub.com\u002Fzarazhangrui).\n\n## When to Activate\n\n- Creating a talk deck, pitch deck, workshop deck, or internal presentation\n- Converting `.ppt` or `.pptx` slides into an HTML presentation\n- Improving an existing HTML presentation's layout, motion, or typography\n- Exploring presentation styles with a user who does not know their design preference yet\n\n## Non-Negotiables\n\n1. **Zero dependencies**: default to one self-contained HTML file with inline CSS and JS.\n2. **Viewport fit is mandatory**: every slide must fit inside one viewport with no internal scrolling.\n3. **Show, don't tell**: use visual previews instead of abstract style questionnaires.\n4. **Distinctive design**: avoid generic purple-gradient, Inter-on-white, template-looking decks.\n5. **Production quality**: keep code commented, accessible, responsive, and performant.\n\nBefore generating, read `STYLE_PRESETS.md` for the viewport-safe CSS base, density limits, preset catalog, and CSS gotchas.\n\n## Workflow\n\n### 1. Detect Mode\n\nChoose one path:\n- **New presentation**: user has a topic, notes, or full draft\n- **PPT conversion**: user has `.ppt` or `.pptx`\n- **Enhancement**: user already has HTML slides and wants improvements\n\n### 2. Discover Content\n\nAsk only the minimum needed:\n- purpose: pitch, teaching, conference talk, internal update\n- length: short (5-10), medium (10-20), long (20+)\n- content state: finished copy, rough notes, topic only\n\nIf the user has content, ask them to paste it before styling.\n\n### 3. Discover Style\n\nDefault to visual exploration.\n\nIf the user already knows the desired preset, skip previews and use it directly.\n\nOtherwise:\n1. Ask what feeling the deck should create: impressed, energized, focused, inspired.\n2. Generate **3 single-slide preview files** in `.ecc-design\u002Fslide-previews\u002F`.\n3. Each preview must be self-contained, show typography\u002Fcolor\u002Fmotion clearly, and stay under roughly 100 lines of slide content.\n4. Ask the user which preview to keep or what elements to mix.\n\nUse the preset guide in `STYLE_PRESETS.md` when mapping mood to style.\n\n### 4. Build the Presentation\n\nOutput either:\n- `presentation.html`\n- `[presentation-name].html`\n\nUse an `assets\u002F` folder only when the deck contains extracted or user-supplied images.\n\nRequired structure:\n- semantic slide sections\n- a viewport-safe CSS base from `STYLE_PRESETS.md`\n- CSS custom properties for theme values\n- a presentation controller class for keyboard, wheel, and touch navigation\n- Intersection Observer for reveal animations\n- reduced-motion support\n\n### 5. Enforce Viewport Fit\n\nTreat this as a hard gate.\n\nRules:\n- every `.slide` must use `height: 100vh; height: 100dvh; overflow: hidden;`\n- all type and spacing must scale with `clamp()`\n- when content does not fit, split into multiple slides\n- never solve overflow by shrinking text below readable sizes\n- never allow scrollbars inside a slide\n\nUse the density limits and mandatory CSS block in `STYLE_PRESETS.md`.\n\n### 6. Validate\n\nCheck the finished deck at these sizes:\n- 1920x1080\n- 1280x720\n- 768x1024\n- 375x667\n- 667x375\n\nIf browser automation is available, use it to verify no slide overflows and that keyboard navigation works.\n\n### 7. Deliver\n\nAt handoff:\n- delete temporary preview files unless the user wants to keep them\n- open the deck with the platform-appropriate opener when useful\n- summarize file path, preset used, slide count, and easy theme customization points\n\nUse the correct opener for the current OS:\n- macOS: `open file.html`\n- Linux: `xdg-open file.html`\n- Windows: `start \"\" file.html`\n\n## PPT \u002F PPTX Conversion\n\nFor PowerPoint conversion:\n1. Prefer `python3` with `python-pptx` to extract text, images, and notes.\n2. If `python-pptx` is unavailable, ask whether to install it or fall back to a manual\u002Fexport-based workflow.\n3. Preserve slide order, speaker notes, and extracted assets.\n4. After extraction, run the same style-selection workflow as a new presentation.\n\nKeep conversion cross-platform. Do not rely on macOS-only tools when Python can do the job.\n\n## Implementation Requirements\n\n### HTML \u002F CSS\n\n- Use inline CSS and JS unless the user explicitly wants a multi-file project.\n- Fonts may come from Google Fonts or Fontshare.\n- Prefer atmospheric backgrounds, strong type hierarchy, and a clear visual direction.\n- Use abstract shapes, gradients, grids, noise, and geometry rather than illustrations.\n\n### JavaScript\n\nInclude:\n- keyboard navigation\n- touch \u002F swipe navigation\n- mouse wheel navigation\n- progress indicator or slide index\n- reveal-on-enter animation triggers\n\n### Accessibility\n\n- use semantic structure (`main`, `section`, `nav`)\n- keep contrast readable\n- support keyboard-only navigation\n- respect `prefers-reduced-motion`\n\n## Content Density Limits\n\nUse these maxima unless the user explicitly asks for denser slides and readability still holds:\n\n| Slide type | Limit |\n|------------|-------|\n| Title | 1 heading + 1 subtitle + optional tagline |\n| Content | 1 heading + 4-6 bullets or 2 short paragraphs |\n| Feature grid | 6 cards max |\n| Code | 8-10 lines max |\n| Quote | 1 quote + attribution |\n| Image | 1 image constrained by viewport |\n\n## Anti-Patterns\n\n- generic startup gradients with no visual identity\n- system-font decks unless intentionally editorial\n- long bullet walls\n- code blocks that need scrolling\n- fixed-height content boxes that break on short screens\n- invalid negated CSS functions like `-clamp(...)`\n\n## Related ECC Skills\n\n- `frontend-patterns` for component and interaction patterns around the deck\n- `liquid-glass-design` when a presentation intentionally borrows Apple glass aesthetics\n- `e2e-testing` if you need automated browser verification for the final deck\n\n## Deliverable Checklist\n\n- presentation runs from a local file in a browser\n- every slide fits the viewport without scrolling\n- style is distinctive and intentional\n- animation is meaningful, not noisy\n- reduced motion is respected\n- file paths and customization points are explained at handoff\n",{"name":5,"description":7},"master","d6ca01da0f24a3b0e26e4a8b7b66cbd25d429f5d","skills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Ffrontend-slides",0,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills","https:\u002F\u002Fgithub.com\u002FSriramGandhiS","https:\u002F\u002Fsriram.website\u002F","Curious guy who keeps tinkering until something works","2026-05-20 16:21:34",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add SriramGandhiS\u002FSkills --skill frontend-slides",{"tool":39,"command":40},"bunx","bunx skills add SriramGandhiS\u002FSkills --skill frontend-slides",{"tool":42,"command":43},"pnpm","pnpm dlx skills add SriramGandhiS\u002FSkills --skill frontend-slides","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Ffrontend-slides\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",267,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Ffrontend-slides\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"STYLE_PRESETS.md",9145,"https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fskills\u002Feverything-claude-code\u002F.agents\u002Fskills\u002Ffrontend-slides\u002FSTYLE_PRESETS.md",[58,65,70,76,83,90],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M732609EPJWV13PVTX3GT4TM","webgpu-threejs-tsl","Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002Fskills\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":66,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7325XM47AGWB6K6C4VXKE6B","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fwebgpu-threejs-tsl\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7325WP6DES69JKC840VMFEP","verification-loop","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7325TFQF1DZTQ6J3WGQQ1VR","tdd-workflow","Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Ftdd-workflow\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7325RGV9AY9PK92D2V8KKPW","strategic-compact","Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fstrategic-compact\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7325MZC28SE86E7NMCNEFS4","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FSriramGandhiS\u002FSkills\u002Fblob\u002Fmaster\u002Fweb-assets\u002Fdocs\u002Fzh-TW\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[]]