@guru-ai-product/ai-product-kit 0.2.251117191453 → 0.2.251117213210

package/bin/setup.js

@@ -284,19 +284,50 @@ function mergeAgentsContent(existingContent, newTemplate) {
 function parseTemplate(template) {
   const parts = {};
 
-  const projectOverviewMatch = template.match(/# Project Overview\s*\n([\s\S]*?)(?=\n## Conventions|<skills_system|$)/);
-  if (projectOverviewMatch) {
-    parts.projectOverview = `# Project Overview\n${projectOverviewMatch[1].trim()}`;
+  const projectOverviewIndex = template.indexOf('# Project Overview');
+  if (projectOverviewIndex !== -1) {
+    const afterProjectOverview = template.substring(projectOverviewIndex);
+    const conventionsIndex = afterProjectOverview.indexOf('\n## Conventions');
+    if (conventionsIndex !== -1) {
+      parts.projectOverview = afterProjectOverview.substring(0, conventionsIndex).trim();
+    } else {
+      const skillsSystemTagMatch = afterProjectOverview.match(/<skills_system[\s>]/);
+      if (skillsSystemTagMatch) {
+        const skillsSystemTagIndex = afterProjectOverview.indexOf(skillsSystemTagMatch[0]);
+        parts.projectOverview = afterProjectOverview.substring(0, skillsSystemTagIndex).trim();
+      } else {
+        parts.projectOverview = afterProjectOverview.trim();
+      }
+    }
   }
 
-  const conventionsMatch = template.match(/## Conventions\s*\n([\s\S]*?)(?=\n## Skills Bundle Access|<skills_system|$)/);
-  if (conventionsMatch) {
-    parts.conventions = `## Conventions\n${conventionsMatch[1].trim()}`;
+  const conventionsIndex = template.indexOf('## Conventions');
+  if (conventionsIndex !== -1) {
+    const afterConventions = template.substring(conventionsIndex);
+    const skillsBundleAccessIndex = afterConventions.indexOf('\n## Skills Bundle Access');
+    if (skillsBundleAccessIndex !== -1) {
+      parts.conventions = afterConventions.substring(0, skillsBundleAccessIndex).trim();
+    } else {
+      const skillsSystemTagMatch = afterConventions.match(/<skills_system[\s>]/);
+      if (skillsSystemTagMatch) {
+        const skillsSystemTagIndex = afterConventions.indexOf(skillsSystemTagMatch[0]);
+        parts.conventions = afterConventions.substring(0, skillsSystemTagIndex).trim();
+      } else {
+        parts.conventions = afterConventions.trim();
+      }
+    }
   }
 
-  const skillsBundleAccessMatch = template.match(/## Skills Bundle Access\s*\n([\s\S]*?)(?=<skills_system|$)/);
-  if (skillsBundleAccessMatch) {
-    parts.skillsBundleAccess = `## Skills Bundle Access\n${skillsBundleAccessMatch[1].trim()}`;
+  const skillsBundleAccessIndex = template.indexOf('## Skills Bundle Access');
+  if (skillsBundleAccessIndex !== -1) {
+    const afterSkillsBundleAccess = template.substring(skillsBundleAccessIndex);
+    const skillsSystemTagMatch = afterSkillsBundleAccess.match(/<skills_system[\s>]/);
+    if (skillsSystemTagMatch) {
+      const skillsSystemTagIndex = afterSkillsBundleAccess.indexOf(skillsSystemTagMatch[0]);
+      parts.skillsBundleAccess = afterSkillsBundleAccess.substring(0, skillsSystemTagIndex).trim();
+    } else {
+      parts.skillsBundleAccess = afterSkillsBundleAccess.trim();
+    }
   }
 
   const skillsSystemMatch = template.match(/<skills_system[\s\S]*?<\/skills_system>/);

package/mcp/skills/aipk_init_project/template/AGENTS_TEMPLATE.md

@@ -20,77 +20,77 @@ Use these MCP tools to load a Skill by name. The server maps known Skill names t
 
 <skill>
 <name>aipk_aso-new-release</name>
-<description>This skill should be used when generating ASO content for a new app version, covering update notes and refreshed store asset guidance.</description>
+<description>Workflow for crafting App Store/Google Play release notes and store asset briefs for a new version; use when shipping a release and avoid internal-only notes or unrelated marketing assets.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_aso-new-release"}</arguments>
 </skill>
 
 <skill>
 <name>aipk_format-requirement-pages-with-design</name>
-<description>Format requirement document pages with design images into standardized tables. Use when requirement documents contain design images and need to be organized into a two-column table format (page description | design image) following the project's table formatting standards.</description>
+<description>Format requirement document pages that include design images into standardized two-column tables so page descriptions and visuals align with project standards; use when visuals exist, not when no design images or unrelated doc tasks are needed.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_format-requirement-pages-with-design"}</arguments>
 </skill>
 
 <skill>
 <name>aipk_initiative-planning</name>
-<description>Comprehensive workflow for evaluating, scoping, and approving new product initiatives.</description>
+<description>Structure initiative evaluation and scoping to align strategy, feasibility, and risk before formal requirements; use for new product or major feature planning and steer clear of design sync, doc tweaks, or execution-phase work.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_initiative-planning"}</arguments>
 </skill>
 
 <skill>
 <name>aipk_requirements-changes</name>
-<description>Templates, prompts, and procedures for documenting and reviewing requirement changes.</description>
+<description>Templates, prompts, and procedures for documenting requirement changes, including structured overviews and diff analysis; use for any change to requirement docs and avoid new requirement drafting or unrelated engineering work.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_requirements-changes"}</arguments>
 </skill>
 
 <skill>
 <name>aipk_requirements-documentation</name>
-<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 `skills/update-requirements-from-design` skill instead.</description>
+<description>Guide for drafting new requirement docs or iterating existing ones textually; apply when starting from scratch or doing template-compliant text updates without design assets, and avoid design-driven updates or implementation/test tasks.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_requirements-documentation"}</arguments>
 </skill>
 
 <skill>
 <name>aipk_requirements-intake</name>
-<description>Intelligent intake pipeline for gathering and consolidating product requirements from multiple sources.</description>
+<description>Structured intake pipeline combining Gemini DeepResearch with multi-platform data to discover product needs; use during early-stage opportunity validation and avoid it once requirements are defined or when design/dev tasks begin.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_requirements-intake"}</arguments>
 </skill>
 
 <skill>
 <name>aipk_update-requirements-from-design</name>
-<description>Update requirement documents based on design mockups (composite boards or individual UI frames). Use this when you need to split composite boards or directly align single/multiple standalone UI images with requirement docs, including syncing visuals, verifying differences, and generating change records.</description>
+<description>Sync requirement docs with design mockups (composite or standalone UI frames) via split/mapping scripts, capturing visual alignment and change records; use this when design assets drive the update and avoid pure text-only work.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_update-requirements-from-design"}</arguments>
 </skill>
 
 <skill>
 <name>development</name>
-<description>Development phase index pointing to the single authoritative implementation plan template.</description>
+<description>Index for the single authoritative implementation plan template covering development execution, so use it when planning dev deliverables and not for unrelated coding or testing notes.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_development"}</arguments>
 </skill>
 
 <skill>
 <name>init-project</name>
-<description>Initialize the project Agents playbook, sync the skills inventory into AGENTS.md/templates, and verify the workspace includes a complete AGENTS.md file.</description>
+<description>Ensure AGENTS.md and skills inventories match the template during onboarding or audits; use for Agents initwork and skip it for ordinary business content or document creation.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_init_project"}</arguments>
 </skill>
 
 <skill>
 <name>skill-creation</name>
-<description>Standards and practices for creating new Agent Skills that extend Claude with reusable workflows, documentation, and tooling assets.</description>
+<description>Playbook for creating or refreshing Skills so metadata, templates, and scripts meet Claude’s expectations; use when scaffolding Skills or syncing bundles, not for unrelated product content.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_skill_generate"}</arguments>
 </skill>
 
 <skill>
 <name>tool_prompts</name>
-<description>Directory of curated tool prompts, their core strengths, calling scenarios, input/output expectations, and the Markdown files that describe how to run them.</description>
+<description>Catalog of curated tool prompts with strengths, scenarios, and I/O rules for reuse; refer to it when consuming or extending prompts, not when writing unrelated product docs or new Skills.</description>
 <tool>product_kit_skill</tool>
 <arguments>{"skill_name": "aipk_tool_prompts"}</arguments>
 </skill>

package/mcp/src/server.js

@@ -33,16 +33,16 @@ const PRODUCT_KIT_SKILLS = {
 
 // Skill 描述映射
 const SKILL_DESCRIPTIONS = {
-  "aipk_aso-new-release": "This skill should be used when generating ASO content for a new app version, covering update notes and refreshed store asset guidance.",
-  "aipk_development": "Development phase index pointing to the single authoritative implementation plan template.",
-  "aipk_format-requirement-pages-with-design": "Format requirement document pages with design images into standardized tables. Use when requirement documents contain design images and need to be organized into a two-column table format (page description | design image) following the project's table formatting standards.",
-  "aipk_initiative-planning": "Comprehensive workflow for evaluating, scoping, and approving new product initiatives.",
-  "aipk_requirements-changes": "Templates, prompts, and procedures for documenting and reviewing requirement changes.",
-  "aipk_requirements-documentation": "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 `skills/update-requirements-from-design` skill instead.",
-  "aipk_requirements-intake": "Intelligent intake pipeline for gathering and consolidating product requirements from multiple sources.",
-  "aipk_skill_generate": "Standards and practices for creating new Agent Skills that extend Claude with reusable workflows, documentation, and tooling assets.",
-  "aipk_tool_prompts": "Directory of curated tool prompts, their core strengths, calling scenarios, input/output expectations, and the Markdown files that describe how to run them.",
-  "aipk_update-requirements-from-design": "Update requirement documents based on design mockups (composite boards or individual UI frames). Use this when you need to split composite boards or directly align single/multiple standalone UI images with requirement docs, including syncing visuals, verifying differences, and generating change records.",
+  "aipk_aso-new-release": "Workflow for crafting App Store/Google Play release notes and store asset briefs for a new version; use when shipping a release and avoid internal-only notes or unrelated marketing assets.",
+  "aipk_development": "Index for the single authoritative implementation plan template covering development execution, so use it when planning dev deliverables and not for unrelated coding or testing notes.",
+  "aipk_format-requirement-pages-with-design": "Format requirement document pages that include design images into standardized two-column tables so page descriptions and visuals align with project standards; use when visuals exist, not when no design images or unrelated doc tasks are needed.",
+  "aipk_initiative-planning": "Structure initiative evaluation and scoping to align strategy, feasibility, and risk before formal requirements; use for new product or major feature planning and steer clear of design sync, doc tweaks, or execution-phase work.",
+  "aipk_requirements-changes": "Templates, prompts, and procedures for documenting requirement changes, including structured overviews and diff analysis; use for any change to requirement docs and avoid new requirement drafting or unrelated engineering work.",
+  "aipk_requirements-documentation": "Guide for drafting new requirement docs or iterating existing ones textually; apply when starting from scratch or doing template-compliant text updates without design assets, and avoid design-driven updates or implementation/test tasks.",
+  "aipk_requirements-intake": "Structured intake pipeline combining Gemini DeepResearch with multi-platform data to discover product needs; use during early-stage opportunity validation and avoid it once requirements are defined or when design/dev tasks begin.",
+  "aipk_skill_generate": "Playbook for creating or refreshing Skills so metadata, templates, and scripts meet Claude’s expectations; use when scaffolding Skills or syncing bundles, not for unrelated product content.",
+  "aipk_tool_prompts": "Catalog of curated tool prompts with strengths, scenarios, and I/O rules for reuse; refer to it when consuming or extending prompts, not when writing unrelated product docs or new Skills.",
+  "aipk_update-requirements-from-design": "Sync requirement docs with design mockups (composite or standalone UI frames) via split/mapping scripts, capturing visual alignment and change records; use this when design assets drive the update and avoid pure text-only work.",
   "aipk_init_project": "Initialize the project Agents playbook, sync the skills inventory into AGENTS.md/templates, and verify the workspace includes a complete AGENTS.md file.",};
 
 const server = new Server(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@guru-ai-product/ai-product-kit",
-  "version": "0.2.251117191453",
+  "version": "0.2.251117213210",
   "description": "Sync the AI Product Kit Skill bundle through npx without cloning the repository.",
   "bin": {
     "ai-product-kit": "bin/setup.js",

package/skills/aipk_aso-new-release/GURU_AI.md

@@ -1,9 +1,9 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
 | `references/aso-update-notes-prompt.md` | 2025-11-12T10:41:15.857Z |
 | `references/aso-update-notes-template.md` | 2025-11-12T10:41:15.857Z |
-| `SKILL.md` | 2025-11-17T09:13:53.653Z |
+| `SKILL.md` | 2025-11-17T13:24:42.134Z |

package/skills/aipk_aso-new-release/SKILL.md

@@ -1,10 +1,24 @@
 ---
 name: aipk_aso-new-release
-description: This skill should be used when generating ASO content for a new app version, covering update notes and refreshed store asset guidance.
+description: Workflow for crafting App Store/Google Play release notes and store asset briefs for a new version; use when shipping a release and avoid internal-only notes or unrelated marketing assets.
 ---
 
 # ASO New Release Skill
 
+## Skill Scope
+
+**Purpose**: Provide a step-by-step workflow and templates for generating App Store/Google Play update notes and complementary store asset guidance each time a new version ships.
+
+**Applicable scenarios**:
+- Launching a new product version that requires narrative-aligned update notes and refreshed store assets.
+- Coordinating keyword-focused copy, visuals, and launch messaging across App Store and Play Store listings.
+- Translating release highlights, UX improvements, or new functionality into persuasive marketing copy for stores.
+
+**Not applicable when**:
+- The task is general marketing collateral without a specific app release or store update.
+- You only need internal release notes or engineering change logs.
+- Assets are unrelated to App Store or Google Play listings (e.g., social/PR materials).
+
 Use this skill whenever a product version ships and the team needs polished, on-brand App Store and Google Play content that highlights the release. Follow the steps below to transform raw release inputs into persuasive update copy and actionable store asset briefs.
 
 ## When to Use

package/skills/aipk_development/GURU_AI.md

@@ -1,8 +1,8 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
-| `SKILL.md` | 2025-11-12T10:41:15.855Z |
+| `SKILL.md` | 2025-11-17T13:25:01.244Z |
 | `templates/实施计划文档.md` | 2025-11-17T09:33:20.784Z |

package/skills/aipk_development/SKILL.md

@@ -1,10 +1,24 @@
 ---
 name: development
-description: Development phase index pointing to the single authoritative implementation plan template.
+description: Index for the single authoritative implementation plan template covering development execution, so use it when planning dev deliverables and not for unrelated coding or testing notes.
 ---
 
 # 开发阶段模板索引
 
+## 技能范围
+
+**作用**：作为开发阶段唯一规范化资产的索引，明确使用 `实施计划文档` 模板来统一需求对齐、设计联动、开发排期与验收交接等内容。
+
+**适用场景**：
+- 准备或更新开发执行计划、实施步骤或验收要求时需要统一格式。
+- 团队需要一个稳定、可复用的文档入口来梳理开发阶段的输出。
+- 需要在变更或复盘中引用开发阶段通用模板时。
+
+**不适用场景**：
+- 直接撰写代码、实现细节或测试检查列表的任务（请在具体实施文档或工程目录中完成）。
+- 需要编写与开发计划无关的战略、设计或产品文档。
+- 需要为多个项目分别维护不同结构的开发流程（此处强调单一模板一致性）。
+
 开发阶段目前仅保留一个标准化资产——`实施计划文档` 模板。所有与开发过程相关的说明、Checklist、交付要求都应在该模板中进行维护和引用。
 
 ## 可用模板

package/skills/aipk_format-requirement-pages-with-design/GURU_AI.md

@@ -1,8 +1,8 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
 | `requirement-page-table-format.md` | 2025-11-17T06:21:56.025Z |
-| `SKILL.md` | 2025-11-17T09:13:58.040Z |
+| `SKILL.md` | 2025-11-17T13:24:58.161Z |

package/skills/aipk_format-requirement-pages-with-design/SKILL.md

@@ -1,12 +1,21 @@
 ---
 name: aipk_format-requirement-pages-with-design
-description: Format requirement document pages with design images into standardized tables. Use when requirement documents contain design images and need to be organized into a two-column table format (page description | design image) following the project's table formatting standards.
+description: Format requirement document pages that include design images into standardized two-column tables so page descriptions and visuals align with project standards; use when visuals exist, not when no design images or unrelated doc tasks are needed.
 ---
 
 # 需求页面表格格式化 Skill
 
+## 技能范围
+
+**作用**：把需求文档中的页面说明和设计图按项目规范整理成双列表格，提高页面可读性与格式一致性，确保所有视觉稿都对应明确的说明。
+
 **适用场景**：当需求文档中包含设计图时，将页面说明和设计图按照标准表格格式组织。当你看到任务中提到"将设计图放入表格"、"格式化需求页面"、"整理页面说明和设计图"或类似描述时，立即使用本 Skill。
 
+**不适用场景**：
+- 文档中无设计图、只是需要纯文本调整的情况。
+- 需要对设计稿本身进行创作或修改，不涉及表格排版。
+- 需要处理需求变动说明、开发或测试内容的工作。
+
 ## 1. 技能定位
 
 - **适用场景**：需求文档中包含设计图，需要将页面说明和设计图组织成标准表格格式

package/skills/aipk_init_project/GURU_AI.md

@@ -1,10 +1,10 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
 | `scripts/check_agents.sh` | 2025-11-13T09:03:47.702Z |
 | `skill.ini` | 2025-11-13T09:47:02.793Z |
-| `SKILL.md` | 2025-11-13T10:06:33.764Z |
-| `template/AGENTS_TEMPLATE.md` | 2025-11-17T11:14:53.842Z |
+| `SKILL.md` | 2025-11-17T13:24:45.708Z |
+| `template/AGENTS_TEMPLATE.md` | 2025-11-17T13:32:10.540Z |

package/skills/aipk_init_project/SKILL.md

@@ -1,10 +1,24 @@
 ---
 name: init-project
-description: Initialize the project Agents playbook, sync the skills inventory into AGENTS.md/templates, and verify the workspace includes a complete AGENTS.md file.
+description: Ensure AGENTS.md and skills inventories match the template during onboarding or audits; use for Agents initwork and skip it for ordinary business content or document creation.
 ---
 
 # 项目初始化 Skill
 
+## 技能范围
+
+**作用**：确保项目包含完整的 Agents 配置（AGENTS.md、skills 系统区块等），并提供初始化或校验流程，保障新项目在 AI Product Kit 规范下具备可识别的 Agents 指南。
+
+**适用场景**：
+- 新项目启动时需要构建或同步 `AGENTS.md` 与 `<skills_system>` 区块。
+- 需要校验现有仓库是否具备完整的 Agents 文件及模板一致性。
+- 维护团队准备对 AGENTS 模板或技能清单进行版本更新。
+
+**不适用场景**：
+- 日常的文档写作、需求、设计、开发内容本身（这些应由各自技能处理）。
+- 纯业务内容更新，不涉及 Agents 工作规范。
+- 需要大量定制内容的 AGENTS.md（除 Project Overview 外均需与模板一致）。
+
 ## 1. 技能定位
 
 - **适用场景**：初始化新项目、检查现有项目的 Agents 配置、更新项目的 Agents 文档

package/skills/aipk_initiative-planning/GURU_AI.md

@@ -1,10 +1,10 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
-| `SKILL.md` | 2025-11-17T09:14:19.526Z |
+| `SKILL.md` | 2025-11-17T13:24:29.546Z |
 | `template/SWOT分析模板.md` | 2025-11-12T10:41:15.864Z |
 | `template/产品规划模板.md` | 2025-11-12T10:41:15.864Z |
 | `template/商业化规划模板.md` | 2025-11-12T10:41:15.864Z |

package/skills/aipk_initiative-planning/SKILL.md

@@ -1,10 +1,26 @@
 ---
 name: aipk_initiative-planning
-description: Comprehensive workflow for evaluating, scoping, and approving new product initiatives.
+description: Structure initiative evaluation and scoping to align strategy, feasibility, and risk before formal requirements; use for new product or major feature planning and steer clear of design sync, doc tweaks, or execution-phase work.
 ---
 
 # 立项规划
 
+## 技能范围
+
+**作用**：以结构化的立项规划流程连接需求收集与正式需求文档，帮助团队在投入资源前评估战略对齐、可行性与风险，并为决策提供清晰依据。
+
+**适用场景**：
+- 需要将初步研究或创意推进到正式需求文档的项目初期立项
+- 重大功能模块或新业务线的可行性评估与资源规划
+- 需要整合市场、产品、技术、商业等维度的立项建议供领导决策
+- 需要准备项目投资分析、商业模式验证或技术选型输出
+
+**不适用场景**：
+- 已经处在需求撰写/开发阶段，只需补充细节的执行任务
+- 仅需对现有设计稿进行同步修改的文档更新（请使用 design 相关 skill）
+- 小规模日常变更说明或低影响 bug 修复
+- 与开发、测试或上线执行具体落地（如代码、脚本）有关的任务
+
 > 🎯 **产品立项规划完整指南** - 从需求收集到需求文档撰写的关键桥梁，确保产品方向正确、资源合理分配
 
 ## 📋 文档信息

package/skills/aipk_requirements-changes/GURU_AI.md

@@ -1,10 +1,10 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
-| `SKILL.md` | 2025-11-17T09:14:02.152Z |
+| `SKILL.md` | 2025-11-17T13:25:08.595Z |
 | `template/index.md` | 2025-11-12T10:41:15.858Z |
 | `template/需求变动说明文档模板.md` | 2025-11-12T10:41:15.859Z |
 | `template/需求变动说明生成Prompt.md` | 2025-11-12T10:41:15.859Z |

package/skills/aipk_requirements-changes/SKILL.md

@@ -1,10 +1,24 @@
 ---
 name: aipk_requirements-changes
-description: Templates, prompts, and procedures for documenting and reviewing requirement changes.
+description: Templates, prompts, and procedures for documenting requirement changes, including structured overviews and diff analysis; use for any change to requirement docs and avoid new requirement drafting or unrelated engineering work.
 ---
 
 # 需求变动说明生成工具包
 
+## 技能范围
+
+**作用**：统一记录需求文档变更的模板、Prompt 与流程，确保每次变动都有完整的变动说明、差异核查与复盘材料。
+
+**适用场景**：
+- 需要为任何需求文档变更（重大迭代、小改动、合规更新）生成结构化的变动说明。
+- 需要按照统一模板输出变动概述、Commit 历史与产品/功能/策略分析内容。
+- 希望用 Prompt 或自动化脚本辅助整理变动内容、生成说明或检查清单。
+
+**不适用场景**：
+- 编写新的需求文档或设计内容（而不是描述变更本身）的任务。
+- 单纯做开发、测试、发布相关工作，而非记录需求差异。
+- 只需提交简单变更说明而无需模板规范（不过建议仍使用模板保持一致）。
+
 ## 执行指南
 
 **重要提示**: 本指南专为自动化文档生成设计，请严格按照以下规则执行：

package/skills/aipk_requirements-documentation/GURU_AI.md

@@ -1,10 +1,10 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
-| `SKILL.md` | 2025-11-17T09:39:31.163Z |
+| `SKILL.md` | 2025-11-17T13:24:35.423Z |
 | `template/1_产品定位与分析.md` | 2025-11-17T06:49:33.762Z |
 | `template/2_功能需求.md` | 2025-11-17T06:49:38.006Z |
 | `template/3_商业化策略.md` | 2025-11-17T06:43:53.421Z |

package/skills/aipk_requirements-documentation/SKILL.md

@@ -1,10 +1,26 @@
 ---
 name: aipk_requirements-documentation
-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 `skills/update-requirements-from-design` skill instead.
+description: Guide for drafting new requirement docs or iterating existing ones textually; apply when starting from scratch or doing template-compliant text updates without design assets, and avoid design-driven updates or implementation/test tasks.
 ---
 
 # 需求文档与迭代模板指南
 
+## 技能范围
+
+**作用**：负责从零创建需求文档或对现有文档进行纯文本迭代，同时引导 AI 与人类协作者在不依赖视觉设计资产的前提下保持结构和格式一致。
+
+**适用场景**：
+- 全新产品或功能的需求文档撰写（从 0 到 1）
+- 基于现有需求文档进行内容优化、补充说明或结构调整
+- 纯文本的需求评审、需求变更记录更新（不涉及设计稿）
+- 需要严格套用项目模板输出高一致性文档
+
+**不适用场景**：
+- 任务明确提到“设计图”、“视觉稿”、“mockup”或需要同步设计变化的情况（请转到 `skills/update-requirements-from-design`）
+- 仅需处理演示、说明或示意性内容而非正式需求文档
+- 与代码实现、测试用例、发布流程相关的工程任务
+- 需要图像处理、设计稿拆分与命名的工作
+
 **重要区分**：本 Skill 用于**从零开始创建**需求文档或对现有文档进行**纯文本层面的迭代**。如果任务涉及"基于设计图更新需求"、"根据视觉稿修改需求文档"或任何从设计资产开始的流程，请使用 **`skills/update-requirements-from-design`** skill 而不是本 skill。
 
 ## 执行指南

package/skills/aipk_requirements-intake/GURU_AI.md

@@ -1,13 +1,13 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
 | `examples/K12数学学习应用案例.md` | 2025-11-12T10:41:15.866Z |
 | `examples/电商平台优化案例.md` | 2025-11-12T10:41:15.866Z |
 | `references/Gemini_DeepResearch_工具链整合架构设计.md` | 2025-11-12T10:41:15.867Z |
-| `SKILL.md` | 2025-11-17T09:14:10.148Z |
+| `SKILL.md` | 2025-11-17T13:25:04.821Z |
 | `template/产品需求发现与验证模板.md` | 2025-11-12T10:41:15.867Z |
 | `template/市场机会评估与竞争分析模板.md` | 2025-11-12T10:41:15.867Z |
 | `template/技术方案评估与可行性分析模板.md` | 2025-11-12T10:41:15.867Z |

package/skills/aipk_requirements-intake/SKILL.md

@@ -1,10 +1,24 @@
 ---
 name: aipk_requirements-intake
-description: Intelligent intake pipeline for gathering and consolidating product requirements from multiple sources.
+description: Structured intake pipeline combining Gemini DeepResearch with multi-platform data to discover product needs; use during early-stage opportunity validation and avoid it once requirements are defined or when design/dev tasks begin.
 ---
 
 # 需求收集
 
+## 技能范围
+
+**作用**：通过 Gemini DeepResearch 与多平台数据源的组合，提供结构化的需求发现流程，帮助团队快速整合问题、用户声音与市场洞察，输出高质量的需求方向和分析报告。
+
+**适用场景**：
+- 新功能或新产品立项前需要系统化需求收集和市场洞察。
+- 需要多平台、跨区域产品数据（如 SensorTower/七麦/点点）来验证机会或痛点。
+- 希望用 AI 整理多源数据并输出结构化分析、需求地图或技术评估。
+
+**不适用场景**：
+- 任务目标已明确、只需撰写具体的需求文档或交付物。
+- 没有外部数据或市场输入，仅需根据内部需求创建文档。
+- 需要进行设计稿同步、开发实施或测试验证的工作（其他 skill 负责）。
+
 > 🚀 **智能需求收集工具链** - 整合Gemini DeepResearch与多平台数据，实现高效、准确的产品需求收集
 
 ## 📋 文档信息

package/skills/aipk_skill_generate/GURU_AI.md

@@ -1,10 +1,10 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
 | `agent_skills_spec.md` | 2025-11-12T10:41:15.869Z |
 | `scripts/init_skill.js` | 2025-11-17T09:35:05.968Z |
 | `scripts/package_skill.js` | 2025-11-17T09:35:19.171Z |
-| `SKILL.md` | 2025-11-17T08:26:11.887Z |
+| `SKILL.md` | 2025-11-17T13:24:38.406Z |

package/skills/aipk_skill_generate/SKILL.md

@@ -1,11 +1,25 @@
 ---
 name: skill-creation
-description: Standards and practices for creating new Agent Skills that extend Claude with reusable workflows, documentation, and tooling assets.
+description: Playbook for creating or refreshing Skills so metadata, templates, and scripts meet Claude’s expectations; use when scaffolding Skills or syncing bundles, not for unrelated product content.
 license: Complete terms in LICENSE.txt
 ---
 
 # Skill Creation Playbook
 
+## Skill Scope
+
+**Purpose**: Serve as the authoritative playbook for packaging new Skills, refreshing existing ones, and ensuring every addition follows the repo's meta-guidelines so Claude can discover and load them reliably.
+
+**Applicable scenarios**:
+- You need to scaffold or update a Skill directory (SKILL.md, templates, scripts).
+- You are documenting how Claude should trigger, execute, or maintain a Skill.
+- You are preparing materials (AGENTS sync, bundle packaging) that must match the Skill creation conventions.
+
+**Not applicable when**:
+- You write general product requirements, release notes, or customer-facing docs unrelated to Skill packaging.
+- You are editing content inside a Skill for its domain-specific guidance without touching the meta-structure (use the respective Skill instead).
+- You are implementing code or tooling outside the Skills bundle (use tools/ or other directories).
+
 This skill captures the expectations, templates, and workflows used across AI Product Kit to author reusable Skills. Treat it as the canonical reference when you need to convert a document into a Skill, add a new workflow, or refresh existing guidance.
 
 ## 1. Why Skills Matter

package/skills/aipk_tool_prompts/GURU_AI.md

@@ -1,6 +1,6 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
@@ -8,6 +8,6 @@ Last refreshed: 2025-11-17T11:14:53.954Z
 | `images/20250710200701.png` | 2025-11-12T10:41:15.870Z |
 | `images/20250710200802.png` | 2025-11-12T10:41:15.870Z |
 | `Prompt生成.md` | 2025-11-12T10:41:15.869Z |
-| `SKILL.md` | 2025-11-17T09:52:16.315Z |
+| `SKILL.md` | 2025-11-17T13:24:48.472Z |
 | `标记文档更新.md` | 2025-11-12T10:41:15.870Z |
 | `生成DrawIO文档.md` | 2025-11-12T10:41:15.871Z |

package/skills/aipk_tool_prompts/SKILL.md

@@ -1,10 +1,24 @@
 ---
 name: tool_prompts
-description: Directory of curated tool prompts, their core strengths, calling scenarios, input/output expectations, and the Markdown files that describe how to run them.
+description: Catalog of curated tool prompts with strengths, scenarios, and I/O rules for reuse; refer to it when consuming or extending prompts, not when writing unrelated product docs or new Skills.
 ---
 
 # 工具 Prompt 目录
 
+## 技能范围
+
+**作用**：一站式列出所有可复用的工具 Prompt、调用场景与输入输出规范，方便团队快速定位并复用已有 Prompt。
+
+**适用场景**：
+- 需要使用、扩展或记录标准 Prompt（例如文档同步、DrawIO 输出、AI 体验设计）。
+- 在文档或自动化流程中引用 Prompt，想快速找到对应的 Markdown 指南。
+- 审查 Prompt 目录是否齐全或准备新增 Prompt 资源链接。
+
+**不适用场景**：
+- 需要编写与 Prompt 管理无关的产品/设计文档内容。
+- 需要创建新的 Skill（应转到 `skills/aipk_skill_generate`）。
+- Prompt 直接交付用户而不作为文档或标准化资产引用的情况。
+
 ## 1. 技能定位
 - **适用场景**：需要复用或扩展现有 Prompt、为团队成员指路、或在文档/自动化流程中引用标准 Prompt 时
 - **目标人群**：文档维护者、产品/设计同学、自动化脚本作者

package/skills/aipk_update-requirements-from-design/GURU_AI.md

@@ -1,6 +1,6 @@
 # GURU AI Snapshot
 
-Last refreshed: 2025-11-17T11:14:53.954Z
+Last refreshed: 2025-11-17T13:32:10.622Z
 
 | File | Last Modified (UTC) |
 | --- | --- |
@@ -118,4 +118,4 @@ Last refreshed: 2025-11-17T11:14:53.954Z
 | `scripts/sharp-runtime/package.json` | 2025-11-13T12:53:10.715Z |
 | `scripts/split-design-boards.js` | 2025-11-13T13:11:29.610Z |
 | `scripts/sync-design-to-requirements.js` | 2025-11-13T13:11:32.947Z |
-| `SKILL.md` | 2025-11-17T09:14:24.660Z |
+| `SKILL.md` | 2025-11-17T13:24:54.452Z |

package/skills/aipk_update-requirements-from-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: aipk_update-requirements-from-design
-description: Update requirement documents based on design mockups (composite boards or individual UI frames). Use this when you need to split composite boards or directly align single/multiple standalone UI images with requirement docs, including syncing visuals, verifying differences, and generating change records.
+description: Sync requirement docs with design mockups (composite or standalone UI frames) via split/mapping scripts, capturing visual alignment and change records; use this when design assets drive the update and avoid pure text-only work.
 ---
 
 # Update Requirements from Design Skill
@@ -9,6 +9,20 @@ description: Update requirement documents based on design mockups (composite boa
 
 处理流程：如果是合成图，先通过 [`./scripts/split-design-boards.js`](./scripts/split-design-boards.js) 拆分每个面板，再用 [`./scripts/sync-design-to-requirements.js`](./scripts/sync-design-to-requirements.js) 管理映射与入库；如果是单张或多张独立 UI 图，则在确认落库命名后直接调整需求文档，重点对齐图片与文案一致性，并在变动说明中汇总差异。
 
+## 技能范围
+
+**作用**：提供从设计稿到需求文档的连贯流程（含拆分、映射、入库、图文对齐与变更记录），确保视觉与文本同步并留下清晰的差异说明。
+
+**适用场景**：
+- 需要拆分合成设计图并批量处理或命名面板时。
+- 必须将单张/多张 UI 图精确对齐到指定需求章节并更新文案或控件说明。
+- 期望同时生成设计差异核对表、变动说明与版本记录，便于审计。
+
+**不适用场景**：
+- 纯文本需求更新或撰写工作（此类任务请使用其他需求技能）。
+- 没有视觉材料、仅依靠描述输出文档的需求说明。
+- 仅在设计工具内制作界面稿而不触及需求文档的流程。
+
 > **注意**：脚本直接运行在 Node 环境，依赖集中安装在 [`./scripts/sharp-runtime/`](./scripts/sharp-runtime/) 中。首次使用或更新版本时，在该目录执行 `npm install`，即可获取 `sharp` 等运行时依赖，无需额外打包。
 
 <!-- rule: Agents must complete the entire pipeline end-to-end without依赖人工手动操作或 GUI 工具。 -->