@guru-ai-product/ai-product-kit 0.2.251113194913 → 0.2.251113203206

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -19,7 +19,7 @@ Use these MCP tools to load a Skill by name. The server maps known Skill names t
19
19
 
20
20
  <skill>
21
21
  <name>design</name>
22
- <description>Central hub for automation-ready design workflows, describing how agents split composite boards, prep visual assets, sync requirement docs, compare and verify differences between design mockups and requirements, and discover the right sub-skill before handling new mocks.</description>
22
+ <description>Central hub for automation-ready design-to-requirement workflows. When agents receive composite design boards and need to update requirement documents with new visuals, verify differences between mockups and existing docs, and sync changes systematically, they consult this index to discover the appropriate sub-skill (update-requirements-from-design) for handling design-driven requirement updates.</description>
23
23
  <tool>product_kit_skill</tool>
24
24
  <arguments>{"skill_name": "aipk_design"}</arguments>
25
25
  </skill>
package/mcp/src/server.js CHANGED
@@ -29,7 +29,7 @@ const PRODUCT_KIT_SKILLS = {
29
29
 
30
30
  // Skill 描述映射
31
31
  const SKILL_DESCRIPTIONS = {
32
- "aipk_design": "Central hub for automation-ready design workflows, describing how agents split composite boards, prep visual assets, sync requirement docs, compare and verify differences between design mockups and requirements, and discover the right sub-skill before handling new mocks.",
32
+ "aipk_design": "Central hub for automation-ready design-to-requirement workflows. When agents receive composite design boards and need to update requirement documents with new visuals, verify differences between mockups and existing docs, and sync changes systematically, they consult this index to discover the appropriate sub-skill (update-requirements-from-design) for handling design-driven requirement updates.",
33
33
  "aipk_development": "Development phase index pointing to the single authoritative implementation plan template.",
34
34
  "aipk_operations": "Canonical entry point for every post-release operating guide; maps scenarios to the available Skills and explains how to invoke them.",
35
35
  "aipk_requirements": "Central repository for requirement discovery, documentation, review, and change management assets.",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@guru-ai-product/ai-product-kit",
3
- "version": "0.2.251113194913",
3
+ "version": "0.2.251113203206",
4
4
  "description": "Sync the AI Product Kit Skill bundle through npx without cloning the repository.",
5
5
  "bin": {
6
6
  "ai-product-kit": "bin/setup.js",
@@ -1,12 +1,12 @@
1
1
  # GURU AI Snapshot
2
2
 
3
- Last refreshed: 2025-11-13T11:49:13.718Z
3
+ Last refreshed: 2025-11-13T12:32:06.548Z
4
4
 
5
5
  | File | Last Modified (UTC) |
6
6
  | --- | --- |
7
- | `auto_panel_splitter/scripts/auto_panel_splitter_bundle.js` | 2025-11-13T11:33:40.478Z |
8
- | `auto_panel_splitter/scripts/auto_panel_splitter.js` | 2025-11-12T10:41:15.854Z |
9
- | `auto_panel_splitter/scripts/panel_asset_mapper_bundle.js` | 2025-11-13T11:33:49.334Z |
10
- | `auto_panel_splitter/scripts/panel_asset_mapper.js` | 2025-11-12T10:41:15.855Z |
11
- | `auto_panel_splitter/SKILL.md` | 2025-11-13T11:34:28.517Z |
12
- | `SKILL.md` | 2025-11-13T11:01:24.584Z |
7
+ | `SKILL.md` | 2025-11-13T12:10:39.018Z |
8
+ | `update-requirements-from-design/scripts/auto_panel_splitter.js` | 2025-11-12T10:41:15.854Z |
9
+ | `update-requirements-from-design/scripts/panel_asset_mapper.js` | 2025-11-12T10:41:15.855Z |
10
+ | `update-requirements-from-design/scripts/split-design-boards-bundle.js` | 2025-11-13T11:33:40.478Z |
11
+ | `update-requirements-from-design/scripts/sync-design-to-requirements-bundle.js` | 2025-11-13T11:33:49.334Z |
12
+ | `update-requirements-from-design/SKILL.md` | 2025-11-13T12:31:35.709Z |
@@ -1,23 +1,24 @@
1
1
  ---
2
2
  name: design
3
- description: Central hub for automation-ready design workflows, describing how agents split composite boards, prep visual assets, sync requirement docs, compare and verify differences between design mockups and requirements, and discover the right sub-skill before handling new mocks.
3
+ description: Central hub for automation-ready design-to-requirement workflows. When agents receive composite design boards and need to update requirement documents with new visuals, verify differences between mockups and existing docs, and sync changes systematically, they consult this index to discover the appropriate sub-skill (update-requirements-from-design) for handling design-driven requirement updates.
4
4
  ---
5
5
 
6
6
  # 设计阶段 Skill
7
7
 
8
8
  ## 目标与适用范围
9
9
 
10
- - 统一收录设计交付相关的脚本化流程与指引,方便在需求或开发阶段前快速对齐视觉产出。
10
+ - 统一收录从设计交付到需求更新的完整脚本化流程与指引,当收到合成设计图并需要同步更新需求文档时使用。
11
11
  - 为代理和协作者提供索引,指向符合 [`../skill_generate/SKILL.md`](../skill_generate/SKILL.md) 规范的子 Skill。
12
- - 当你需要处理视觉拆分、素材入库、设计变更对齐时,先查阅此处的列表,再加载对应子 Skill。
12
+ - **当你收到设计图/视觉稿,需要切分设计板、同步更新需求文档、比对设计差异时,立即查阅此处的列表,加载 update-requirements-from-design skill**。
13
13
 
14
14
  ## 当前可用的设计 Skill
15
15
 
16
- - **Auto Panel Splitter**(`./auto_panel_splitter/`)
17
- - 使用脚本批量切分合成设计图、生成映射 CSV、同步需求文档并输出变动说明。
18
- - 包含 `./auto_panel_splitter/scripts/auto_panel_splitter.js` 与 `./auto_panel_splitter/scripts/panel_asset_mapper.js` 等自动化工具。
16
+ - **Update Requirements from Design**(`./update-requirements-from-design/`)
17
+ - 基于设计图更新需求文档的完整工作流:切分合成设计板、准备视觉资产、同步需求文档、比对验证设计与需求的差异,并生成标准的需求变动记录。
18
+ - 包含 `split-design-boards-bundle.js`(自动切分合成图)与 `sync-design-to-requirements-bundle.js`(资产映射与批量入库)等自动化工具。
19
+ - **适用场景**:任务中提到"基于设计图更新需求"、"收到合成设计稿"、"根据视觉稿修改需求"时立即使用。
19
20
 
20
- 如需扩展新的设计场景,请在 `skills/aipk_design/` 下创建子目录,按照模板完成 `SKILL.md`、`references/` 等结构,并在本文件的“当前可用的设计 Skill”中登记用途与入口路径。
21
+ 如需扩展新的设计场景,请在 `skills/aipk_design/` 下创建子目录,按照模板完成 `SKILL.md`、`references/` 等结构,并在本文件的"当前可用的设计 Skill"中登记用途与入口路径。
21
22
 
22
23
  ## 使用方式
23
24
 
@@ -1,13 +1,15 @@
1
1
  ---
2
- name: auto-panel-splitter
3
- description: Split composite design boards, align requirement docs with new visuals, and emit standardized requirement-change records.
2
+ name: update-requirements-from-design
3
+ description: Update requirement documents based on design mockups. Use this when your task involves receiving composite design boards, splitting them into panels, syncing visual assets to requirement docs, verifying differences between design mockups and existing documentation, and generating standardized change records. This skill handles the complete workflow from design assets to updated requirement documentation.
4
4
  ---
5
5
 
6
- # Auto Panel Splitter Skill
6
+ # Update Requirements from Design Skill
7
7
 
8
- 处理最新视觉稿时使用本 Skill:先用 [`./scripts/auto_panel_splitter_bundle.js`](./scripts/auto_panel_splitter_bundle.js) 自动切分设计图,再用 [`./scripts/panel_asset_mapper_bundle.js`](./scripts/panel_asset_mapper_bundle.js) 生成映射、批量入库,并同步需求文档/变动说明。
8
+ **适用场景**:收到合成设计图(多屏拼板)后,需要切分设计图、同步更新需求文档中的插图、修正文案,并输出需求变动记录。当你看到任务中提到"基于设计图更新需求文档"、"根据视觉稿修改需求"、"核对设计图并更新需求"或类似描述时,立即使用本 Skill
9
9
 
10
- > **注意**:项目已提供打包好的独立脚本,内置所有依赖(包括 sharp),无需额外安装。使用 `bundled/` 目录下的版本即可。源代码位于 `scripts/` 目录,如需修改请重新打包。
10
+ 处理流程:先用 [`./scripts/split-design-boards-bundle.js`](./scripts/split-design-boards-bundle.js) 自动切分合成设计图,再用 [`./scripts/sync-design-to-requirements-bundle.js`](./scripts/sync-design-to-requirements-bundle.js) 生成资产映射、批量入库,并同步需求文档/变动说明。
11
+
12
+ > **注意**:项目已提供打包好的独立脚本,内置所有依赖(包括 sharp),无需额外安装。源代码位于 `scripts/` 目录,如需修改请重新打包。
11
13
 
12
14
  <!-- rule: Agents must complete the entire pipeline end-to-end without依赖人工手动操作或 GUI 工具。 -->
13
15
 
@@ -43,10 +45,10 @@ graph TD
43
45
 
44
46
  ### 2.2 详细步骤
45
47
 
46
- 1. **自动切分设计图**:运行 [`scripts/auto_panel_splitter_bundle.js`](./scripts/auto_panel_splitter_bundle.js) 将合成图拆成临时 PNG(详见第3节)。
47
- 2. **生成映射模板CSV**:执行 `node scripts/panel_asset_mapper_bundle.js --source <tmp> --mapping <tmp>/mapping.csv --init-mapping`,脚本会扫描全部 PNG 并生成映射模板(详见第4节)。
48
+ 1. **自动切分设计图**:运行 [`scripts/split-design-boards-bundle.js`](./scripts/split-design-boards-bundle.js) 将合成图拆成临时 PNG(详见第3节)。
49
+ 2. **生成映射模板CSV**:执行 `node scripts/sync-design-to-requirements-bundle.js --source <tmp> --mapping <tmp>/mapping.csv --init-mapping`,脚本会扫描全部 PNG 并生成映射模板(详见第4节)。
48
50
  3. **手动填充映射信息**:在 CSV 中补齐 `panel_title`(截图上方蓝色标题原文)与 `file_slug`(希望落库的文件名,推荐 kebab-case),必要时填写 `version`、`notes`(详见第5节)。
49
- 4. **批量入库到assets目录**:确认映射后,运行 `scripts/panel_asset_mapper_bundle.js`(可指定 `--destination` 或 `--doc-slug/--iteration`)完成重命名与复制(详见第6节)。
51
+ 4. **批量入库到assets目录**:确认映射后,运行 `scripts/sync-design-to-requirements-bundle.js`(可指定 `--destination` 或 `--doc-slug/--iteration`)完成重命名与复制(详见第6节)。
50
52
  5. **更新需求文档并比对差异**:在需求文档中更新图片引用与文案,同时比对设计图与文档的一致性,记录不一致项(详见第7节)。
51
53
  6. **生成需求变动说明文档**:依照 [`需求变动说明模板`](../requirements/changes/template/需求变动说明文档模板.md) 在**需求文档版本文件夹下的 `changes/` 目录**中生成版本记录(详见第8节)。**重要**:变动说明文档必须保存在需求文档版本文件夹下的 `changes/` 目录中,例如 `../../sample/docs/requirement/v1.3.0/changes/YYYYMMDD_需求文档变动说明_*.md`。在删除 `.tmp` 目录前,必须将 `mapping.csv` 的内容以表格形式直接写入需求变动说明文档的附录中(推荐),或将其复制到需求文档版本文件夹下的 `changes/` 目录下(带时间戳命名,如 `YYYYMMDD_mapping.csv`)。同时附上脚本命令行和相关 issue/PR 链接。
52
54
  7. **清理临时文件**:完成所有步骤后,删除 `.tmp` 目录下的所有临时文件(包括切分的 PNG 和 `mapping.csv`),保持工作区整洁(详见第9节)。
@@ -64,7 +66,7 @@ graph TD
64
66
  ### 3.2 运行脚本
65
67
 
66
68
  ```bash
67
- node scripts/auto_panel_splitter_bundle.js \
69
+ node scripts/split-design-boards-bundle.js \
68
70
  --input ../design/assets/source/20241115_checkout.png \
69
71
  --output .tmp/checkout-panels \
70
72
  --prefix checkout \
@@ -94,7 +96,7 @@ node scripts/auto_panel_splitter_bundle.js \
94
96
  ### 4.2 运行脚本
95
97
 
96
98
  ```bash
97
- node scripts/panel_asset_mapper_bundle.js \
99
+ node scripts/sync-design-to-requirements-bundle.js \
98
100
  --source .tmp/checkout-panels \
99
101
  --mapping .tmp/checkout-panels/mapping.csv \
100
102
  --init-mapping
@@ -197,7 +199,7 @@ ai-calorie_10.png,11-第一阶段完成,,11-第一阶段完成,
197
199
  **资产入库命令**:
198
200
 
199
201
  ```bash
200
- node scripts/panel_asset_mapper_bundle.js \
202
+ node scripts/sync-design-to-requirements-bundle.js \
201
203
  --source .tmp/checkout-panels \
202
204
  --mapping .tmp/checkout-panels/mapping.csv \
203
205
  --destination ../../sample/docs/requirement/v1.3.0/assets \
@@ -329,9 +331,9 @@ Overwrote .tmp/ai-calorie-panels/ai-calorie_09.png -> ../../sample/docs/requirem
329
331
  - 比对差异核对表的发现(如有不一致项,见第7.2节)
330
332
  5. **包含映射信息**:在"附录"章节中必须包含 `mapping.csv` 的内容(见第6.5节)。**注意**:由于 `.tmp` 目录会在第9节被删除,因此必须将 `mapping.csv` 的内容以表格形式直接写入文档中(推荐),或先将其复制到**需求文档版本文件夹下的 `changes/`** 目录下再在文档中引用。
331
333
  6. **记录命令**:在"附录"章节中附上完整的脚本命令行,包括:
332
- - 切分命令(`scripts/auto_panel_splitter_bundle.js`,见第3节)
333
- - 生成映射命令(`scripts/panel_asset_mapper_bundle.js --init-mapping`,见第4节)
334
- - 入库命令(`scripts/panel_asset_mapper_bundle.js`,见第6节)
334
+ - 切分命令(`scripts/split-design-boards-bundle.js`,见第3节)
335
+ - 生成映射命令(`scripts/sync-design-to-requirements-bundle.js --init-mapping`,见第4节)
336
+ - 入库命令(`scripts/sync-design-to-requirements-bundle.js`,见第6节)
335
337
  - 相关 issue/PR 链接(如有)
336
338
  7. **包含核对表**:将第7.2节生成的文案/设计对齐核对表包含在文档的"文档级变动详情"或"附录"章节中。
337
339
  8. **生成文案/设计对齐核对表**:将第7.2节生成的文案/设计对齐核对表保存为 Markdown 文件到**需求文档版本文件夹下的 `check/`** 目录(如 `../../sample/docs/requirement/v1.3.0/check/YYYYMMDD_文案设计对齐核对表.md`)。**重要**:check 目录应保存的是文案/设计对齐核对表(记录设计图与需求文档的一致性比对),而非图片 diff 比对表(图片文件的哈希值比对)。核对表使用 Markdown 格式,包含表格和必要的说明文字。
@@ -356,7 +358,7 @@ Overwrote .tmp/ai-calorie-panels/ai-calorie_09.png -> ../../sample/docs/requirem
356
358
 
357
359
  ## 10. 附加资源
358
360
 
359
- - [自动切分脚本](./scripts/auto_panel_splitter_bundle.js) — 面板检测与裁切逻辑(独立打包版,内含所有依赖)
360
- - [资产映射脚本](./scripts/panel_asset_mapper_bundle.js) — 映射管理与批量入库(独立打包版,内含所有依赖)
361
+ - [切分设计板脚本](./scripts/split-design-boards-bundle.js) — 面板检测与裁切逻辑(独立打包版,内含所有依赖)
362
+ - [同步设计到需求脚本](./scripts/sync-design-to-requirements-bundle.js) — 资产映射管理与批量入库(独立打包版,内含所有依赖)
361
363
  - [需求文档 Skill](../requirements/documentation/SKILL.md) — 需求文档结构与质检
362
364
  - [需求变动 Skill](../requirements/changes/SKILL.md) — 需求变动说明模板与执行清单
@@ -1,6 +1,6 @@
1
1
  # GURU AI Snapshot
2
2
 
3
- Last refreshed: 2025-11-13T11:49:13.718Z
3
+ Last refreshed: 2025-11-13T12:32:06.548Z
4
4
 
5
5
  | File | Last Modified (UTC) |
6
6
  | --- | --- |
@@ -1,10 +1,10 @@
1
1
  # GURU AI Snapshot
2
2
 
3
- Last refreshed: 2025-11-13T11:49:13.718Z
3
+ Last refreshed: 2025-11-13T12:32:06.548Z
4
4
 
5
5
  | File | Last Modified (UTC) |
6
6
  | --- | --- |
7
7
  | `scripts/check_agents.sh` | 2025-11-13T09:03:47.702Z |
8
8
  | `skill.ini` | 2025-11-13T09:47:02.793Z |
9
9
  | `SKILL.md` | 2025-11-13T10:06:33.764Z |
10
- | `template/AGENTS_TEMPLATE.md` | 2025-11-13T11:49:13.676Z |
10
+ | `template/AGENTS_TEMPLATE.md` | 2025-11-13T12:32:06.509Z |
@@ -37,7 +37,7 @@ Usage notes:
37
37
 
38
38
  <skill>
39
39
  <name>design</name>
40
- <description>Central hub for automation-ready design workflows, describing how agents split composite boards, prep visual assets, sync requirement docs, compare and verify differences between design mockups and requirements, and discover the right sub-skill before handling new mocks.</description>
40
+ <description>Central hub for automation-ready design-to-requirement workflows. When agents receive composite design boards and need to update requirement documents with new visuals, verify differences between mockups and existing docs, and sync changes systematically, they consult this index to discover the appropriate sub-skill (update-requirements-from-design) for handling design-driven requirement updates.</description>
41
41
  <location>.claude/skills/aipk_design</location>
42
42
  </skill>
43
43
 
@@ -1,6 +1,6 @@
1
1
  # GURU AI Snapshot
2
2
 
3
- Last refreshed: 2025-11-13T11:49:13.718Z
3
+ Last refreshed: 2025-11-13T12:32:06.548Z
4
4
 
5
5
  | File | Last Modified (UTC) |
6
6
  | --- | --- |
@@ -1,6 +1,6 @@
1
1
  # GURU AI Snapshot
2
2
 
3
- Last refreshed: 2025-11-13T11:49:13.718Z
3
+ Last refreshed: 2025-11-13T12:32:06.548Z
4
4
 
5
5
  | File | Last Modified (UTC) |
6
6
  | --- | --- |
@@ -9,7 +9,7 @@ Last refreshed: 2025-11-13T11:49:13.718Z
9
9
  | `changes/template/需求变动说明文档模板.md` | 2025-11-12T10:41:15.859Z |
10
10
  | `changes/template/需求变动说明生成Prompt.md` | 2025-11-12T10:41:15.859Z |
11
11
  | `changes/template/需求变动说明生成指南.md` | 2025-11-12T10:41:15.859Z |
12
- | `documentation/SKILL.md` | 2025-11-12T10:41:15.859Z |
12
+ | `documentation/SKILL.md` | 2025-11-13T12:30:17.269Z |
13
13
  | `documentation/template/1_产品定位与分析.md` | 2025-11-12T10:41:15.860Z |
14
14
  | `documentation/template/2_功能需求.md` | 2025-11-12T10:41:15.860Z |
15
15
  | `documentation/template/3_商业化策略.md` | 2025-11-12T10:41:15.860Z |
@@ -1,14 +1,33 @@
1
1
  ---
2
2
  name: requirements-documentation
3
- description: Unified guide for requirement documentation and iteration templates, ensuring correct template selection and execution.
3
+ description: Create new requirement documents or iterate on existing ones from scratch. Use this ONLY when the task involves drafting brand-new requirement documents or conducting requirement reviews WITHOUT starting from design assets. If the task involves updating requirements from design mockups or modifying docs based on visual designs, use the design/update-requirements-from-design skill instead.
4
4
  ---
5
5
 
6
6
  # 需求文档与迭代模板指南
7
7
 
8
+ **重要区分**:本 Skill 用于**从零开始创建**需求文档或对现有文档进行**纯文本层面的迭代**。如果任务涉及"基于设计图更新需求"、"根据视觉稿修改需求文档"或任何从设计资产开始的流程,请使用 **design/update-requirements-from-design** skill 而不是本 skill。
9
+
8
10
  ## 执行指南
9
11
 
10
12
  **重要提示:本指南专为自动化文档生成设计,请严格按照以下规则执行**
11
13
 
14
+ ### 关键区分原则(必读)
15
+
16
+ **⚠️ 在继续前,请先确认你是否使用了正确的 Skill:**
17
+
18
+ - **使用本 Skill(requirements-documentation)的场景**:
19
+ - 从零开始撰写全新的需求文档
20
+ - 基于已有的需求文档进行纯文本迭代(不涉及设计图变更)
21
+ - 进行需求评审或变更管理(文档层面)
22
+
23
+ - **使用 design/update-requirements-from-design Skill 的场景**:
24
+ - 任务中提到"基于设计图更新需求"、"根据视觉稿修改需求"
25
+ - 收到合成设计图(多屏拼板)需要切分
26
+ - 需要批量更新需求文档中的插图
27
+ - 需要同步设计变更到需求文档
28
+
29
+ **如果你的任务涉及设计图处理 → 立即停止,转到 design/update-requirements-from-design skill**
30
+
12
31
  ### 执行原则
13
32
 
14
33
  1. **严格遵循模板结构**:生成文档时必须完全按照提供的模板结构,不得添加模板中未定义的章节或内容
@@ -21,12 +40,15 @@ description: Unified guide for requirement documentation and iteration templates
21
40
 
22
41
  **⚠️ 重要:在执行任何文档生成工作前,必须先完成模板选择确认**
23
42
 
43
+ **关键前置检查**:请再次确认你的任务不是从设计图更新需求!如果你的任务中提到"设计图"、"视觉稿"、"mockup"、"切分设计图"等关键词,请立即停止,转向使用 **design/update-requirements-from-design** skill。
44
+
24
45
  Agent必须遵循以下流程:
25
46
 
26
47
  1. **分析用户需求场景**:
27
48
  - 判断是新产品/功能开发(从0到1)还是现有功能迭代优化
28
49
  - 分析需求的复杂度和范围
29
50
  - 评估是否需要完整的产品定位、商业化策略等
51
+ - **关键判断**:仔细检查任务描述中是否包含"基于设计图更新需求"、"收到设计稿"、"切分设计图"等关键词。如果包含,说明应该使用 design skill 而不是本 skill
30
52
 
31
53
  2. **给出模板推荐**:
32
54
  - **推荐使用"需求文档模板"的情况**:
@@ -1,6 +1,6 @@
1
1
  # GURU AI Snapshot
2
2
 
3
- Last refreshed: 2025-11-13T11:49:13.718Z
3
+ Last refreshed: 2025-11-13T12:32:06.548Z
4
4
 
5
5
  | File | Last Modified (UTC) |
6
6
  | --- | --- |
@@ -1,6 +1,6 @@
1
1
  # GURU AI Snapshot
2
2
 
3
- Last refreshed: 2025-11-13T11:49:13.718Z
3
+ Last refreshed: 2025-11-13T12:32:06.548Z
4
4
 
5
5
  | File | Last Modified (UTC) |
6
6
  | --- | --- |