@bovinphang/frontend-craft 2.8.0 → 3.0.0

package/localized/zh-CN/skills/relations.json

@@ -1,7 +1,201 @@
 {
+  "cc-c-project-standard": {
+    "relatedSkills": [
+      "cc-native-memory-safety",
+      "cc-cpp-project-standard"
+    ],
+    "capabilityTags": [
+      "c",
+      "project",
+      "standard"
+    ]
+  },
+  "cc-cpp-project-standard": {
+    "relatedSkills": [
+      "cc-native-memory-safety",
+      "cc-c-project-standard"
+    ],
+    "capabilityTags": [
+      "cpp",
+      "project",
+      "standard"
+    ]
+  },
+  "cc-debug-methodology": {
+    "capabilityTags": [
+      "debug",
+      "evidence",
+      "root-cause"
+    ]
+  },
+  "cc-doc-sync-core": {
+    "capabilityTags": [
+      "documentation",
+      "source-of-truth",
+      "i18n"
+    ]
+  },
+  "cc-drawio-studio": {
+    "capabilityTags": [
+      "drawio",
+      "uml",
+      "erd",
+      "architecture"
+    ]
+  },
+  "cc-electron-project-standard": {
+    "relatedSkills": [
+      "cc-typescript-project-standard"
+    ],
+    "capabilityTags": [
+      "electron",
+      "desktop",
+      "ipc"
+    ]
+  },
+  "cc-go-concurrency": {
+    "relatedSkills": [
+      "cc-go-project-standard"
+    ],
+    "capabilityTags": [
+      "go",
+      "concurrency"
+    ]
+  },
+  "cc-go-project-standard": {
+    "relatedSkills": [
+      "cc-go-concurrency"
+    ],
+    "capabilityTags": [
+      "go",
+      "project",
+      "standard"
+    ]
+  },
+  "cc-java-project-standard": {
+    "relatedSkills": [
+      "cc-java-runtime"
+    ],
+    "capabilityTags": [
+      "java",
+      "project",
+      "standard"
+    ]
+  },
+  "cc-java-runtime": {
+    "relatedSkills": [
+      "cc-java-project-standard"
+    ],
+    "capabilityTags": [
+      "java",
+      "runtime"
+    ]
+  },
+  "cc-native-memory-safety": {
+    "relatedSkills": [
+      "cc-c-project-standard",
+      "cc-cpp-project-standard"
+    ],
+    "capabilityTags": [
+      "native",
+      "memory",
+      "safety"
+    ]
+  },
+  "cc-python-async": {
+    "relatedSkills": [
+      "cc-python-project-standard"
+    ],
+    "capabilityTags": [
+      "python",
+      "async"
+    ]
+  },
+  "cc-python-project-standard": {
+    "relatedSkills": [
+      "cc-python-async"
+    ],
+    "capabilityTags": [
+      "python",
+      "project",
+      "standard"
+    ]
+  },
+  "cc-refactoring-core": {
+    "capabilityTags": [
+      "refactoring",
+      "behavior-preservation",
+      "baseline"
+    ]
+  },
+  "cc-rust-async": {
+    "relatedSkills": [
+      "cc-rust-project-standard"
+    ],
+    "capabilityTags": [
+      "rust",
+      "async"
+    ]
+  },
+  "cc-rust-project-standard": {
+    "relatedSkills": [
+      "cc-rust-async"
+    ],
+    "capabilityTags": [
+      "rust",
+      "project",
+      "standard"
+    ]
+  },
+  "cc-source-driven-development": {
+    "capabilityTags": [
+      "official-docs",
+      "versioning",
+      "local-knowledge"
+    ]
+  },
+  "cc-tauri-project-standard": {
+    "relatedSkills": [
+      "cc-rust-project-standard",
+      "cc-typescript-project-standard"
+    ],
+    "capabilityTags": [
+      "tauri",
+      "desktop",
+      "ipc"
+    ]
+  },
+  "cc-tdd-methodology": {
+    "capabilityTags": [
+      "tdd",
+      "regression",
+      "red-green-refactor"
+    ]
+  },
+  "cc-technical-diagrams": {
+    "capabilityTags": [
+      "architecture",
+      "sequence",
+      "workflow",
+      "png-qa"
+    ]
+  },
+  "cc-typescript-project-standard": {
+    "relatedSkills": [
+      "cc-source-driven-development",
+      "cc-tdd-methodology"
+    ],
+    "capabilityTags": [
+      "typescript",
+      "project-standard",
+      "type-safety",
+      "tsconfig",
+      "declarations"
+    ]
+  },
   "fec-alchemy": {
     "relatedSkills": [
-      "fec-source-driven-development",
+      "cc-source-driven-development",
       "fec-doc-sync",
       "fec-refactor-clean",
       "fec-code-review",
@@ -25,8 +219,8 @@
       "fec-security-review",
       "fec-route-protection",
       "fec-form-handling",
-      "fec-typescript-project-standard",
-      "fec-source-driven-development"
+      "cc-typescript-project-standard",
+      "cc-source-driven-development"
     ],
     "boundaryWorkflows": [
       "涉及 TanStack Query 缓存策略、query key、乐观更新和服务端状态 hooks 时，使用数据获取工作流。",
@@ -45,7 +239,7 @@
     "relatedSkills": [
       "fec-api-integration",
       "fec-doc-sync",
-      "fec-source-driven-development",
+      "cc-source-driven-development",
       "fec-testing-strategy",
       "fec-route-protection"
     ],
@@ -105,9 +299,9 @@
       "fec-e2e-testing",
       "fec-validation-fix",
       "fec-performance-optimization",
-      "fec-typescript-project-standard",
+      "cc-typescript-project-standard",
       "fec-state-management",
-      "fec-source-driven-development",
+      "cc-source-driven-development",
       "fec-dependency-upgrade",
       "fec-responsive-layout"
     ],
@@ -122,6 +316,27 @@
       "frontend"
     ]
   },
