5dd70b5016
Some checks failed
ci / Validate workspace (push) Successful in 12m32s
landing-page-ci / Validate landing page (push) Successful in 9m41s
landing-page-deploy / Deploy landing page (push) Failing after 5m23s
github-metrics / Generate repository metrics SVG (push) Failing after 2m3s
refresh-contributors-wall / Refresh contributors wall cache bust (push) Failing after 11s
This repository contains the open-design daemon CLI source code, built and packaged at https://helix-mind.ai/cli/open-design/latest.tgz for use by the HelixMind /design slash command. Licenses: Apache-2.0 (root) + MIT (skills/*)
79 lines
4.2 KiB
Markdown
79 lines
4.2 KiB
Markdown
---
|
||
name: html-ppt-weekly-report
|
||
description: Team weekly / status-update deck — corporate clarity, 8-cell KPI grid, shipped list, 8-week bar chart, next-week table. Use for 周报, business reviews, team status updates, and exec dashboards.
|
||
triggers:
|
||
- "weekly report"
|
||
- "周报"
|
||
- "status update"
|
||
- "team report"
|
||
- "business review"
|
||
- "wbr"
|
||
od:
|
||
mode: deck
|
||
scenario: operations
|
||
featured: 23
|
||
upstream: "https://github.com/lewislulu/html-ppt-skill"
|
||
preview:
|
||
type: html
|
||
entry: index.html
|
||
design_system:
|
||
requires: false
|
||
speaker_notes: true
|
||
animations: true
|
||
example_prompt: "用 html-ppt-weekly-report 模板生成一份周报（7 页）。先问我四件事：本周时间范围、3-5 个核心 KPI 数字、本周已发布 / 已完成的事项、下周计划与风险。然后用模板填好 8 周柱状图和下周表格。"
|
||
---
|
||
# HTML PPT · Weekly Report
|
||
|
||
A focused entry point into the [`html-ppt`](../html-ppt/SKILL.md) master skill that lands the user directly on the **`weekly-report`** full-deck template.
|
||
|
||
## When this card is picked
|
||
|
||
The Examples gallery wires "Use this prompt" to the example_prompt above. When you accept that prompt, this card is the right pick if the user wants exactly the visual identity of `weekly-report` (see the upstream [full-decks catalog](../html-ppt/references/full-decks.md) for screenshots and rationale).
|
||
|
||
## How to author the deck
|
||
|
||
1. **Read the master skill first.** All authoring rules live in
|
||
[`skills/html-ppt/SKILL.md`](../html-ppt/SKILL.md) — content/audience checklist,
|
||
token rules, layout reuse, presenter mode, the keyboard runtime, and the
|
||
"never put presenter-only text on the slide" rule.
|
||
2. **Start from the matching template folder:**
|
||
`skills/html-ppt/templates/full-decks/weekly-report/` — copy `index.html` and
|
||
`style.css` into the project, keep the `.tpl-weekly-report` body class.
|
||
3. **Bring the shared runtime with the template.** The upstream
|
||
`index.html` links the shared CSS/JS via `../../../assets/...` because it
|
||
sits three folders deep inside `skills/html-ppt/templates/full-decks/`.
|
||
Once you copy `index.html` into the project, those parent-relative URLs
|
||
no longer resolve and `base.css`, `animations.css`, and `runtime.js`
|
||
will 404 — meaning the deck never activates and slide navigation is
|
||
dead. Pick one of these two recipes per project:
|
||
- **Recipe A — copy + rewrite (preferred):** copy
|
||
`skills/html-ppt/assets/fonts.css`, `skills/html-ppt/assets/base.css`,
|
||
`skills/html-ppt/assets/animations/animations.css`, and
|
||
`skills/html-ppt/assets/runtime.js` into a project-local
|
||
`assets/` (with `assets/animations/animations.css`), then rewrite the
|
||
four `<link>`/`<script>` tags in `index.html` from
|
||
`../../../assets/...` to the matching project-local paths
|
||
(`assets/fonts.css`, `assets/base.css`,
|
||
`assets/animations/animations.css`, `assets/runtime.js`).
|
||
- **Recipe B — inline:** read the same four files and replace each
|
||
`<link rel="stylesheet" href="../../../assets/...">` with a
|
||
`<style>...</style>` containing the file's contents, and the
|
||
`<script src="../../../assets/runtime.js">` with a
|
||
`<script>...</script>` containing `runtime.js`. Yields a single
|
||
self-contained `index.html`.
|
||
Either way, do not ship the upstream `../../../assets/...` URLs
|
||
verbatim into a project artifact — they only work in-tree.
|
||
4. **Pick a theme.** Default tokens look fine; if the user wants a different
|
||
feel, swap in any of the 36 themes from `skills/html-ppt/assets/themes/*.css`
|
||
via `<link id="theme-link">` and let `T` cycle.
|
||
5. **Replace demo content, not classes.** The `.tpl-weekly-report` scoped CSS only
|
||
recognises the structural classes shipped in the template — keep them.
|
||
6. **Speaker notes go inside `<aside class="notes">` or `<div class="notes">`** — never as visible text on the slide.
|
||
|
||
## Attribution
|
||
|
||
Visual system, layouts, themes and the runtime keyboard model come from
|
||
the upstream MIT-licensed [`lewislulu/html-ppt-skill`](https://github.com/lewislulu/html-ppt-skill). The
|
||
LICENSE file ships at `skills/html-ppt/LICENSE`; please keep it in place when
|
||
redistributing.
|