version: "1.0.0" name: html-ppt-retro-quarterly-review description: | Retro Quarterly Review presentation template in a bold blue + orange editorial language. Use when users ask for a high-impact quarterly review / roadmap deck with heavyweight slab headlines, clean cream paper sections, structured grids, and fast premium motion pacing (3 slides, each hold under 3s in video mode). triggers:

• "retro quarterly review"
• "quarterly review template"
• "roadmap slide style"
• "blue orange presentation"
• "vintage business deck"
• "季度复盘复古风"
• "蓝橙复古汇报模板"

od: mode: template surface: video type: hyperframes platform: desktop preview: type: html entry: index.html reload: debounce-100 outputs: primary: index.html secondary:

• template.html
• example.html

capabilities_required:

• file_write

Retro Quarterly Review Template

A high-contrast, print-inspired quarterly review template with three cinematic slides:

1. Cover (hero title lockup)
2. Three priorities (triptych grid)
3. Roadmap timeline + KPI strip

Resource map

html-ppt-retro-quarterly-review/
├── SKILL.md
├── assets/
│   └── template.html
├── references/
│   └── checklist.md
└── example.html

Workflow

1. Read active DESIGN.md first and map any requested token changes into CSS

variables while preserving the retro blue/orange/cream visual grammar.

1. Start from assets/template.html; do not rebuild from scratch.
2. Preserve the three-slide information architecture and typographic hierarchy.
3. Keep interactions and motion quality:

• keyboard 1/2/3 quick jump
• R restart
• page indicator updates per scene
• premium wipe transitions and staggered reveals

1. Keep output self-contained (single HTML, inline CSS + JS, no framework runtime).
2. If adapting copy/data, keep content realistic and internally consistent.
3. Validate against references/checklist.md before emitting artifact.

Output contract

Emit one short orientation sentence and then the artifact:

<artifact identifier="retro-quarterly-review" type="text/html" title="Retro Quarterly Review">
<!doctype html>
<html>...</html>
</artifact>

SenWeaverCoding strengthening

Hard requirements for every artifact this skill produces inside Designer mode, regardless of the workflow above:

• Bind to the active design system. Pull palette, type, spacing, and

radius from the selected DESIGN.md / tokens.css; never hardcode an off-token palette or invent a second accent.

• Apply the craft layer. Honour the injected craft references

(typography, color, anti-ai-slop, state-coverage, accessibility) — they are P0 self-checks at the critique stage, not suggestions.

• Write into the session directory so the artifact appears in the

per-session canvas; keep files self-contained (inline assets, no external CDNs that break in the sandboxed iframe).

• Use real content, never filler. No Lorem Ipsum, no invented metrics,

no placeholder copy — compose to fill empty space.

• Generate, don't transcribe — the template is scaffolding; the

shipped artifact must carry the brief's real content.

<!-- swc-strengthened -->