+  "fec-code-smells": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-refactoring-catalog",
+      "fec-code-review"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "code-smells",
+      "diagnosis",
+      "maintainability",
+      "evidence"
+    ]
+  },
   "fec-component-testing": {
     "relatedSkills": [
       "fec-testing-strategy",
@@ -176,7 +391,7 @@
   },
   "fec-dependency-upgrade": {
     "relatedSkills": [
-      "fec-source-driven-development",
+      "cc-source-driven-development",
       "fec-validation-fix",
       "fec-refactor-clean",
       "fec-security-review",
@@ -194,27 +409,6 @@
       "migration"
     ]
   },
-  "fec-drawio-studio": {
-    "relatedSkills": [
-      "fec-image-generation",
-      "fec-canvas-threejs",
-      "fec-svg-animation",
-      "fec-ui-design",
-      "fec-source-driven-development"
-    ],
-    "boundaryWorkflows": [
-      "涉及位图优先的海报、视觉概念、产品图，以及超出可编辑技术图的 PNG QA 时，使用图像生成工作流。",
-      "当图表变成运行时交互可视化、仿真、游戏场景、shader 或 3D 渲染器时，使用Canvas/Three.js。",
-      "动效专项的矢量微交互使用 SVG 动画；静态或可编辑技术 SVG 导出使用 draw.io 图表工作室。"
-    ],
-    "capabilityTags": [
-      "drawio",
-      "editable-diagram",
-      "autolayout",
-      "shape-search",
-      "code-structure-map"
-    ]
-  },
   "fec-e2e-testing": {
     "relatedSkills": [
       "fec-testing-strategy",
@@ -263,13 +457,16 @@
     ],
     "boundaryWorkflows": [
       "涉及产品专属视觉方向、品牌调性、层级和生成资产视觉 QA 时，使用 UI 设计工作流。",
-      "当Figma、Sketch、MasterGo、Pixso、截图或其他外部设计源是权威来源时，使用按设计实现。",
-      "当生成视觉资产变成交互式渲染器、shader 或动效资产，而不是静态图片时，使用Canvas/Three.js or SVG 动画 workflows。"
+      "当 Figma、Sketch、MasterGo、Pixso、截图或其他外部设计源是权威来源时，使用按设计实现工作流。",
+      "需要可在浏览器中直接使用、带主题的工作流图、序列图、数据流图、生命周期图、操作手册图、个人信息（PII）或数据血缘图，以及状态机图时，使用 HTML 技术图路线。",
+      "当优先需要可编辑的 .drawio 源文件、官方图形检索或在 diagrams.net 中手动编辑时，使用 draw.io 图表工作室。",
+      "当生成视觉资产变成交互式渲染器、shader 或动效资产，而不是静态图片时，使用 Canvas/Three.js 或 SVG 动画工作流。"
     ],
     "capabilityTags": [
       "image-generation",
       "image-editing",
       "diagram-generation",
+      "html-diagram",
       "png-qa",
       "visual-assets",
       "autofix"
@@ -421,7 +618,7 @@
   },
   "fec-react-project-standard": {
     "relatedSkills": [
-      "fec-typescript-project-standard",
+      "cc-typescript-project-standard",
       "fec-state-management",
       "fec-tailwind-design-system",
       "fec-responsive-layout",
@@ -447,6 +644,249 @@
       "fec-architecture"
     ]
   },
+  "fec-refactoring": {
+    "relatedSkills": [
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "fec-refactor-clean",
+      "fec-code-review",
+      "fec-tdd-workflow",
+      "fec-debug-framework",
+      "fec-validation-fix",
+      "fec-testing-strategy"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "behavior-preservation",
+      "workflow",
+      "validation"
+    ]
+  },
+  "fec-refactoring-api": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "fec-api-integration",
+      "cc-typescript-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "api",
+      "parameters",
+      "dependencies"
+    ]
+  },
+  "fec-refactoring-catalog": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-functions",
+      "fec-refactoring-encapsulation",
+      "fec-refactoring-move-features",
+      "fec-refactoring-data",
+      "fec-refactoring-control",
+      "fec-refactoring-api",
+      "fec-refactoring-inheritance",
+      "fec-refactoring-validation"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "catalog",
+      "selection",
+      "composition"
+    ]
+  },
+  "fec-refactoring-control": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "cc-typescript-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "conditionals",
+      "guard-clauses",
+      "polymorphism"
+    ]
+  },
+  "fec-refactoring-data": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "fec-state-management",
+      "cc-typescript-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "data",
+      "derived-state",
+      "identity"
+    ]
+  },
+  "fec-refactoring-encapsulation": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "fec-state-management"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "encapsulation",
+      "delegation",
+      "value-object"
+    ]
+  },
+  "fec-refactoring-functions": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "cc-typescript-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "functions",
+      "parameters",
+      "decomposition"
+    ]
+  },
+  "fec-refactoring-inheritance": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "cc-typescript-project-standard",
+      "fec-legacy-to-modern-migration"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "inheritance",
+      "delegation",
+      "composition"
+    ]
+  },
+  "fec-refactoring-move-features": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "fec-refactor-clean"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "move-function",
+      "ownership",
+      "loops"
+    ]
+  },
+  "fec-refactoring-validation": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-testing-strategy",
+      "fec-tdd-workflow",
+      "fec-validation-fix",
+      "fec-debug-framework",
+      "fec-code-review"
+    ],
+    "boundaryWorkflows": [
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "validation",
+      "behavior-preservation",
+      "rollback"
+    ]
+  },
   "fec-responsive-layout": {
     "relatedSkills": [
       "fec-ui-design",
@@ -485,26 +925,6 @@
       "frontend"
     ]
   },
