Build HTML Sharing Report / 构建 HTML 分享汇报

Create a short report that behaves like a browser-native deck while remaining an editable web artifact. Optimize for presenting, reviewing, and sharing a decision story rather than reproducing PowerPoint styling.

把阶段复盘、方案说明或内部分享整理成可编辑的网页式汇报。重点是清晰讲述、快速跳转和证据可追溯，不追求模拟 PowerPoint 的装饰效果。

Confirm the communication job / 确认沟通任务

Before editing, state:

• audience and presenting context;
• the one outcome the audience should reach;
• the central takeaway;
• available evidence, source files, and links;
• confidentiality, redaction, and publishing boundaries;
• target delivery mode: local file, repository route, static host, or exported package.

开始前明确听众、现场语境、核心结论、证据、来源、脱敏范围和交付方式。

Ask one focused question only when a missing answer changes the narrative, confidentiality boundary, or delivery route. Otherwise continue with labeled assumptions.

Plan a short cumulative narrative / 规划递进叙事

Read references/report-contract.md before implementation. Use 4–12 steps by default. Give each step:

• one narrative job;
• one takeaway-style title;
• a short explanation;
• one useful evidence block or source link;
• an implication, decision gate, or next action.

Prefer a cumulative arc such as context → signal → insight → response → evidence → next step. Remove agenda-only steps, repeated summaries, unsupported claims, decorative metrics, and generic closing pages.

默认控制在 4–12 步。每一步只承担一个叙事任务，并用结论标题、简短解释、证据和下一步形成递进关系。不要编造数据、人物、引语或结果。

Choose the implementation surface / 选择实现载体

Use the smallest suitable route:

1. extend an existing project route when the report belongs to that project;
2. create an isolated report folder when it must remain reversible;
3. copy assets/clickthrough-report-template.html for a standalone, dependency-free starting point.

Treat the supplied template as a starting asset. Copy it into the task workspace and edit the copy; never write user content back into the installed Skill.

Use project-native tooling and components when an existing application already supplies them. Avoid adding a framework or dependency for a simple standalone report. Do not change an existing production entry, navigation default, or public deployment unless that change is explicitly in scope.

优先复用现有项目路由；需要隔离时创建独立目录；单文件交付可复制附带模板。不要为了简单汇报引入新的框架，也不要默认替换生产入口或直接发布。

Build the navigation contract / 建立跳转契约

Every report must provide:

• visible current step and total count;
• previous and next controls with correct disabled states;
• direct step navigation;
• Left/Right Arrow plus Home/End keyboard behavior;
• visible focus and logical tab order;
• a stable URL hash or equivalent direct link for each step;
• touch-friendly controls and a responsive small-screen layout;
• reduced-motion behavior.

Number-key shortcuts and fullscreen controls are recommended when they fit the report. Never trap the user in fullscreen, hijack browser Back, or make hover the only way to reach information.

每份汇报必须支持当前页码、前后跳转、章节直达、左右键、Home/End、焦点可见、可复制的章节链接、触屏操作和 reduced motion。全屏必须可退出，浏览器返回行为必须保持正常。

Keep evidence inspectable / 保持证据可检查

Use real, authorized material. For every non-trivial claim or visual:

• identify the source and freshness;
• link to the approved source when the delivery context allows it;
• distinguish observed fact, interpretation, proposal, and open question;
• label placeholders and missing evidence;
• preserve asset rights and attribution requirements.

Do not publish local usernames, absolute paths, credentials, private URLs, customer or partner names, file keys, node IDs, unpublished product names, proprietary fonts, or confidential screenshots. Replace sensitive examples with neutral placeholders before creating public artifacts.

使用真实且获授权的材料；区分事实、判断、提案与待确认项。公开版本不得包含本地用户名、绝对路径、凭证、私有 URL、客户名、文件 Key、节点 ID、未发布产品、专有字体和机密截图。

Compose for presentation / 按现场讲述排版

• Keep one primary visual composition per step.
• Use at least 24 px page-edge spacing on small screens and balanced margins on larger screens.
• Keep titles short enough to avoid awkward wraps.
• Shorten copy before shrinking type.
• Use one restrained accent color unless a supplied design system requires more.
• Prefer system fonts or approved web fonts with a legal fallback.
• Preserve sufficient contrast and avoid placing essential meaning in color alone.
• Use media only when it advances the current claim; provide meaningful alternatives.

每一步保持一个主要视觉构图；小屏页边距至少 24 px；标题避免难看的换行；文字过多时先删减；默认使用一种强调色和可合法分发的字体。

Validate the finished report / 验证完成稿

Use browser automation or the project's existing test stack to check the actual output at representative desktop and mobile viewports. Verify:

• every step and deep link loads the intended content;
• all navigation paths, disabled states, and keyboard shortcuts work;
• no text clips, overlaps, or overflows;
• images load, crop correctly, and include alternatives;
• focus, landmarks, labels, contrast, and reading order are usable;
• reduced motion is honored;
• no console errors or broken local references remain;
• the report works in its promised delivery mode;
• public output passes the privacy scan.

Record each check as pass, fail, or blocked. Do not claim a check passed without evidence. Stop and report the blocker when required evidence is missing, confidential material cannot be safely redacted, or delivery would require an unapproved deployment or production-route change.

Required output / 必须输出

Return:

1. the report path or approved URL;
2. audience, communication job, and step count;
3. navigation and responsive behaviors implemented;
4. sources, placeholders, and privacy decisions;
5. browser QA results and tested viewports;
6. remaining risks, blockers, and publication status.

交付时说明文件或链接、听众与叙事目标、步骤数、跳转方式、响应式行为、来源与脱敏决定、浏览器 QA 和剩余风险。