Slide Template Manager

Use this skill to choose a built-in slide template,create a custom template from a style description,or extract one from an existing PPT project.

Templates

Decision

• Explicit template name/dir/alias:use it directly.
• User describes concrete visual style(colors,materials,layout,decorative elements,visual keywords;配色/材质/版式/装饰/视觉关键词):generate a custom template first,then use it.
• User only describes scenario/topic/audience(场景/主题/受众) without enough visual specs:recommend 3-5 built-in templates with ask_user.
• ask_user options must include name+short description+dir,and include "no template/default style".
• If the user asks to see templates,show suitable options and mention previews at <skill_dir>/assets/templates/<dir>/preview.html (see Built-In Template Workflow for <skill_dir>).
• Editing/fixing/refactoring existing slides does not trigger template selection unless the user asks for a new PPT/project.

Built-In Template Workflow

Do not resolve this skill's bundled templates under .magic/skills/slide-template/. After read_skills(skill_names=["slide-template"]), read the absolute skill root from the <skill_dir> tag (or parent of <location>). In examples below, <skill_dir> is that directory. Use read_files and cp sources only as fully qualified paths: <skill_dir>/ plus the relative paths listed in this skill.

1.Load selected spec and preview gallery:

read_files(files=[
  {"file_path":"<skill_dir>/assets/templates/<dir>/visual-spec.md"},
  {"file_path":"<skill_dir>/assets/templates/<dir>/preview.html"}
])

2.Treat preview.html as the template example gallery. Before writing slides, inspect its Color Palette/Color System, Layout Page Types, and Core/Extended Components sections. Extract concrete page structures, component patterns, color-role usage, spacing rhythm, and visual anchors. For each slide, choose the closest preview layout or component pattern and adapt it to the user's content.

3.Do not copy preview wrapper styles such as preview-header, slides-grid, slide-wrap, or tiny thumbnail sizing into final slide pages. Do not link preview.html from generated slides. The preview demonstrates composition and proportions; final slides must still be fixed 1920x1080 pages using local theme.css, template CSS variables/classes, and the Google Fonts link from visual-spec.md.

4.Authority order: theme.css owns final CSS variables, fonts, decorations, components, layout helpers, and fixed canvas reset. visual-spec.md owns design rules, typography, Google Fonts link, layout types, ECharts rules, and image style guidance. preview.html demonstrates how to apply them. If preview.html conflicts with theme.css or visual-spec.md, follow theme.css/visual-spec.md and use preview only as composition guidance.

5.Before creating slide pages, summarize the template internally: palette roles, layout inventory from .slide-label, component inventory from Core/Extended Components, composition rules such as header/footer, grid columns, visual anchors, and the adaptation rule for replacing demo content while preserving structure, color roles, and rhythm.

6.Create project with create_slide_project,then copy CSS to project root before creating slide pages (use absolute source path):

shell_exec(command="cp <skill_dir>/assets/templates/<dir>/theme.css <project>/theme.css")

7.Each slide HTML must include local CSS and the Google Fonts <link> declared in visual-spec.md:

<link rel="stylesheet" href="theme.css" />

8.Load creating-slides and generate slides. Keep every slide fixed at 1920x1080; do not use responsive design. Use only template CSS variables,components,dedicated layout types,ECharts rules,and image guidance from visual-spec.md/theme.css. Prefer a matching dedicated layout from visual-spec.md or preview.html; if none fits, compose the page from template components,decorations,and layout helpers instead of generic centered text. Each slide should have one clear visual anchor, such as an image area,chart,matrix,large number,color block,or template-specific decoration.

9.Never link to skill files or assets outside the PPT project. All images/assets used by slides must be inside the PPT project,usually under images/.

Image Rules

• First decide whether the page needs images. Use images for visual layouts,cover/section/closing pages,specific person/product/scene/case,or sparse text.
• Skip image search for dense comparison,card grid,timeline/process,data dashboard,or chart pages.
• Prefer image_search. Try at least 2 content-relevant keyword groups and include template style keywords from visual-spec.md.
• If search results are poor,use generate_images and save output under the PPT project images/ folder.
• Apply template style only to creative illustrations(concept visuals,atmosphere,decorative or abstract images). Do not stylize factual photos,real people,real places,products,history/science references,brand marks,screenshots,QR codes,or data graphics.
• Images should occupy meaningful visual space; do not use them as tiny icons.
• Images can be used as local section backgrounds with an overlay when they support the content and template style.
• If a slide skips images,use a non-image visual anchor instead of leaving sparse text floating in empty space.
• Do not repeat the same background-image treatment on most consecutive slides.

Custom Template Workflow

Use when the user describes a style in text, provides screenshots, or gives an existing PPT project. Read <skill_dir>/references/custom-template-workflow.md and follow it before generating custom template files.

Style Specificity & Template Scope

• theme.css must only contain template-specific styles: color variables, background decorations, typography, template components, and visual helpers. It must NOT contain structural layout properties (padding, flex, grid) on framework-level selectors like .slide-container.
• .slide-container in theme.css should only set: dimensions (width/height), position, overflow, box-sizing, and template-specific backgrounds/colors. Layout properties (padding, margin, display: flex, flex-direction) must be defined in each slide page's own <style> block.
• Page-level <style> in each slide HTML has higher specificity than theme.css by nature of source order (page styles load after theme.css). If needed, use more specific selectors (e.g., .slide-container.my-page) to ensure page styles override template defaults.
• When writing slide pages, always define layout (padding, flex, grid) directly in the page <style> rather than relying on theme.css, to avoid cross-page style conflicts.

Output

• Built-in/custom workflow output:a complete slide project generated through creating-slides.
• Custom template output must include visual-spec.md,theme.css,preview.html.
• Do not paste raw HTML in chat.