-  "fec-source-driven-development": {
-    "relatedSkills": [
-      "fec-doc-sync",
-      "fec-dependency-upgrade",
-      "fec-api-integration",
-      "fec-vite-project-standard",
-      "fec-nextjs-project-standard",
-      "fec-nuxt-project-standard"
-    ],
-    "boundaryWorkflows": [
-      "当source-verified decisions change public docs, runtime docs, or metadata时，使用文档同步。",
-      "当source checking leads to frontend-backend contract or error-shape changes时，使用 API 集成。",
-      "当the source-verified behavior is specific to Vite, Next.js, Nuxt, React, or Vue时，使用framework project workflows。"
-    ],
-    "capabilityTags": [
-      "source-driven",
-      "official-docs",
-      "version-sensitive"
-    ]
-  },
   "fec-state-management": {
     "relatedSkills": [
       "fec-data-fetching",
@@ -615,29 +1035,6 @@
       "quality-gate"
     ]
   },
-  "fec-typescript-project-standard": {
-    "relatedSkills": [
-      "fec-code-review",
-      "fec-api-integration",
-      "fec-react-project-standard",
-      "fec-vue3-project-standard",
-      "fec-vite-project-standard",
-      "fec-monorepo-project-standard",
-      "fec-validation-fix"
-    ],
-    "boundaryWorkflows": [
-      "涉及组件架构、路由、状态归属和框架专项模块边界时，使用框架项目工作流。",
-      "当runtime API clients, auth refresh, uploads, realtime behavior, or error mapping go beyond TypeScript type contracts时，使用 API 集成。",
-      "当the task is to repair concrete lint, typecheck, test, build, or CI failures after TypeScript changes时，使用验证修复 fix。"
-    ],
-    "capabilityTags": [
-      "typescript",
-      "project-standard",
-      "type-safety",
-      "tsconfig",
-      "declarations"
-    ]
-  },
   "fec-ui-design": {
     "relatedSkills": [
       "fec-image-generation",
@@ -690,7 +1087,7 @@
   },
   "fec-vue3-project-standard": {
     "relatedSkills": [
-      "fec-typescript-project-standard",
+      "cc-typescript-project-standard",
       "fec-state-management",
       "fec-tailwind-design-system",
       "fec-responsive-layout",

package/localized/zh-CN/templates/shared/rules/fec-agent-workflow.md

@@ -41,6 +41,7 @@
 ## 协作约束
 
 - 委托前先明确范围、输入和输出，不把模糊任务丢给子代理。
+- 修改后自动委托审核时，显式传入本次改动范围（文件及差异 / PR / 提交上下文）。未限定的审核默认全项目；仅指定文件或目录表示全量审核该范围，不等于增量审核。
 - 多个独立问题可以并行分析；彼此有依赖的任务按顺序推进。
 - 子代理输出必须落到可验证结论：报告、文件路径、命令结果或具体风险。
 - 子代理建议不自动等于实现决策；与仓库现有约定冲突时，优先遵循仓库约定。

package/localized/zh-CN/templates/shared/rules/fec-source-driven-development.md

@@ -1,31 +1,5 @@
-# 来源驱动开发规则
+# 前端事实来源检查
 
-当实现依赖框架、库、浏览器、运行时、构建工具或平台行为时，先确认事实来源，再写代码或评审结论。
+当决策涉及前端版本行为时，检查项目实际框架/库版本、路由与渲染模式、缓存、构建配置、浏览器 API 和兼容性。
 
-## 事实来源优先级
-
-1. 项目内 README、配置、测试、模板和已有实现。
-2. 官方文档、源码、类型定义、release notes、migration guide。
-3. Web 标准、浏览器兼容数据和平台文档。
-4. Issue、讨论、博客和第三方文章仅作为线索。
-
-## 使用场景
-
-- 框架新版本、路由、渲染模式、缓存、构建配置、浏览器 API。
-- 公共接口、组件 API、设计系统 token、CLI 命令和插件元数据。
-- 依赖升级、迁移、废弃 API 替换、跨运行时兼容。
-- 与安全、性能、可访问性相关的版本敏感判断。
-
-## 输出要求
-
-- 写清来源、版本或项目事实、决策结论、影响范围和验证方式。
-- 若项目现状与官方推荐冲突，说明冲突原因和渐进迁移策略。
-- 不复制长篇外部文档；只保留必要结论、链接或项目内文件路径。
-- 无法验证时标注不确定性和需要用户/团队确认的事项。
-
-## 反模式
-
-- 凭记忆使用版本敏感 API。
-- 用过时教程替代官方文档。
-- 为追新推翻稳定项目约定。
-- 在组件里散落外部库行为假设，而不是集中到适配层。
+公共 source-driven 方法随产品提供；前端场景额外关注组件 API、设计 Token、浏览器安全、性能、无障碍、包导出和 Runtime 适配。以当前项目实现和官方版本资料作证据，记录版本、影响和实际验证，不把过时教程当成稳定契约。