菜单
Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/leewayworks/guochuang-gps --skill deck命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | deck |
| description | Use when outlining, reviewing, or rehearsing a Guochuang pitch deck, project-book presentation, slide narrative, or visual evidence sequence. |
Apply the shared policies in gps-common. When saving a Markdown report, use the common project-name rule with topic PPT.
Design the deck as a sequence of reviewer decisions. Each slide needs one conclusion, one visual job and one evidence pointer.
A common technical or venture spine is:
value in one sentence -> real problem -> field finding -> intervention -> mechanism -> baseline and metric -> validation -> user or scene -> alternatives -> IP and student work -> customer and economics -> growth -> social value -> ask.
Change the order when the track demands it. For an industry project, make the chain visible: enterprise question -> response -> demonstrator -> expert questions. For red-tour, show participation and beneficiary change early.
For each page fill: no, purpose, headline, visual, evidence_ids, speaker cue, risk and cut priority.
The headline should state the conclusion, not the topic. Put units, sample size, date and source beside a number. Keep project-book, slide and spoken figures identical. Label image-only pages visual review required; missing extracted text is not proof that a page is empty.
Prepare three versions:
Never cut the only baseline, limitation or student-contribution evidence. Timing, page count, font and effects are local rules until the 2026 evaluation notice or a school or provincial notice confirms them.
Check headline clarity, legibility, source and date, units, number consistency, ownership, privacy, transitions, screen readability and unsupported superlatives. End with the two claims the team wants the reviewer to remember and the evidence that supports each.
See references/slide-patterns.md for historical patterns.