---
name: enterprise-exchange-deck
description: Use when preparing enterprise executive exchange materials, customer/partner meeting decks, AI transformation discussion decks, or when the user says "把这些交流问题做成课件", "按科大讯飞这一版风格", "企业交流会课件", "前端技术做课件", "逐页检查并发布". This skill turns raw questions, prior articles, notes, or Markdown into a polished self-contained HTML slide deck with the same structure, visual effects, navigation, print behavior, sanitation, and slide-by-slide QA discipline as the 科大讯飞交流会 reference deck.
version: 1.0.0
updated: 2026-05-28
reference: references/kdxf_reference_deck.html
---

# 企业交流会 HTML 课件

Use this skill to turn enterprise exchange topics, meeting questions, prior articles, Markdown notes, or rough talking points into a polished browser-based courseware deck. The reference quality target is the 科大讯飞交流会 deck bundled in `references/kdxf_reference_deck.html`.

The expected output is not a generic PPT outline. It is a self-contained HTML deck that feels like a consulting-style discussion material: one clear judgment per page, enough substance for a real conversation, calm business visuals, keyboard navigation, print mode, responsive layout, and slide-by-slide QA before delivery.

## Default Output

Create these outputs unless the user asks for something narrower:

- A sanitized answer memo in Markdown.
- A self-contained HTML deck.
- A QA folder with screenshots or a contact sheet and a report.
- A public URL when the user explicitly asks to publish.
- A short delivery note with file path, URL if any, and verification result.

## Reference Standard

The 科大讯飞 reference deck is the canonical style sample:

- HTML: `references/kdxf_reference_deck.html`
- Memo: `references/kdxf_reference_memo.md`
- Contact sheet: `references/kdxf_reference_contact_sheet.jpg`
- QA report: `references/kdxf_reference_qa_report.json`

Read the reference deck when exact visual behavior matters. Reuse its layout shell, color discipline, controls, progress bar, slide aspect ratio, print CSS, and text density principles.

## Visual Direction

Use the bundled light business palette by default:

- Background: light blue-gray to warm ivory.
- Page: ivory/white.
- Main text: blue-gray, not pure black.
- Primary accent: restrained sky/steel blue.
- Secondary accent: champagne gold.
- Avoid dark green, black theme, red theme, and purple theme unless the user explicitly changes preference.

Read `references/style_contract.md` before implementing.

## Workflow

1. **Convert input into meeting answer logic**
   - Extract the meeting context, company, topic list, user stance, and reusable judgments.
   - If prior articles are available in the workspace, use them as source logic, but do not expose that provenance in the public deck.
   - If content is missing, fill it with a conservative enterprise AI/process/platform governance viewpoint.
   - Produce or update a Markdown memo first for reasoning clarity.

2. **Build a narrative spine**
   - Start with one framing judgment.
   - Cluster questions into 2-4 thematic groups.
   - Give each question a "core answer + expanded logic + operating method" structure.
   - End with practical next steps, pilot path, or reusable closing lines.
   - Preserve the user's full argument. Do not over-compress a substantial memo into slogans.

3. **Create the HTML deck**
   - Prefer 18-28 slides for a strategic exchange deck.
   - Use one main idea per slide.
   - Use the reference shell: 16:9 stage, `.slide` articles, `.topline`, `.footer`, previous/next buttons, progress bar, keyboard navigation, hash navigation, and print CSS.
   - Use layouts from `references/layout_patterns.md`.
   - If useful, run `scripts/build_deck.mjs` with `templates/deck_content.template.json` as a starting point.

4. **Sanitize public-facing wording**
   - Remove references to "my prior article", "based on what you wrote", approval history, internal chat, internal IDs, private names, and source provenance.
   - Keep the point of view, but make it read as a clean meeting material.
   - Do not include "批准", "引用", "旧文", "你之前", "内部来源", or similar process words in the deck body.

5. **QA every slide**
   - Open the deck and check every page.
   - Run visual checks for overflow, text overlap, clipped content, blank pages, bad public wording, and navigation.
   - Prefer using `scripts/check_deck.mjs` when a local Chrome is available.
   - Fix issues and re-run checks before claiming completion.

6. **Publish only when requested**
   - For public sharing, deploy the static HTML folder to the available host requested by the user or already configured in the workspace.
   - Verify the public URL returns HTTP 200 and render-check at least the first page and all slide hashes if time allows.

## Deck Structure

For enterprise exchange decks, this structure usually works:

1. Cover: company/topic and three framing claims.
2. Opening position: one strong judgment.
3. Discussion map: cluster all questions into themes.
4. Question pages: 1-2 slides per question.
5. Operating mechanism: governance, assets, control plane, process, metrics.
6. Pilot path: 60/90-day action plan.
7. Reusable lines: meeting-ready closing statements.
8. Closing: one final judgment and next steps.

## Layout Rules

- Use title + visual structure, not title + long paragraph only.
- Use two-column "core answer/detail" pages for complex questions.
- Use matrices for platform layers, asset categories, capability maps, vendor requirements.
- Use checklists for governance mechanisms and evaluation rules.
- Use step strips for methods, roadmaps, pilots, and transformation paths.
- Split a crowded slide instead of shrinking text.
- Keep the style calm and substantial. No decorative blobs, no purple AI gradient, no marketing hero page.

## QA Rules

Before final delivery:

- Slide count is intentional and all slides can be reached.
- Desktop viewport has no visible overlap, clipping, or out-of-frame elements.
- Mobile mode preserves reading order.
- Keyboard navigation works.
- Print CSS reveals all slides.
- Public deck contains no internal provenance or private workflow wording.
- If user specified colors, scan the CSS and screenshots against that preference.

Read `references/qa_checklist.md` for the full checklist.

## Optional Scripts

The scripts are helpers, not a substitute for judgment:

- `scripts/build_deck.mjs`: builds an HTML deck from a structured JSON file while reusing the reference CSS/JS shell.
- `scripts/check_deck.mjs`: opens every slide in Chrome, captures screenshots, and writes a QA report.

Example:

```bash
node scripts/build_deck.mjs templates/deck_content.template.json outputs/demo.html
node scripts/check_deck.mjs outputs/demo.html outputs/demo_qa
```

## Delivery Note Template

```markdown
已完成：<HTML 文件路径>
公网地址：<URL，如有>
参考风格：科大讯飞交流会这一版
检查结果：已逐页检查 <N> 页，无文字堆叠、溢出、遮挡；已清理内部来源/引用/批准类表述。
```

