diff --git a/.agents/plugins/marketplace.json b/.agents/plugins/marketplace.json
index 7f42d3e1f..d72d94da0 100644
--- a/.agents/plugins/marketplace.json
+++ b/.agents/plugins/marketplace.json
@@ -171,6 +171,54 @@
"authentication": "ON_INSTALL"
},
"category": "开发工具"
+ },
+ {
+ "name": "frontend-slides",
+ "source": {
+ "source": "local",
+ "path": "./plugins/codex/plugins/frontend-slides"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
+ },
+ {
+ "name": "guizang-ppt-skill",
+ "source": {
+ "source": "local",
+ "path": "./plugins/codex/plugins/guizang-ppt-skill"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
+ },
+ {
+ "name": "html-ppt",
+ "source": {
+ "source": "local",
+ "path": "./plugins/codex/plugins/html-ppt"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
+ },
+ {
+ "name": "ppt-master",
+ "source": {
+ "source": "local",
+ "path": "./plugins/codex/plugins/ppt-master"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
}
]
}
diff --git a/config/external-sources.json b/config/external-sources.json
index 3c4bf2a03..f06949eb6 100644
--- a/config/external-sources.json
+++ b/config/external-sources.json
@@ -138,6 +138,213 @@
"includeRootFiles": [
"LICENSE.md"
]
+ },
+ {
+ "id": "frontend-slides",
+ "repo": "https://github.com/zarazhangrui/frontend-slides.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "pluginName": "frontend-slides",
+ "category": "文档处理",
+ "skillPath": "plugins/frontend-slides/skills/frontend-slides",
+ "brandColor": "#2563EB",
+ "manifestOverrides": {
+ "version": "0.1.0",
+ "description": "用于创建零依赖、动画丰富、固定 16:9 舞台的 HTML 演示文稿，并支持从 PPT/PPTX 转换为网页 slides。",
+ "author": {
+ "name": "zarazhangrui",
+ "url": "https://github.com/zarazhangrui"
+ },
+ "homepage": "https://github.com/zarazhangrui/frontend-slides",
+ "repository": "https://github.com/zarazhangrui/frontend-slides",
+ "license": "MIT",
+ "keywords": [
+ "frontend-slides",
+ "presentation",
+ "slides",
+ "html",
+ "pptx"
+ ],
+ "interface": {
+ "displayName": "Frontend Slides",
+ "shortDescription": "创建动画丰富、固定 16:9 舞台的 HTML 演示文稿。",
+ "longDescription": "Frontend Slides 用于从零创建零依赖 HTML slides，或将 PowerPoint 文件转换为网页演示文稿。它强调固定 1920×1080 舞台、鲜明视觉风格、动画表现和模板化审美探索，适合演讲、路演、分享和网页化展示。",
+ "developerName": "zarazhangrui",
+ "category": "文档处理",
+ "defaultPrompt": [
+ "使用 Frontend Slides 帮我制作一份网页演示文稿。",
+ "使用 Frontend Slides 帮我把 PPT/PPTX 转成 HTML slides。"
+ ],
+ "websiteURL": "https://github.com/zarazhangrui/frontend-slides",
+ "privacyPolicyURL": "https://github.com/zarazhangrui/frontend-slides",
+ "termsOfServiceURL": "https://github.com/zarazhangrui/frontend-slides",
+ "brandColor": "#2563EB"
+ }
+ },
+ "skillDescriptions": {
+ "frontend-slides": "用于创建零依赖、动画丰富、固定 16:9 舞台的 HTML 演示文稿，并支持从 PPT/PPTX 转换为网页 slides。"
+ },
+ "includeRootFiles": [
+ "README.md",
+ "LICENSE"
+ ]
+ },
+ {
+ "id": "guizang-ppt-skill",
+ "repo": "https://github.com/op7418/guizang-ppt-skill.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "pluginName": "guizang-ppt-skill",
+ "category": "文档处理",
+ "skillPath": ".",
+ "brandColor": "#F97316",
+ "manifestOverrides": {
+ "version": "0.1.0",
+ "description": "用于生成横向翻页的单文件 HTML 网页 PPT，提供电子杂志风和瑞士国际主义两类高质感视觉模板。",
+ "author": {
+ "name": "歸藏",
+ "url": "https://github.com/op7418"
+ },
+ "homepage": "https://github.com/op7418/guizang-ppt-skill",
+ "repository": "https://github.com/op7418/guizang-ppt-skill",
+ "license": "MIT",
+ "keywords": [
+ "ppt",
+ "slides",
+ "html",
+ "web-ppt",
+ "swiss-style"
+ ],
+ "interface": {
+ "displayName": "歸藏 PPT Skill",
+ "shortDescription": "生成杂志风或瑞士风的横向翻页网页 PPT。",
+ "longDescription": "歸藏 PPT Skill 用于生成单文件 HTML 横向翻页演示文稿，内置电子杂志风和瑞士国际主义两套视觉路线，适合分享、发布会、Demo Day、行业观察和需要强视觉风格的网页 PPT。",
+ "developerName": "歸藏",
+ "category": "文档处理",
+ "defaultPrompt": [
+ "使用歸藏 PPT Skill 帮我制作一份网页 PPT。",
+ "使用歸藏 PPT Skill 帮我做一份瑞士风演示文稿。"
+ ],
+ "websiteURL": "https://github.com/op7418/guizang-ppt-skill",
+ "privacyPolicyURL": "https://github.com/op7418/guizang-ppt-skill",
+ "termsOfServiceURL": "https://github.com/op7418/guizang-ppt-skill",
+ "brandColor": "#F97316"
+ }
+ },
+ "skillDescriptions": {
+ "guizang-ppt-skill": "用于生成横向翻页的单文件 HTML 网页 PPT，提供电子杂志风和瑞士国际主义两类高质感视觉模板。"
+ },
+ "includeRootFiles": [
+ "README.md",
+ "README.en.md",
+ "LICENSE"
+ ]
+ },
+ {
+ "id": "html-ppt",
+ "repo": "https://github.com/lewislulu/html-ppt-skill.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "pluginName": "html-ppt",
+ "category": "文档处理",
+ "skillPath": ".",
+ "brandColor": "#0F766E",
+ "manifestOverrides": {
+ "version": "0.1.0",
+ "description": "HTML PPT Studio，用模板、主题、布局和动画创作专业静态 HTML 演示文稿、小红书图文和多页分享稿。",
+ "author": {
+ "name": "lewislulu",
+ "url": "https://github.com/lewislulu"
+ },
+ "homepage": "https://github.com/lewislulu/html-ppt-skill",
+ "repository": "https://github.com/lewislulu/html-ppt-skill",
+ "license": "MIT",
+ "keywords": [
+ "html-ppt",
+ "presentation",
+ "slides",
+ "templates",
+ "animations"
+ ],
+ "interface": {
+ "displayName": "HTML PPT Studio",
+ "shortDescription": "用主题、布局和动画模板创作专业 HTML 演示文稿。",
+ "longDescription": "HTML PPT Studio 提供多套主题、完整 deck 模板、单页布局、CSS/Canvas 动画、演讲者模式和导出脚本，用于生成演示文稿、技术分享、路演稿、小红书图文和静态 HTML slides。",
+ "developerName": "lewislulu",
+ "category": "文档处理",
+ "defaultPrompt": [
+ "使用 HTML PPT Studio 帮我制作一份演示文稿。",
+ "使用 HTML PPT Studio 帮我生成带演讲者备注的 HTML slides。"
+ ],
+ "websiteURL": "https://github.com/lewislulu/html-ppt-skill",
+ "privacyPolicyURL": "https://github.com/lewislulu/html-ppt-skill",
+ "termsOfServiceURL": "https://github.com/lewislulu/html-ppt-skill",
+ "brandColor": "#0F766E"
+ }
+ },
+ "skillDescriptions": {
+ "html-ppt": "用主题、布局、动画和演讲者模式模板创作专业静态 HTML 演示文稿、小红书图文和多页分享稿。"
+ },
+ "includeRootFiles": [
+ "README.md",
+ "README.zh-CN.md",
+ "LICENSE"
+ ]
+ },
+ {
+ "id": "ppt-master",
+ "repo": "https://github.com/hugohe3/ppt-master.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "pluginName": "ppt-master",
+ "category": "文档处理",
+ "skillPath": "skills/ppt-master",
+ "sparseCheckout": [
+ "skills/ppt-master",
+ "README.md",
+ "LICENSE"
+ ],
+ "brandColor": "#4F46E5",
+ "manifestOverrides": {
+ "version": "0.1.0",
+ "description": "PPT Master 是多格式源文档到高质量 SVG 页面再导出 PPTX 的多阶段演示文稿生成工作流。",
+ "author": {
+ "name": "hugohe3",
+ "url": "https://github.com/hugohe3"
+ },
+ "homepage": "https://github.com/hugohe3/ppt-master",
+ "repository": "https://github.com/hugohe3/ppt-master",
+ "license": "MIT",
+ "keywords": [
+ "ppt-master",
+ "pptx",
+ "svg",
+ "presentation",
+ "deck"
+ ],
+ "interface": {
+ "displayName": "PPT Master",
+ "shortDescription": "从文档生成 SVG 页面并导出 PPTX 的多阶段工作流。",
+ "longDescription": "PPT Master 将 PDF、DOCX、URL、Markdown 等源材料转换为高质量 SVG 页面，并通过策略、模板、执行、质量检查和后处理流程导出 PPTX，适合需要结构化长流程和高质量页面控制的演示文稿制作。",
+ "developerName": "hugohe3",
+ "category": "文档处理",
+ "defaultPrompt": [
+ "使用 PPT Master 帮我基于资料生成一份 PPT。",
+ "使用 PPT Master 帮我把源文档转换成高质量演示文稿。"
+ ],
+ "websiteURL": "https://github.com/hugohe3/ppt-master",
+ "privacyPolicyURL": "https://github.com/hugohe3/ppt-master",
+ "termsOfServiceURL": "https://github.com/hugohe3/ppt-master",
+ "brandColor": "#4F46E5"
+ }
+ },
+ "skillDescriptions": {
+ "ppt-master": "多格式源文档到高质量 SVG 页面再导出 PPTX 的多阶段演示文稿生成工作流。"
+ },
+ "includeRootFiles": [
+ "README.md",
+ "LICENSE"
+ ]
}
]
}
diff --git a/config/external-sources.lock.json b/config/external-sources.lock.json
index 4ce58f100..71d0cdfae 100644
--- a/config/external-sources.lock.json
+++ b/config/external-sources.lock.json
@@ -26,6 +26,42 @@
"adapter": "claude-skill",
"commit": "1994caba0b2140d4d5aa765bb9d7d4412d6aaabb",
"syncedAt": "2026-06-11T02:45:51Z"
+ },
+ {
+ "id": "frontend-slides",
+ "pluginName": "frontend-slides",
+ "repo": "https://github.com/zarazhangrui/frontend-slides.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "commit": "871ce4daa13599d6195fe0bb465eb0ed80b2fa44",
+ "syncedAt": "2026-06-11T03:57:53Z"
+ },
+ {
+ "id": "guizang-ppt-skill",
+ "pluginName": "guizang-ppt-skill",
+ "repo": "https://github.com/op7418/guizang-ppt-skill.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "commit": "82fe5ae129e8c2a12e1155fcabed6703342749d6",
+ "syncedAt": "2026-06-11T03:57:53Z"
+ },
+ {
+ "id": "html-ppt",
+ "pluginName": "html-ppt",
+ "repo": "https://github.com/lewislulu/html-ppt-skill.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "commit": "f3a8435d3901697d5ac5e64d356c933637e43107",
+ "syncedAt": "2026-06-11T03:57:53Z"
+ },
+ {
+ "id": "ppt-master",
+ "pluginName": "ppt-master",
+ "repo": "https://github.com/hugohe3/ppt-master.git",
+ "ref": "main",
+ "adapter": "claude-skill",
+ "commit": "2b337bec18c2cb1381fee2dfca2e6f6fed463ce6",
+ "syncedAt": "2026-06-11T03:57:53Z"
}
]
}
diff --git a/plugins/codex/.agents/plugins/marketplace.json b/plugins/codex/.agents/plugins/marketplace.json
index 09c2456e7..9b8c95df4 100644
--- a/plugins/codex/.agents/plugins/marketplace.json
+++ b/plugins/codex/.agents/plugins/marketplace.json
@@ -171,6 +171,54 @@
"authentication": "ON_INSTALL"
},
"category": "开发工具"
+ },
+ {
+ "name": "frontend-slides",
+ "source": {
+ "source": "local",
+ "path": "./plugins/frontend-slides"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
+ },
+ {
+ "name": "guizang-ppt-skill",
+ "source": {
+ "source": "local",
+ "path": "./plugins/guizang-ppt-skill"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
+ },
+ {
+ "name": "html-ppt",
+ "source": {
+ "source": "local",
+ "path": "./plugins/html-ppt"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
+ },
+ {
+ "name": "ppt-master",
+ "source": {
+ "source": "local",
+ "path": "./plugins/ppt-master"
+ },
+ "policy": {
+ "installation": "AVAILABLE",
+ "authentication": "ON_INSTALL"
+ },
+ "category": "文档处理"
}
]
}
diff --git a/plugins/codex/plugins/frontend-slides/.codex-plugin/plugin.json b/plugins/codex/plugins/frontend-slides/.codex-plugin/plugin.json
new file mode 100644
index 000000000..e9f12c351
--- /dev/null
+++ b/plugins/codex/plugins/frontend-slides/.codex-plugin/plugin.json
@@ -0,0 +1,40 @@
+{
+ "name": "frontend-slides",
+ "version": "0.1.0",
+ "description": "用于创建零依赖、动画丰富、固定 16:9 舞台的 HTML 演示文稿，并支持从 PPT/PPTX 转换为网页 slides。",
+ "author": {
+ "name": "zarazhangrui",
+ "url": "https://github.com/zarazhangrui"
+ },
+ "homepage": "https://github.com/zarazhangrui/frontend-slides",
+ "repository": "https://github.com/zarazhangrui/frontend-slides",
+ "license": "MIT",
+ "keywords": [
+ "frontend-slides",
+ "presentation",
+ "slides",
+ "html",
+ "pptx"
+ ],
+ "skills": "./skills/",
+ "interface": {
+ "displayName": "Frontend Slides",
+ "shortDescription": "创建动画丰富、固定 16:9 舞台的 HTML 演示文稿。",
+ "longDescription": "Frontend Slides 用于从零创建零依赖 HTML slides，或将 PowerPoint 文件转换为网页演示文稿。它强调固定 1920×1080 舞台、鲜明视觉风格、动画表现和模板化审美探索，适合演讲、路演、分享和网页化展示。",
+ "developerName": "zarazhangrui",
+ "category": "文档处理",
+ "capabilities": [
+ "Read",
+ "Write"
+ ],
+ "defaultPrompt": [
+ "使用 Frontend Slides 帮我制作一份网页演示文稿。",
+ "使用 Frontend Slides 帮我把 PPT/PPTX 转成 HTML slides。"
+ ],
+ "websiteURL": "https://github.com/zarazhangrui/frontend-slides",
+ "privacyPolicyURL": "https://github.com/zarazhangrui/frontend-slides",
+ "termsOfServiceURL": "https://github.com/zarazhangrui/frontend-slides",
+ "brandColor": "#2563EB",
+ "screenshots": []
+ }
+}
diff --git a/plugins/codex/plugins/frontend-slides/LICENSE b/plugins/codex/plugins/frontend-slides/LICENSE
new file mode 100644
index 000000000..746da6896
--- /dev/null
+++ b/plugins/codex/plugins/frontend-slides/LICENSE
@@ -0,0 +1,21 @@
+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.
diff --git a/plugins/codex/plugins/frontend-slides/README.md b/plugins/codex/plugins/frontend-slides/README.md
new file mode 100644
index 000000000..140c2639d
--- /dev/null
+++ b/plugins/codex/plugins/frontend-slides/README.md
@@ -0,0 +1,584 @@
+# Frontend Slides
+
+A coding-agent skill for creating stunning HTML presentations — from scratch or by converting PowerPoint files. It is packaged as a Claude Code plugin, and the core `SKILL.md` can also be read by other coding agents with filesystem and shell access.
+
+## 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).
+- **Bold Template Pack** — Optional design-forward templates from `beautiful-html-templates`, loaded progressively so safe presets still work as the default fallback.
+- **Production Quality** — Accessible, fixed 16:9, well-commented code you can customize.
+
+## Installation
+
+### Via Claude Code Custom Marketplace Source
+
+Install directly from this public GitHub repo. Run these as two separate Claude Code messages; do not paste both lines into the prompt at once.
+
+```text
+/plugin marketplace add https://github.com/zarazhangrui/frontend-slides
+```
+
+After that finishes, run:
+
+```text
+/plugin install frontend-slides@frontend-slides
+```
+
+Use the HTTPS URL. The shorter `zarazhangrui/frontend-slides` form may make Claude Code try SSH, which can fail if GitHub is not already in your `known_hosts` file.
+
+Then use it by typing `/frontend-slides:frontend-slides` in Claude Code. Claude Code namespaces plugin-installed skills as `/plugin-name:skill-name`.
+
+### Claude Code Manual Installation
+
+Copy the skill files to your Claude Code skills directory:
+
+```bash
+# Create the skill directory
+mkdir -p ~/.claude/skills/frontend-slides/scripts
+
+# Copy the user-facing skill files
+cp SKILL.md STYLE_PRESETS.md viewport-base.css html-template.md animation-patterns.md ~/.claude/skills/frontend-slides/
+cp -R bold-template-pack ~/.claude/skills/frontend-slides/
+cp scripts/extract-pptx.py scripts/deploy.sh scripts/export-pdf.sh ~/.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. Standalone skills are not namespaced.
+
+### Other Coding Agents
+
+Agents such as Codex, Kimi Code, OpenCode, Gemini CLI, or other local coding assistants can use the same core skill. The simplest path is to send the agent this GitHub repo link and ask it to use the Frontend Slides skill:
+
+```text
+https://github.com/zarazhangrui/frontend-slides
+```
+
+If the agent can read GitHub repos or browse files, it should start from `SKILL.md` and load only the referenced support files it needs:
+
+- `STYLE_PRESETS.md`
+- `viewport-base.css`
+- `html-template.md`
+- `animation-patterns.md`
+- `bold-template-pack/`
+- `scripts/`
+
+Some agents can also install the skill for you if they have filesystem access and a known local skills directory. If not, they can still follow `SKILL.md` directly for the current session.
+
+The Claude Code plugin gives Claude Code a custom marketplace-source install flow and `/frontend-slides:frontend-slides` command. Other agents usually do not use that command surface.
+
+## Usage
+
+### Create a New Presentation
+
+```text
+/frontend-slides:frontend-slides
+
+> "I want to create a pitch deck for my AI startup"
+```
+
+If installed manually as a standalone Claude Code skill, use `/frontend-slides` instead.
+
+In non-Claude agents, ask the agent to use the Frontend Slides skill and point it at this repo or `SKILL.md`.
+
+The skill will:
+
+1. Ask about your content (slides, messages, images)
+2. Generate 3 visual style previews for you to compare, inferring the vibe from your brief unless you already named one
+3. Let you pick the visual direction
+4. Create the full presentation in your chosen style
+5. Open it in your browser
+
+### Convert a PowerPoint
+
+```text
+/frontend-slides: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
+
+### Bold Template Pack
+
+The skill also includes 34 optional bold design systems from
+`beautiful-html-templates`, such as **Neo-Grid Bold**, **Editorial Tri-Tone**,
+**Creative Mode**, **Broadside**, **Signal**, and **Vellum**.
+
+During style discovery, the preview set is:
+
+- 1 safe preset from `STYLE_PRESETS.md`
+- at least 1 bold template option from `bold-template-pack/selection-index.json`
+- 1 wildcard option, either another bold template or a self-generated custom design
+
+The agent reads the compact bold template index first, then loads only the
+shortlisted candidates' small `preview.md` cards for title-slide previews. It
+loads the full `design.md` for exactly one bold template only after the user
+picks that template for the final deck. If the user picks a custom wildcard,
+the agent expands that preview's own CSS and layout system into the full deck.
+
+## Bold Template Gallery
+
+Frontend Slides can now draw from the 34 bold design systems in [`beautiful-html-templates`](https://github.com/zarazhangrui/beautiful-html-templates). Three screenshots per template show how each visual system handles different slide layouts. Click any template name to inspect the source template library.
+
+### [Soft Editorial](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/soft-editorial/)
+
+
+ 
+ 
+ 
+
+
+> Cormorant Garamond serif on warm paper with sage, blush, and lemon accents.
+
+### [Editorial Forest](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/editorial-forest/)
+
+
+ 
+ 
+ 
+
+
+> Forest green, dusty pink, and warm cream in Source Serif 4 — quiet, intentional quarterly-review aesthetic.
+
+### [Pin & Paper](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/pin-and-paper/)
+
+
+ 
+ 
+ 
+
+
+> Yellow paper with safety-pin illustrations, ink-blue handwritten Caveat, paper-grain texture.
+
+### [Sakura Chroma](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/sakura-chroma/)
+
+
+ 
+ 
+ 
+
+
+> Vintage Japanese cassette-package aesthetic: cream paper, diagonal rainbow ribbons, condensed bold type, JIS-style spec checkboxes.
+
+### [Stencil & Tablet](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/stencil-tablet/)
+
+
+ 
+ 
+ 
+
+
+> Bone paper with stencil-cut headlines and a six-color earth palette: archaeology meets brand.
+
+### [Cobalt Grid](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/cobalt-grid/)
+
+
+ 
+ 
+ 
+
+
+> Electric cobalt italic serifs on a graph-paper canvas, anchored by stair-stepped pixel-glitch decorations and slim hairline rules.
+
+### [Vellum](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/vellum/)
+
+
+ 
+ 
+ 
+
+
+> Deep navy canvas with warm-yellow italic Cormorant serifs and a single dusty teal accent. A quiet, scholarly aesthetic.
+
+### [Emerald Editorial](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/emerald-editorial/)
+
+
+ 
+ 
+ 
+
+
+> Magazine-cover business deck: emerald + navy + paper with double-rule masthead ornaments and a heavy Bodoni-style display serif.
+
+### [Neo-Grid Bold](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/neo-grid-bold/)
+
+
+ 
+ 
+ 
+
+
+> Editorial neo-brutalism with a single neon yellow accent on off-white paper.
+
+### [Editorial Tri-Tone](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/editorial-tri-tone/)
+
+
+ 
+ 
+ 
+
+
+> Three-color editorial system: dusty pink, mustard cream, and deep burgundy, set in Bricolage + Instrument Serif.
+
+### [Creative Mode](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/creative-mode/)
+
+
+ 
+ 
+ 
+
+
+> Cream paper canvas with confident multi-color (green, pink, orange, yellow) accents and Archivo Black display.
+
+### [Monochrome](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/monochrome/)
+
+
+ 
+ 
+ 
+
+
+> Ivory ledger paper with all-black type; Lora serif headlines, Jost body, no color at all.
+
+### [People's Platform (Block & Bold)](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/peoples-platform/)
+
+
+ 
+ 
+ 
+
+
+> Activist poster energy: blue, orange, red on cream, with Alfa Slab + Caveat Brush.
+
+### [Pink Script — After Hours](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/pink-script/)
+
+
+ 
+ 
+ 
+
+
+> Black canvas, hot pink accent, pearl-cream paper, Instrument Serif headlines: late-night editorial luxury.
+
+### [8-Bit Orbit](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/8-bit-orbit/)
+
+
+ 
+ 
+ 
+
+
+> Pixel-art neon arcade aesthetic on a deep navy void.
+
+### [BlockFrame](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/block-frame/)
+
+
+ 
+ 
+ 
+
+
+> Neobrutalist deck with pastel-neon color blocks and chunky black borders.
+
+### [Blue Professional](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/blue-professional/)
+
+
+ 
+ 
+ 
+
+
+> Cream paper background with electric cobalt blue accents; clean modern professional.
+
+### [Bold Poster](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/bold-poster/)
+
+
+ 
+ 
+ 
+
+
+> Editorial poster aesthetic with massive Shrikhand display and a single fire-engine red accent.
+
+### [Broadside](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/broadside/)
+
+
+ 
+ 
+ 
+
+
+> Dark editorial canvas with a single fire orange accent and bilingual Latin/Chinese type stack.
+
+### [Capsule](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/capsule/)
+
+
+ 
+ 
+ 
+
+
+> Modular pill-shaped cards on warm bone with a full pastel-pop palette.
+
+### [Cartesian](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/cartesian/)
+
+
+ 
+ 
+ 
+
+
+> Quiet warm-neutral palette with classical Playfair serifs; tasteful and unhurried.
+
+### [Coral](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/coral/)
+
+
+ 
+ 
+ 
+
+
+> Cream and coral on near-black, set in oversized Bebas Neue.
+
+### [Daisy Days](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/daisy-days/)
+
+
+ 
+ 
+ 
+
+
+> Cheerful pastel deck with hand-drawn daisies, stars, and rainbows. Friendly, soft, and warm.
+
+### [Grove](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/grove/)
+
+
+ 
+ 
+ 
+
+
+> Forest-green canvas with cream type, classical Playfair serifs, and a single rust accent.
+
+### [Mat](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/mat/)
+
+
+ 
+ 
+ 
+
+
+> Dark sage canvas with bone paper and burnt-orange accent; mid-century modern with wood undertones.
+
+### [Playful](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/playful/)
+
+
+ 
+ 
+ 
+
+
+> Sun-warm peach background with Syne display: a friendly indie launch deck.
+
+### [Raw Grid](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/raw-grid/)
+
+
+ 
+ 
+ 
+
+
+> Neo-brutalist deck with thick borders, offset shadows, and a pink/sage/ink palette.
+
+### [Retro Windows](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/retro-windows/)
+
+
+ 
+ 
+ 
+
+
+> Windows 95 chrome: gray title bars, MS Sans Serif, pixel typography, full nostalgia.
+
+### [Retro Zine](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/retro-zine/)
+
+
+ 
+ 
+ 
+
+
+> Beige paper with green accent and Bebas Neue + Caveat: a riso-printed zine in HTML form.
+
+### [Scatterbrain](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/scatterbrain/)
+
+
+ 
+ 
+ 
+
+
+> Post-it inspired: pastel sticky notes, Caveat handwriting, Shrikhand and Zilla Slab type stack.
+
+### [Signal](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/signal/)
+
+
+ 
+ 
+ 
+
+
+> Deep navy canvas with bone paper and a single muted-gold accent; institutional with quiet weight.
+
+### [Studio](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/studio/)
+
+
+ 
+ 
+ 
+
+
+> Black canvas with electric-yellow type; high-voltage design studio aesthetic.
+
+### [Biennale Yellow](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/biennale-yellow/)
+
+
+ 
+ 
+ 
+
+
+> Solar yellow on warm parchment with deep indigo serif and atmospheric sun-glow gradients. Dutch-editorial poster energy.
+
+### [Long Table](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/long-table/)
+
+
+ 
+ 
+ 
+
+
+> Warm cream and rust-red supper-club aesthetic with bold uppercase grotesk headlines, italic Fraunces, and pill-shaped outlined buttons.
+
+## Architecture
+
+This skill uses **progressive disclosure** — the main `SKILL.md` is a workflow map, 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) |
+| `bold-template-pack/selection-index.json` | Compact bold template metadata | Phase 2 (candidate selection) |
+| `bold-template-pack/templates/*/preview.md` | Tiny style cards for shortlisted bold previews | Phase 2 after shortlisting |
+| `bold-template-pack/templates/*/design.md` | Full design system for the selected bold template | Phase 3 after user selection |
+| `viewport-base.css` | Mandatory fixed-stage 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) |
+| `scripts/deploy.sh` | Deploy to Vercel | Phase 6 (sharing) |
+| `scripts/export-pdf.sh` | Export slides to PDF | Phase 6 (sharing) |
+
+Maintenance-only source metadata and regeneration helpers live outside the
+user-facing skill package. Normal users do not need them.
+
+This design follows agent-skill best practices: give the agent a map first,
+then reveal only the specific files needed for the current choice.
+
+## 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).
+
+## Sharing Your Presentations
+
+After creating a presentation, the skill offers two ways to share it:
+
+### Deploy to a Live URL
+
+One command deploys your slides to a permanent, shareable URL that works on any device — phones, tablets, laptops:
+
+```bash
+bash scripts/deploy.sh ./my-deck/
+# or
+bash scripts/deploy.sh ./presentation.html
+```
+
+Uses [Vercel](https://vercel.com) (free tier). The skill walks you through signup and login if it's your first time.
+
+### Export to PDF
+
+Convert your slides to a PDF for email, Slack, Notion, or printing:
+
+```bash
+bash scripts/export-pdf.sh ./my-deck/index.html
+bash scripts/export-pdf.sh ./presentation.html ./output.pdf
+```
+
+Uses [Playwright](https://playwright.dev) to screenshot each slide at 1920×1080 and combine into a PDF. Installs automatically if needed. Animations are not preserved (it's a static snapshot).
+
+## Requirements
+
+- A local coding agent with filesystem access and the ability to run shell commands
+- Claude Code is required only for the custom marketplace-source install and `/frontend-slides:frontend-slides` command
+- For PPT conversion: Python with `python-pptx` library
+- For URL deployment: Node.js + Vercel account (free)
+- For PDF export: Node.js (Playwright installs automatically)
+
+## Credits
+
+Created by [@zarazhangrui](https://github.com/zarazhangrui).
+
+## License
+
+MIT — Use it, modify it, share it.
diff --git a/plugins/codex/plugins/frontend-slides/THIRD_PARTY_SOURCE.json b/plugins/codex/plugins/frontend-slides/THIRD_PARTY_SOURCE.json
new file mode 100644
index 000000000..0f242e5e7
--- /dev/null
+++ b/plugins/codex/plugins/frontend-slides/THIRD_PARTY_SOURCE.json
@@ -0,0 +1,9 @@
+{
+ "sourceId": "frontend-slides",
+ "repo": "https://github.com/zarazhangrui/frontend-slides.git",
+ "ref": "main",
+ "commit": "871ce4daa13599d6195fe0bb465eb0ed80b2fa44",
+ "adapter": "claude-skill",
+ "sourcePath": "plugins/frontend-slides/skills/frontend-slides",
+ "syncedAt": "2026-06-11T03:57:53Z"
+}
diff --git a/plugins/codex/plugins/frontend-slides/skills/frontend-slides/SKILL.md b/plugins/codex/plugins/frontend-slides/skills/frontend-slides/SKILL.md
new file mode 100644
index 000000000..a2c02ffa7
--- /dev/null
+++ b/plugins/codex/plugins/frontend-slides/skills/frontend-slides/SKILL.md
@@ -0,0 +1,380 @@
+---
+name: frontend-slides
+description: "用于创建零依赖、动画丰富、固定 16:9 舞台的 HTML 演示文稿，并支持从 PPT/PPTX 转换为网页 slides。"
+---
+
+# 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. **Progressive Disclosure** — Read lightweight style indexes first. For bold templates, use small preview cards for style previews and load the full `design.md` only after the user picks that template.
+5. **Fixed 16:9 Stage (NON-NEGOTIABLE)** — Every deck uses a 1920×1080 slide canvas scaled as a whole to the viewport. Slides must stay 16:9 on every screen, including phones. Do not reflow slide content to fit the device.
+
+## 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!
+
+## Fixed Stage Rules
+
+These invariants apply to EVERY slide in EVERY presentation:
+
+- Every deck has a viewport wrapper that fills the browser window.
+- Every slide is authored inside a fixed 1920×1080 stage.
+- The stage scales uniformly to fit the viewport. It may letterbox/pillarbox; it must not re-layout content.
+- Do not use responsive breakpoints to rearrange slide content for phones.
+- Use fixed internal slide measurements at the 1920×1080 design size.
+- Slide visibility must be controlled by `.active` / `.visible` using `visibility`, `opacity`, and `pointer-events` from `viewport-base.css`. Do not use `display: none` / `display: block` for slide switching; later layout classes such as `.slide-content { display: flex; }` can override them and make every slide visible at once.
+- Use `clamp()` only for non-slide UI outside the stage, or for small fallback previews where a full stage is impractical.
+- 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 Modes
+
+Ask the user whether this is primarily a reading deck or a speaking deck, then design around that answer:
+
+| Density mode | Best for | Design behavior |
+| ------------- | -------- | --------------- |
+| **Low density / speaker-led** | Public talks, keynote-style sharing, live explanation | One idea per slide, large type, strong visual hierarchy, generous negative space, 1-3 bullets max, more slides if needed |
+| **High density / reading-first** | Reports, handouts, async review, detailed internal docs | More self-contained slides, structured grids/tables/annotations, 4-8 bullets or 4-6 cards when readable, tighter but still intentional spacing |
+
+Baseline limits still apply: no scrolling, no overflow, no overlapping panels, and no text below comfortable reading size. If content exceeds the selected density mode, split it into more slides instead of shrinking until it becomes cramped.
+
+---
+
+## 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, fixed-stage fitting is the biggest risk:
+
+1. **Before adding content:** Count existing elements, check against density limits
+2. **Adding images:** Fit them inside the 1920×1080 slide canvas. 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:** the slide stage remains 16:9, no text overflows its card, no panels overlap, and screenshots look correct at 1280×720 plus one phone viewport
+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 a new slide or reduce other content first. Never add images without checking if existing content already fills the 1920×1080 slide stage.
+
+---
+
+## Phase 1: Content Discovery (New Presentations)
+
+**Ask ALL questions together** so the user fills everything out at once. If the current environment provides a native structured-question UI, use it; otherwise ask in one concise message with clearly numbered choices:
+
+**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 — Density** (header: "Density"):
+How dense should the deck feel? Options:
+
+- "Low density / speaker-led" — Big ideas, fewer words, more visual breathing room
+- "High density / reading-first" — More self-contained detail for async reading
+
+**Do not ask about inline editing during Phase 1.** Users should not have to choose editing behavior before seeing a draft. Inline editing is a post-draft affordance: include it by default unless the user explicitly asks for a locked/export-only file.
+
+Remember the user's density choice. It affects slide count, typography scale, amount of text per slide, layout density, and whether to favor cinematic presenter slides or self-contained reading slides.
+
+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. **Inspect each image** — Use the agent's available image-understanding capability. If image reading is unavailable, use filenames/metadata and ask the user to clarify only when needed
+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 the outline** using the same structured-question mechanism when available: "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: Generate 3 Style Previews Directly
+
+Based on purpose, audience, mood, and content density, generate 3 distinct single-slide HTML previews showing typography, colors, animation, and overall aesthetic.
+
+Do not ask the user whether they want options or a preset picker. The default discovery experience is always visual comparison.
+
+If the user already gave a vibe, use it. If they did not, infer the likely mood from the occasion, audience, content, and stakes. Keep the options diverse enough that the user can react visually instead of needing to articulate taste up front.
+
+If the user explicitly names a preset or bold template, honor that as one option and generate the remaining preview slots around it.
+
+Read [STYLE_PRESETS.md](STYLE_PRESETS.md) for safe preset candidates. If [bold-template-pack/selection-index.json](bold-template-pack/selection-index.json) exists, read that compact index too, but do not read any `design.md` files yet.
+
+| 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 |
+
+**Preview mix rules:**
+
+- Generate 3 previews by default: 1 safe preset from `STYLE_PRESETS.md`, at least 1 bold template from `bold-template-pack/selection-index.json`, and 1 wildcard.
+- The wildcard may be either a second bold template or a self-generated custom design. Choose whichever creates the strongest, most useful contrast for the user's occasion, audience, mood, and content.
+- Do not force every expressive option to come from the template library. If the brief has a sharper, more specific design opportunity than the available templates, use the wildcard slot to design freely.
+- For conservative or high-stakes decks, make the safe preset especially restrained; choose a calm, higher-formality bold template; make the wildcard either another restrained template or a custom design that feels authoritative rather than decorative.
+- For expressive decks, keep the safe preset as a readable fallback; choose one strong bold template; make the wildcard adventurous, context-specific, and clearly different from both other previews.
+- If bold template matches feel weak, use the wildcard as a custom design or fall back to another safe preset instead of forcing a template.
+
+**Custom wildcard design rules:**
+
+- Follow the Design Aesthetics section above: no generic "AI slop", no default font/color/layout choices, no purple-gradient-on-white clichés, no cookie-cutter dashboard/card look.
+- Match the user's stated occasion, audience, mood/vibe, and content density. The custom design should feel authored for this deck, not merely "stylish."
+- Make a deliberate visual thesis: distinctive typography, a committed palette, a recognizable layout system, and one strong atmospheric or graphic device.
+- Keep it feasible for a full deck. The preview must imply a design system that can expand into section, content, quote, comparison, and closing slides.
+- Use fixed 1920×1080 stage rules and pass the same preview authenticity checks as every other option.
+- Never render "custom", "wildcard", "AI-generated", or design-process labels on the slide itself.
+
+**Bold template selection rules:**
+
+- Match user purpose and mood against `mood`, `tone`, `best_for`, `avoid_for`, `formality`, `density`, and `scheme`.
+- Treat `best_for` examples as soft signals, not strict industry filters.
+- Keep the three previews genuinely different from each other.
+- After choosing bold template candidate(s), read only those candidate(s)' `preview.md` files from the `preview_md` paths in the selection index.
+- Use `preview.md` only for title-slide previews. Do not read full `design.md` files until the user picks the final template.
+- Do not read or copy `template.html` unless the selected final `design.md` is missing a critical implementation detail.
+
+**Preview authenticity rules (NON-NEGOTIABLE):**
+
+- Every style preview must look like a real first slide from the user's deck, not a diagnostic card.
+- Never render internal workflow text on a slide: no `preview`, `generated from`, `preview.md`, `template`, `preset`, `style option`, `Option A/B/C`, file names, paths, or source-doc labels.
+- Never render template names or slug names on the slide itself. Template/style names belong only in the message to the user.
+- Never render user requirement notes as slide content, such as "sharp and provocative", "safe option", "bold option", "for internal sharing", or "audience: ...", unless the user explicitly wants that exact phrase to appear in the deck.
+- If the slide needs chrome, use real deck chrome only: the deck title, section title, date, author, company, page number, or a genuine content phrase from the user's material.
+- Before opening previews, inspect the visible text and revise if any internal metadata appears.
+
+Save previews to `.frontend-slides/slide-previews/` (style-a.html, style-b.html, style-c.html). Each should be self-contained and compact, showing one animated title slide.
+
+Open each preview automatically for the user.
+
+### Step 2.1: 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.
+
+Apply the user's density choice throughout the deck:
+
+- **Low density / speaker-led:** Use more slides with fewer ideas per slide. Favor large headings, short phrases, visual metaphors, section beats, quote/statement slides, and presenter-friendly pacing.
+- **High density / reading-first:** Make slides more self-contained. Use structured grids, comparison tables, annotated diagrams, captions, and concise explanatory copy. Keep hierarchy strong so it feels designed, not like a document pasted onto slides.
+
+If the user's stated needs are mixed, choose the closer of the two modes instead of inventing a middle option: live audience persuasion defaults low-density; async circulation or detailed review defaults high-density.
+
+Never let high density become visual clutter. If a high-density slide starts to overflow, split it or redesign it into a clearer structure.
+
+If the user selected a bold template from `bold-template-pack`, read that one template's full `design.md` before generating. Do not read the other bold templates. Treat `design.md` as the design recipe:
+
+- Preserve its fonts, palette, decorative vocabulary, spacing rhythm, and component grammar.
+- Generate the final deck as a fixed 1920×1080 stage scaled uniformly to the viewport, regardless of whether the source template originally used `deck-stage.js` or viewport-fluid CSS.
+- Treat viewport-fluid values in `design.md` as design proportions to translate into 1920×1080 stage coordinates. Do not keep them as live viewport reflow rules in the final deck.
+- Keep the output as a single self-contained Frontend Slides HTML file.
+- Do not copy demo slide content or mimic the source template too literally.
+- Use `template.html` only as a last-resort implementation reference for the selected template.
+- After generating, verify both content overflow and panel overlap in rendered browser screenshots. `scrollHeight` checks alone are not enough because grid panels can visually cover each other.
+
+If the user selected a self-generated custom wildcard, treat that preview's CSS and layout as the design recipe:
+
+- Preserve its fonts, palette, decorative vocabulary, spacing rhythm, grid logic, and component grammar.
+- Expand the same visual system across the full deck. Do not switch to a preset or bold template after the user has chosen the custom direction.
+- Design any missing slide layouts from that system rather than importing patterns from another style.
+- Keep the output fixed-stage, single-file, and visually verified like every other deck.
+
+**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...
+
+