PPT Master Glassmorphism SaaS Skill
Scope
This built-in skill package owns the glassmorphism-saas template variant imported from PPT-Master.
skill_id: ppt-master-glassmorphism-saas-skillvariant_id: glassmorphism-saas- upstream example:
/Users/mawenyi/try/ppt-master/examples/ppt169_glassmorphism_demo
- upstream final SVGs:
svg_final/*.svg
- upstream execution lock:
spec_lock.md
- package renderer:
assets/template.html
- package validator:
scripts/validate-deck.mjs
- layout skeletons:
references/layouts.md
- QA checklist:
references/checklist.md
Design Contract
Use this package for Glassmorphism SaaS / SaaS 玻璃态 decks. The source template is a 12-page technical product talk, AI Agent 工程化与落地, not a generic translucent card theme. Slides should preserve the PPT-Master fixed 1280x720 canvas model and use .pm-canvas.pm-glass-saas as the visual root.
Required visual language, derived from the upstream design_spec.md and spec_lock.md:
- 深色玻璃 + 流光霓虹：
#0A0E27 deep-space background, #1A2150 translucent panel base, #5B8DEF blue, #A26BFA purple, #3DDDFC cyan, #E8ECFF text.
- Color richness is part of the upstream quality bar: use blue/purple/cyan as the main light field, then deliberately reserve mint green, neon pink, and amber for success, risk, cost, status, and roadmap accents. Avoid pages where every panel uses the same blue-purple wash.
- Modern CJK sans typography: Microsoft YaHei / PingFang SC heavy titles, regular body, Consolas code labels. No serif editorial treatment.
- Glass panels serve hierarchy and readability: translucent panels, thin white strokes, top highlight lines, neon accents, and AI image atmosphere behind the content. Avoid blur-heavy CSS glass that may export poorly.
- Use the original 12-page rhythm: cover, demo-to-production hero, three pains, four-layer agent architecture, three operating modes, six-step tool orchestration, context engineering hub, KPI dashboard, 12-week trend, failure modes quadrant, 12-week roadmap, CTA closing.
- Every slide must use a registered
pm-glass-* layout and at least one package-local evidence component such as .pm-frost, .pm-glass-panel, .pm-glass-edge, .pm-flow, .pm-feature, .pm-dashboard, .pm-demo, .pm-architecture, .pm-chip, .pm-kpi, .pm-step, .pm-hub, .pm-spoke, .pm-roadmap, or .pm-guardrail.
- Titles, hero numbers, chips, metric cards, and connector/edge details should carry the neon gradient language. Do not rely on flat white text plus identical translucent rectangles as the whole visual system.
- Original example facts and labels should remain available when generating Agent engineering decks:
90%, 5-50× token drift, 92.4%, P95 4.8s, ¥0.42, 99.7% SLO, W1-W12, W4 reranker, W8 fallback, W11 cache.
- Motion only uses declarative hooks:
data-pm-motion="glass" and data-pm-anim.
Do not generate light generic SaaS cards, pure decorative glass blobs, unsourced exact performance claims, cross-template classes, animation JavaScript, @keyframes, external scripts, or custom runtime code in generated slide fragments.
1---2name: ppt-master-glassmorphism-saas-skill3description: PPT Master Glassmorphism SaaS Skill4---5# PPT Master Glassmorphism SaaS Skill67## Scope89This built-in skill package owns the `glassmorphism-saas` template variant imported from PPT-Master.1011- `skill_id`: `ppt-master-glassmorphism-saas-skill`12- `variant_id`: `glassmorphism-saas`13- upstream example: `/Users/mawenyi/try/ppt-master/examples/ppt169_glassmorphism_demo`14- upstream final SVGs: `svg_final/*.svg`15- upstream execution lock: `spec_lock.md`16- package renderer: `assets/template.html`17- package validator: `scripts/validate-deck.mjs`18- layout skeletons: `references/layouts.md`19- QA checklist: `references/checklist.md`2021## Design Contract2223Use this package for Glassmorphism SaaS / SaaS 玻璃态 decks. The source template is a 12-page technical product talk, *AI Agent 工程化与落地*, not a generic translucent card theme. Slides should preserve the PPT-Master fixed 1280x720 canvas model and use `.pm-canvas.pm-glass-saas` as the visual root.2425Required visual language, derived from the upstream `design_spec.md` and `spec_lock.md`:2627- 深色玻璃 + 流光霓虹：`#0A0E27` deep-space background, `#1A2150` translucent panel base, `#5B8DEF` blue, `#A26BFA` purple, `#3DDDFC` cyan, `#E8ECFF` text.28- Color richness is part of the upstream quality bar: use blue/purple/cyan as the main light field, then deliberately reserve mint green, neon pink, and amber for success, risk, cost, status, and roadmap accents. Avoid pages where every panel uses the same blue-purple wash.29- Modern CJK sans typography: Microsoft YaHei / PingFang SC heavy titles, regular body, Consolas code labels. No serif editorial treatment.30- Glass panels serve hierarchy and readability: translucent panels, thin white strokes, top highlight lines, neon accents, and AI image atmosphere behind the content. Avoid blur-heavy CSS glass that may export poorly.31- Use the original 12-page rhythm: cover, demo-to-production hero, three pains, four-layer agent architecture, three operating modes, six-step tool orchestration, context engineering hub, KPI dashboard, 12-week trend, failure modes quadrant, 12-week roadmap, CTA closing.32- Every slide must use a registered `pm-glass-*` layout and at least one package-local evidence component such as `.pm-frost`, `.pm-glass-panel`, `.pm-glass-edge`, `.pm-flow`, `.pm-feature`, `.pm-dashboard`, `.pm-demo`, `.pm-architecture`, `.pm-chip`, `.pm-kpi`, `.pm-step`, `.pm-hub`, `.pm-spoke`, `.pm-roadmap`, or `.pm-guardrail`.33- Titles, hero numbers, chips, metric cards, and connector/edge details should carry the neon gradient language. Do not rely on flat white text plus identical translucent rectangles as the whole visual system.34- Original example facts and labels should remain available when generating Agent engineering decks: `90%`, `5-50× token drift`, `92.4%`, `P95 4.8s`, `¥0.42`, `99.7% SLO`, `W1-W12`, `W4 reranker`, `W8 fallback`, `W11 cache`.35- Motion only uses declarative hooks: `data-pm-motion="glass"` and `data-pm-anim`.3637Do not generate light generic SaaS cards, pure decorative glass blobs, unsourced exact performance claims, cross-template classes, animation JavaScript, `@keyframes`, external scripts, or custom runtime code in generated slide fragments.
chaitin