@bovinphang/frontend-craft 2.9.0 → 3.0.0

package/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": [
       "Use a data-fetching workflow for TanStack Query cache policy, query keys, optimistic updates, and server-state 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": [
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
+    ],
+    "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": [
-      "Use image generation for raster-first posters, visual concepts, product images, and PNG QA beyond editable technical diagrams.",
-      "Use image generation's HTML technical diagram route when the priority is a browser-ready themed single-file workflow, sequence, data-flow, or lifecycle diagram.",
-      "Use Canvas/Three.js when the diagram becomes an interactive runtime visualization, simulation, game scene, shader, or 3D renderer.",
-      "Use SVG animation for motion-specific vector micro-interactions; use drawio studio for static or editable technical SVG exports."
-    ],
-    "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": [
-      "Use UI design when the task is visual direction, product identity, hierarchy, or polish beyond layout behavior.",
-      "Use accessibility check for keyboard, focus, semantics, screen reader behavior, and contrast concerns.",
-      "Use performance optimization when responsive behavior exposes rendering, image, bundle, or main-thread bottlenecks."
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
     ],
     "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": [
-      "Use a general code review workflow for architecture, maintainability, and broad quality review.",
-      "Use an accessibility workflow for accessibility-only concerns.",
-      "Use a browser storage workflow for storage strategy; keep sensitive data leakage risks in the security workflow."
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
     ],
     "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": [
-      "Use documentation sync when source-verified decisions change public docs, runtime docs, or metadata.",
-      "Use API integration when source checking leads to frontend-backend contract or error-shape changes.",
-      "Use framework project workflows when the source-verified behavior is specific to Vite, Next.js, Nuxt, React, or Vue."
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
     ],
     "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": [
-      "Use a data-fetching workflow for query keys, cache lifetime, invalidation, optimistic updates, and server-state hooks.",
-      "Use a form workflow for field registration, validation, submit flows, and form-specific dirty/error state.",
-      "Use a browser storage workflow when state must persist across reloads, sessions, offline mode, or cookie boundaries."
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
     ],
     "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": [
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
+    ],
+    "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": [
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
+    ],
+    "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": [
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
+    ],
+    "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": [
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
+    ],
+    "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": [
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
+    ],
+    "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": [
+      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
+      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
+      "Use debugging first when the failure cause is unknown.",
+      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
+      "Use code review for merge-readiness review rather than structure-changing execution.",
+      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
+    ],
+    "capabilityTags": [
+      "refactoring",
+      "validation",
+      "behavior-preservation",
+      "rollback"
+    ]
+  },
+  "fec-responsive-layout": {
+    "relatedSkills": [
+      "fec-ui-design",
+      "fec-accessibility-check",
+      "fec-performance-optimization",
+      "fec-tailwind-design-system"
+    ],
+    "boundaryWorkflows": [
+      "Use UI design when the task is visual direction, product identity, hierarchy, or polish beyond layout behavior.",
+      "Use accessibility check for keyboard, focus, semantics, screen reader behavior, and contrast concerns.",
+      "Use performance optimization when responsive behavior exposes rendering, image, bundle, or main-thread bottlenecks."
+    ],
+    "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": [
+      "Use a general code review workflow for architecture, maintainability, and broad quality review.",
+      "Use an accessibility workflow for accessibility-only concerns.",
+      "Use a browser storage workflow for storage strategy; keep sensitive data leakage risks in the security workflow."
+    ],
+    "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": [
+      "Use a data-fetching workflow for query keys, cache lifetime, invalidation, optimistic updates, and server-state hooks.",
+      "Use a form workflow for field registration, validation, submit flows, and form-specific dirty/error state.",
+      "Use a browser storage workflow when state must persist across reloads, sessions, offline mode, or cookie boundaries."
+    ],
+    "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": [
-      "Use framework project workflows for component architecture, routing, state ownership, and framework-specific module boundaries.",
-      "Use API integration when runtime API clients, auth refresh, uploads, realtime behavior, or error mapping go beyond TypeScript type contracts.",
-      "Use validation fix when the task is to repair concrete lint, typecheck, test, build, or CI failures after TypeScript changes."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "behavior-preservation",
-      "workflow",
-      "validation"
-    ]
-  },
-  "fec-code-smells": {
-    "relatedSkills": [
-      "fec-refactoring",
-      "fec-refactoring-catalog",
-      "fec-code-review"
-    ],
-    "boundaryWorkflows": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "functions",
-      "parameters",
-      "decomposition"
-    ]
-  },
-  "fec-refactoring-encapsulation": {
-    "relatedSkills": [
-      "fec-refactoring",
-      "fec-code-smells",
-      "fec-refactoring-catalog",
-      "fec-refactoring-validation",
-      "fec-state-management"
-    ],
-    "boundaryWorkflows": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "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": [
-      "Use dead-code cleanup for proven unused code, exports, styles, routes, fixtures, or dependencies.",
-      "Use TDD when adding new observable behavior or fixing a behavior-changing defect.",
-      "Use debugging first when the failure cause is unknown.",
-      "Use validation repair for understood lint, typecheck, test, or build failures that predate the refactoring step.",
-      "Use code review for merge-readiness review rather than structure-changing execution.",
-      "Use migration or architecture planning for dependency, framework, router, state-library, or platform replacements."
-    ],
-    "capabilityTags": [
-      "refactoring",
-      "validation",
-      "behavior-preservation",
-      "rollback"
-    ]
   }
 }