[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ECE58G14XGTMP6FWRNXJMT":3,"skill-same:01M7ECE58G14XGTMP6FWRNXJMT":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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7ECE58G14XGTMP6FWRNXJMT","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Ffrontend-slides-everything-claude-code-main-2\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\norigin: ECC\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,"origin":24,"description":7},"ECC","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","03-逆向工程\u002Ffrontend-slides-everything-claude-code-main-2",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill frontend-slides",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill frontend-slides",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill frontend-slides","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Ffrontend-slides-everything-claude-code-main-2\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",285,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Ffrontend-slides-everything-claude-code-main-2\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"STYLE_PRESETS.md",9145,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Ffrontend-slides-everything-claude-code-main-2\u002FSTYLE_PRESETS.md",[58,65,72,79,87,94],{"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},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]