Skip to content

xinetzone/SpecWeave / .agents/skills/ppt-page

PPT Page

Verified

Create single-file HTML presentation galleries as a vertical, single-column feed of capped-width slide cards. Use for turning slide outlines, articles, screenshots, images, or existing deck content into a scrollable web PPT with below-card captions, a global page-gap/caption toggle, hidden zoom controls, fullscreen presentation shortcuts, and hover/focus-only page badges.

PPT Page

Overview

Generate a polished single-file HTML deck that reads like a vertical gallery: capped-width slide cards flow down the page in one column, captions sit under each card, and readers can click the caption/page-gap area to hide or restore all notes and page gaps. The template also supports fullscreen keyboard presentation for live review.

Use assets/template.html as the starting point and validate with scripts/validate-waterfall-deck.mjs before delivery. Keep this file as the operating checklist; use topic references for detailed rules only when the deck needs them.

Workflow

  1. Clarify only structure-changing inputs: audience, language, source material, number of cards, and whether captions are short notes or full speaker notes. If the user already provides enough material, proceed with reasonable assumptions.
  2. Create one folder per deck under PROJECT/ppt/<deck-title>/. Put the title-named HTML file and its images/ folder inside that deck folder, for example PROJECT/ppt/线性代数入门/线性代数入门.html and PROJECT/ppt/线性代数入门/images/. Do not share one top-level ppt/images/ folder across decks.
  3. Copy assets/template.html to the title-named HTML file. Use the exact deck title when filesystem-safe; otherwise sanitize invalid/confusing filename characters such as /, :, control characters, and leading/trailing whitespace. Preserve the required first line <!-- Generated by Trae Work -->. Keep image paths relative to the HTML file, such as images/01-cover.jpg.
  4. Choose exactly one visual style from references/style-presets.md unless the user specifies one. Replace [TITLE] in the document <title> and replace the sample article.deck-card blocks. Do not add a visible page-level title, subtitle, deck header, navigation chrome, or Waterfall PPT label above the first slide unless the user explicitly asks.
  5. For brand, product, or company decks, use user-provided brand guidelines when available. Otherwise look up current official sources such as the company site, press kit, logo, brand guidelines, or design system before choosing colors. If official colors are unavailable or ambiguous, state the assumption and use the closest registered preset rather than inventing a custom palette.
  6. Make a short Slide Plan before writing slide HTML. Use one row per card: Slide | Job | Content/data pattern | Layout recipe | Evidence/visual | Caption role. Read the relevant references as needed:
    • Use references/content-patterns.md when the deck teaches, compares, argues, explains mechanisms, follows a timeline, or synthesizes research.
    • Use references/data-analysis-charts.md when the deck analyzes spreadsheets, KPI, finance, experiments, surveys, funnels, cohorts, or operational metrics. Prefer proven chart frameworks such as ECharts for standard statistical charts.
    • Use references/layout-patterns.md to choose the page recipe after the content/data job is clear. Layout recipes are light code skeletons built from the template primitives; use its Template Gallery Map to copy from the closest assets/template.html sample page first, then fit content into its slots.
    • Use references/illustration-system.md for visual or embodied topics, image-led covers, photos, screenshots, logos, diagrams, generated raster images, or full-bleed backgrounds. For real products, companies, people, places, events, news, and public interfaces, look for source-backed images or screenshots first; use generated raster assets for conceptual, fictional, unavailable, or deliberately illustrative visuals.
  7. Write every slide as a self-contained card using the card/frame rules in references/design-system.md: article.deck-card, one section.slide-frame, one div.page-badge, one fixed div.slide-stage, and one details.caption immediately below the slide.
  8. For academic, scientific, mathematical, algorithm, or engineering decks, render substantive formulas professionally rather than as plain text approximations. Prefer self-contained browser-native rendering when practical.
  9. Run node <SKILL_ROOT>/scripts/validate-waterfall-deck.mjs path/to/<deck-title>.html. For company, person, product, film, TV, place, event, portfolio, or historical decks longer than 5 slides, also run the image gate:
node <SKILL_ROOT>/scripts/validate-waterfall-deck.mjs \
  path/to/<deck-title>.html \
  --min-images=4 \
  --require-local-images \
  --min-image-bytes=10000
  1. Run static validation and do lightweight local inspection when needed. Check the single-column layout, slide fitting, page-gap/caption toggle, hover/focus-only badges, nonblank charts, and local image paths. Do not repeatedly screenshot or browser-preview unless the user asks for visual QA or the layout is high risk.
  2. Default delivery is the validated HTML deck only. Do not export .pptx or .pdf automatically. In the final response, include the final HTML path with a computer:// prefix so Trae can render the deck. Add a short usage note for fullscreen mode: F enters presentation, Space/ArrowRight advances, ArrowLeft goes back, and Esc exits. Mention that PPTX or PDF export can be created on request.
  3. If the user explicitly asks for PPTX or PDF, use the bundled exporter scripts. Prefer editable PPTX when the user wants to edit content in PowerPoint, raster PPTX when visual fidelity matters more than editability, and PDF for high-fidelity sharing.

Reference Routing

  • references/style-presets.md: visual style presets, palettes, font stacks, and layout voices. Read before writing slide content.
  • assets/style-gallery.html: visual gallery of preset typography, Chinese/Japanese/English type samples, colors, radius, and border behavior. Use when choosing or comparing a style.
  • references/design-system.md: card/frame contract, typography, spacing, color, interaction, flow primitives, responsive rules, and export-safe class prefixes.
  • references/illustration-system.md: image slots, ratios, generated raster prompts, screenshot handling, visual asset density, provenance, and alt text.
  • references/layout-patterns.md: page layout recipes, slot shapes, and light HTML skeletons for statement, evidence, data, and reasoning slides.
  • references/content-patterns.md: content-heavy reasoning patterns for argument, event anatomy, causal chains, comparisons, policy matrices, evidence reading, actor networks, dense reading slides, timelines, and maps.
  • references/data-analysis-charts.md: analytical jobs, chart selection, ECharts guidance, finance/FP&A chart choices, data handling rules, and chart QA.

Core Defaults

  • Visual direction: fixed light gray page, square slide cards capped at 1440px in browsing view, one column, high-contrast slide content, quiet captions, and no visible deck header before the first slide.
  • Style selection: pick one registered preset. Use restrained presets for board, strategy, regulated, investor, policy, legal, healthcare, and executive decks; use bolder registered presets for playful, cultural, lifestyle, campaign, festival, and launch decks.
  • Layout: keep the fixed 1600x900 slide stage and scale it as a whole. Do not add viewport breakpoint overrides for slide-internal typography, padding, grid tracks, or layout gaps.
  • Interaction: preserve the template's deck-level page-gap/caption toggle, hidden zoom controls, and fullscreen presentation shortcuts. Zoom controls stay hidden at 100%, appear after Ctrl/Cmd + wheel or Ctrl/Cmd +/-, and reset with Ctrl/Cmd + 0 or the reset button. Fullscreen presentation uses F to enter, ArrowRight or Space for next slide, ArrowLeft for previous slide, and Esc to exit.
  • Content: make each slide one clear idea. Use captions for sources, caveats, and presenter commentary, but do not push all substantive teaching or comparison into captions.
  • Images: visual subjects need real/source-backed or generated raster assets. Use source search, user-provided media, screenshots, or available raster generation/editing capabilities before falling back to code-native visuals. Text-only slides are fine for thesis, definition, transition, quote, compact metric, or sensitive topics where images would be misleading or decorative.
  • Export: use scripts/export-waterfall-to-pptx.mjs or scripts/export-waterfall-to-pdf.mjs only after the user explicitly asks for that deliverable.

Final Checks

Before responding to the user:

  • Validate the HTML with the bundled script.
  • Confirm the HTML starts with <!-- Generated by Trae Work --> on line 1.
  • Confirm the final response includes the validated HTML file path with a computer:// prefix.
  • Search for [TITLE], [SUBTITLE], visible deck headers, Waterfall PPT, and sample captions.
  • Confirm every card has one .slide-frame, one .page-badge, and one details.caption.
  • Confirm page badges are hidden by default and revealed only on hover/focus.
  • Confirm captions are native <details> elements, open by default, outside .slide-frame, and controlled by a deck-level compact mode.
  • If the deck uses local images, confirm they live in the same deck folder's images/ directory, use relative paths, and load successfully.
  • For data decks, confirm chart choices match the analytical job, units are visible, source values match reviewed data, and chart containers render nonblank.
  • For technical or academic decks, confirm substantive formulas are rendered as real equations.
  • For visual-subject decks longer than 5 slides, run the image gate and do not deliver if it fails.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 196kUpdated Claude CodeCodexVerifiedInstall