@bovinphang/frontend-craft 2.9.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,28 +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 时，使用图像生成工作流。",
-      "当优先需要可在浏览器中直接使用、带主题的单文件工作流图、序列图、数据流图或生命周期图时，使用图像生成的 HTML 技术图路线。",
-      "当图表变成运行时交互可视化、仿真、游戏场景、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",
@@ -425,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",
@@ -451,89 +644,312 @@
       "fec-architecture"
     ]
   },
-  "fec-responsive-layout": {
+  "fec-refactoring": {
     "relatedSkills": [
-      "fec-ui-design",
-      "fec-accessibility-check",
-      "fec-performance-optimization",
-      "fec-tailwind-design-system"
+      "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": [
-      "当the task is visual direction, product identity, hierarchy, or polish beyond layout behavior时，使用UI 设计。",
-      "涉及键盘、焦点、语义、屏幕阅读器行为和对比度问题时，使用无障碍检查。",
-      "当responsive behavior exposes rendering, image, bundle, or main-thread bottlenecks时，使用per表单处理ance optimization。"
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
     ],
     "capabilityTags": [
-      "responsive",
-      "layout",
-      "container-query",
-      "mobile-first"
+      "refactoring",
+      "behavior-preservation",
+      "workflow",
+      "validation"
     ]
   },
-  "fec-security-review": {
+  "fec-refactoring-api": {
     "relatedSkills": [
-      "fec-code-review",
-      "fec-accessibility-check",
-      "fec-browser-storage",
-      "fec-dependency-upgrade",
-      "fec-route-protection"
+      "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": [
-      "security",
-      "review",
-      "frontend"
+      "refactoring",
+      "api",
+      "parameters",
+      "dependencies"
     ]
   },
-  "fec-source-driven-development": {
+  "fec-refactoring-catalog": {
     "relatedSkills": [
-      "fec-doc-sync",
-      "fec-dependency-upgrade",
-      "fec-api-integration",
-      "fec-vite-project-standard",
-      "fec-nextjs-project-standard",
-      "fec-nuxt-project-standard"
+      "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": [
-      "当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。"
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
     ],
     "capabilityTags": [
-      "source-driven",
-      "official-docs",
-      "version-sensitive"
+      "refactoring",
+      "catalog",
+      "selection",
+      "composition"
     ]
   },
-  "fec-state-management": {
+  "fec-refactoring-control": {
     "relatedSkills": [
-      "fec-data-fetching",
-      "fec-form-handling",
-      "fec-browser-storage",
-      "fec-route-protection",
-      "fec-react-project-standard",
-      "fec-vue3-project-standard"
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "cc-typescript-project-standard"
     ],
     "boundaryWorkflows": [
-      "涉及 query key、缓存生命周期、失效、乐观更新和服务端状态 hooks 时，使用数据获取工作流。",
-      "涉及字段注册、校验、提交流程和表单特有 dirty/error 状态时，使用表单工作流。",
-      "当state must persist across reloads, sessions, offline mode, or cookie boundaries时，使用browser storage工作流。"
+      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
+      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
+      "故障原因未知时先使用调试流程。",
+      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
+      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
+      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
     ],
     "capabilityTags": [
-      "state-management",
-      "store-selection",
-      "url-state",
-      "state-ownership"
+      "refactoring",
+      "conditionals",
+      "guard-clauses",
+      "polymorphism"
     ]
   },
-  "fec-storybook-component-doc": {
+  "fec-refactoring-data": {
     "relatedSkills": [
-      "fec-testing-strategy",
-      "fec-component-testing",
+      "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",
+      "fec-accessibility-check",
+      "fec-performance-optimization",
+      "fec-tailwind-design-system"
+    ],
+    "boundaryWorkflows": [
+      "当the task is visual direction, product identity, hierarchy, or polish beyond layout behavior时，使用UI 设计。",
+      "涉及键盘、焦点、语义、屏幕阅读器行为和对比度问题时，使用无障碍检查。",
+      "当responsive behavior exposes rendering, image, bundle, or main-thread bottlenecks时，使用per表单处理ance optimization。"
+    ],
+    "capabilityTags": [
+      "responsive",
+      "layout",
+      "container-query",
+      "mobile-first"
+    ]
+  },
+  "fec-security-review": {
+    "relatedSkills": [
+      "fec-code-review",
+      "fec-accessibility-check",
+      "fec-browser-storage",
+      "fec-dependency-upgrade",
+      "fec-route-protection"
+    ],
+    "boundaryWorkflows": [
+      "涉及架构、可维护性和广义质量评审时，使用通用代码评审工作流。",
+      "仅涉及无障碍问题时，使用无障碍工作流。",
+      "存储策略使用浏览器存储工作流；敏感数据泄露风险保留在安全工作流中。"
+    ],
+    "capabilityTags": [
+      "security",
+      "review",
+      "frontend"
+    ]
+  },
+  "fec-state-management": {
+    "relatedSkills": [
+      "fec-data-fetching",
+      "fec-form-handling",
+      "fec-browser-storage",
+      "fec-route-protection",
+      "fec-react-project-standard",
+      "fec-vue3-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "涉及 query key、缓存生命周期、失效、乐观更新和服务端状态 hooks 时，使用数据获取工作流。",
+      "涉及字段注册、校验、提交流程和表单特有 dirty/error 状态时，使用表单工作流。",
+      "当state must persist across reloads, sessions, offline mode, or cookie boundaries时，使用browser storage工作流。"
+    ],
+    "capabilityTags": [
+      "state-management",
+      "store-selection",
+      "url-state",
+      "state-ownership"
+    ]
+  },
+  "fec-storybook-component-doc": {
+    "relatedSkills": [
+      "fec-testing-strategy",
+      "fec-component-testing",
       "fec-e2e-testing",
       "fec-accessibility-check",
       "fec-tailwind-design-system",
@@ -619,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",
@@ -694,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",
@@ -755,269 +1148,5 @@
       "performance",
       "main-thread"
     ]
-  },
-  "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-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-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-functions": {
-    "relatedSkills": [
-      "fec-refactoring",
-      "fec-code-smells",
-      "fec-refactoring-catalog",
-      "fec-refactoring-validation",
-      "fec-typescript-project-standard"
-    ],
-    "boundaryWorkflows": [
-      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
-      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
-      "故障原因未知时先使用调试流程。",
-      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
-      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
-      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "functions",
-      "parameters",
-      "decomposition"
-    ]
-  },
-  "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-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-data": {
-    "relatedSkills": [
-      "fec-refactoring",
-      "fec-code-smells",
-      "fec-refactoring-catalog",
-      "fec-refactoring-validation",
-      "fec-state-management",
-      "fec-typescript-project-standard"
-    ],
-    "boundaryWorkflows": [
-      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
-      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
-      "故障原因未知时先使用调试流程。",
-      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
-      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
-      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "data",
-      "derived-state",
-      "identity"
-    ]
-  },
-  "fec-refactoring-control": {
-    "relatedSkills": [
-      "fec-refactoring",
-      "fec-code-smells",
-      "fec-refactoring-catalog",
-      "fec-refactoring-validation",
-      "fec-typescript-project-standard"
-    ],
-    "boundaryWorkflows": [
-      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
-      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
-      "故障原因未知时先使用调试流程。",
-      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
-      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
-      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "conditionals",
-      "guard-clauses",
-      "polymorphism"
-    ]
-  },
-  "fec-refactoring-api": {
-    "relatedSkills": [
-      "fec-refactoring",
-      "fec-code-smells",
-      "fec-refactoring-catalog",
-      "fec-refactoring-validation",
-      "fec-api-integration",
-      "fec-typescript-project-standard"
-    ],
-    "boundaryWorkflows": [
-      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
-      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
-      "故障原因未知时先使用调试流程。",
-      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
-      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
-      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "api",
-      "parameters",
-      "dependencies"
-    ]
-  },
-  "fec-refactoring-inheritance": {
-    "relatedSkills": [
-      "fec-refactoring",
-      "fec-code-smells",
-      "fec-refactoring-catalog",
-      "fec-refactoring-validation",
-      "fec-typescript-project-standard",
-      "fec-legacy-to-modern-migration"
-    ],
-    "boundaryWorkflows": [
-      "已证明未使用的代码、导出、样式、路由、fixture 或依赖使用死代码清理能力。",
-      "新增可观察行为或修复会改变行为的缺陷时使用 TDD。",
-      "故障原因未知时先使用调试流程。",
-      "重构前已经存在且原因明确的 lint、typecheck、test 或 build 失败使用验证修复。",
-      "判断 PR 是否可合并时使用代码审查，而不是直接执行结构修改。",
-      "依赖、框架、路由器、状态库或平台替换属于迁移/架构规划，不作为普通保持行为重构处理。"
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "inheritance",
-      "delegation",
-      "composition"
-    ]
-  },
-  "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"
-    ]
   }
 }