@bovinphang/frontend-craft 2.7.0 → 2.9.0

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

@@ -0,0 +1,1023 @@
+{
+  "fec-alchemy": {
+    "relatedSkills": [
+      "fec-source-driven-development",
+      "fec-doc-sync",
+      "fec-refactor-clean",
+      "fec-code-review",
+      "fec-testing-strategy"
+    ],
+    "boundaryWorkflows": [
+      "当参考行为依赖官方文档、版本敏感 API 或项目事实时，使用事实源驱动开发。",
+      "当吸收后的能力会改变公开文档、runtime 文档、metadata 或已发布能力表时，使用文档同步。",
+      "当吸收工作需要先移除已确认的死代码、重复模块或未使用依赖时，使用重构清理。"
+    ],
+    "capabilityTags": [
+      "project-absorption",
+      "originality",
+      "reference-analysis",
+      "workflow"
+    ]
+  },
+  "fec-api-integration": {
+    "relatedSkills": [
+      "fec-data-fetching",
+      "fec-security-review",
+      "fec-route-protection",
+      "fec-form-handling",
+      "fec-typescript-project-standard",
+      "fec-source-driven-development"
+    ],
+    "boundaryWorkflows": [
+      "涉及 TanStack Query 缓存策略、query key、乐观更新和服务端状态 hooks 时，使用数据获取工作流。",
+      "涉及 token 存储、XSS、CSRF、文件上传信任边界和密钥泄露风险时，使用安全审查工作流。",
+      "涉及页面级认证重定向、RBAC 路由守卫和 middleware 行为时，使用路由保护工作流。"
+    ],
+    "capabilityTags": [
+      "api",
+      "typed-client",
+      "auth",
+      "upload",
+      "realtime"
+    ]
+  },
+  "fec-backend-requirements-handoff": {
+    "relatedSkills": [
+      "fec-api-integration",
+      "fec-doc-sync",
+      "fec-source-driven-development",
+      "fec-testing-strategy",
+      "fec-route-protection"
+    ],
+    "boundaryWorkflows": [
+      "当正在设计契约形态、类型化 client、认证刷新、错误映射、上传或实时实现时，使用 API 集成。",
+      "当后端决策会改变公开文档、API 说明、路由文档或 env/config 文档时，使用文档同步。",
+      "当交接重点是认证重定向、RBAC、权限路由或 middleware 行为时，使用路由保护。"
+    ],
+    "capabilityTags": [
+      "backend-requirements",
+      "handoff",
+      "api-collaboration",
+      "data-needs"
+    ]
+  },
+  "fec-browser-storage": {
+    "relatedSkills": [
+      "fec-security-review",
+      "fec-pwa-implementation",
+      "fec-state-management",
+      "fec-data-fetching"
+    ],
+    "boundaryWorkflows": [
+      "涉及 token、私有数据和 XSS 读取风险时，使用安全审查工作流。",
+      "涉及 Service Worker 离线缓存和可安装性时，使用 PWA 工作流。",
+      "涉及服务端状态和 API 缓存行为时，使用数据获取工作流。"
+    ],
+    "capabilityTags": [
+      "storage",
+      "security",
+      "offline-cache"
+    ]
+  },
+  "fec-canvas-threejs": {
+    "relatedSkills": [
+      "fec-web-workers",
+      "fec-svg-animation",
+      "fec-accessibility-check",
+      "fec-motion-interaction"
+    ],
+    "boundaryWorkflows": [
+      "当昂贵图形计算阻塞主线程时，使用 Worker工作流。",
+      "涉及小型矢量图标、路径描边和 UI 微交互时，使用 SVG 动画工作流。",
+      "涉及非文本替代内容和键盘降级路径时，使用无障碍工作流。"
+    ],
+    "capabilityTags": [
+      "canvas",
+      "threejs",
+      "performance",
+      "accessibility"
+    ]
+  },
+  "fec-code-review": {
+    "relatedSkills": [
+      "fec-security-review",
+      "fec-accessibility-check",
+      "fec-e2e-testing",
+      "fec-validation-fix",
+      "fec-performance-optimization",
+      "fec-typescript-project-standard",
+      "fec-state-management",
+      "fec-source-driven-development",
+      "fec-dependency-upgrade",
+      "fec-responsive-layout"
+    ],
+    "boundaryWorkflows": [
+      "涉及 XSS、CSRF、token、上传、第三方脚本和 CSP 风险时，使用安全审查工作流。",
+      "涉及 WCAG、键盘、焦点、语义和 ARIA 风险时，使用无障碍工作流。",
+      "涉及关键路径、不稳定测试、trace 和 CI 产物时，使用 E2E 工作流。"
+    ],
+    "capabilityTags": [
+      "code-review",
+      "quality",
+      "frontend"
+    ]
+  },
+  "fec-component-testing": {
+    "relatedSkills": [
+      "fec-testing-strategy",
+      "fec-e2e-testing",
+      "fec-storybook-component-doc",
+      "fec-accessibility-check",
+      "fec-validation-fix"
+    ],
+    "boundaryWorkflows": [
+      "在静态检查、单元、组件、集成、E2E、视觉或专项质量层之间做选择前，先使用测试策略工作流。",
+      "涉及真实浏览器跨页面旅程、登录态和 CI 产物时，使用 E2E 工作流。",
+      "当任务是运行或修复现有 lint、typecheck、test 或 build 失败时，使用验证修复工作流。"
+    ],
+    "capabilityTags": [
+      "testing",
+      "component-test",
+      "ui-quality"
+    ]
+  },
+  "fec-data-fetching": {
+    "relatedSkills": [
+      "fec-state-management",
+      "fec-form-handling",
+      "fec-pwa-implementation",
+      "fec-list-virtualization"
+    ],
+    "boundaryWorkflows": [
+      "涉及表单状态、校验和提交 UI 时，使用表单工作流。",
+      "涉及 Service Worker 和离线缓存策略时，使用 PWA 工作流。",
+      "涉及无限列表中的 DOM 渲染性能时，使用虚拟列表工作流。"
+    ],
+    "capabilityTags": [
+      "data-fetching",
+      "server-state",
+      "cache"
+    ]
+  },
+  "fec-debug-framework": {
+    "relatedSkills": [
+      "fec-dependency-upgrade"
+    ],
+    "boundaryWorkflows": [
+      "当任务目标是依赖迁移、CVE 修复、lockfile 风险审查或大版本规划时，使用依赖升级工作流。",
+      "将ordinary build failures保留在the debug workflow first中；collect evidence before deciding that dependency versions or package migration are the root cause。"
+    ],
+    "capabilityTags": [
+      "debug",
+      "diagnostic",
+      "build-error",
+      "runtime-error"
+    ]
+  },
+  "fec-dependency-upgrade": {
+    "relatedSkills": [
+      "fec-source-driven-development",
+      "fec-validation-fix",
+      "fec-refactor-clean",
+      "fec-security-review",
+      "fec-monorepo-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "决定升级路径前，先用事实源驱动开发核验官方 release notes、迁移指南、版本敏感行为和项目事实。",
+      "当任务是在升级后修复具体的 lint、typecheck、test、build 或 CI 失败时，使用验证修复 fix。",
+      "已确认的未使用依赖移除使用重构清理；版本迁移和 lockfile 风险保留在依赖升级工作流中。"
+    ],
+    "capabilityTags": [
+      "dependency-upgrade",
+      "lockfile",
+      "cve",
+      "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",
+      "fec-component-testing",
+      "fec-storybook-component-doc",
+      "fec-validation-fix"
+    ],
+    "boundaryWorkflows": [
+      "决定覆盖层级前，先使用测试策略工作流。",
+      "涉及靠近 UI 代码的单元、组件和轻量集成测试时，使用组件测试工作流。",
+      "当现有项目检查失败时，使用验证修复工作流。"
+    ],
+    "capabilityTags": [
+      "testing",
+      "e2e",
+      "browser-automation"
+    ]
+  },
+  "fec-form-handling": {
+    "relatedSkills": [
+      "fec-component-testing",
+      "fec-data-fetching",
+      "fec-state-management",
+      "fec-accessibility-check"
+    ],
+    "boundaryWorkflows": [
+      "涉及表单交互、校验错误和提交回调时，使用组件测试工作流。",
+      "涉及提交后的 mutation、缓存失效和乐观更新时，使用数据获取工作流。",
+      "涉及复杂表单中的 label、错误消息和焦点顺序时，使用无障碍工作流。"
+    ],
+    "capabilityTags": [
+      "forms",
+      "validation",
+      "accessibility"
+    ]
+  },
+  "fec-image-generation": {
+    "relatedSkills": [
+      "fec-ui-design",
+      "fec-implement-from-design",
+      "fec-canvas-threejs",
+      "fec-svg-animation",
+      "fec-responsive-layout",
+      "fec-accessibility-check",
+      "fec-web-video-presentation"
+    ],
+    "boundaryWorkflows": [
+      "涉及产品专属视觉方向、品牌调性、层级和生成资产视觉 QA 时，使用 UI 设计工作流。",
+      "当 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"
+    ]
+  },
+  "fec-legacy-to-modern-migration": {
+    "relatedSkills": [
+      "fec-legacy-web-standard",
+      "fec-react-project-standard",
+      "fec-vue3-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "迁移前需要理解原始 jQuery 或 MPA 代码模型时，使用传统前端工作流。",
+      "涉及 React 或 Vue 目录与组件结构时，使用目标框架项目工作流。",
+      "涉及边界和发布风险较高的大型迁移时，使用架构规划。"
+    ],
+    "capabilityTags": [
+      "legacy",
+      "migration",
+      "modernization"
+    ]
+  },
+  "fec-legacy-web-standard": {
+    "relatedSkills": [
+      "fec-legacy-to-modern-migration",
+      "fec-security-review",
+      "fec-validation-fix"
+    ],
+    "boundaryWorkflows": [
+      "涉及盘点、策略以及分阶段迁移到 React、Vue 或 TypeScript 时，使用迁移工作流。",
+      "涉及遗留项目中的 XSS、CSRF、开放重定向和第三方脚本风险时，使用安全审查工作流。",
+      "涉及现有 lint、test、build 或人工验证脚本时，使用验证工作流。"
+    ],
+    "capabilityTags": [
+      "legacy",
+      "migration",
+      "quality"
+    ]
+  },
+  "fec-list-virtualization": {
+    "relatedSkills": [
+      "fec-data-fetching",
+      "fec-web-workers",
+      "fec-accessibility-check"
+    ],
+    "boundaryWorkflows": [
+      "涉及无限列表中的分页和缓存行为时，使用数据获取工作流。",
+      "当expensive item computation blocks scrolling时，使用 Worker工作流。",
+      "涉及虚拟列表中的键盘和屏幕阅读器行为时，使用无障碍工作流。"
+    ],
+    "capabilityTags": [
+      "performance",
+      "virtualization",
+      "large-lists"
+    ]
+  },
+  "fec-motion-interaction": {
+    "relatedSkills": [
+      "fec-ui-design",
+      "fec-svg-animation",
+      "fec-canvas-threejs",
+      "fec-accessibility-check"
+    ],
+    "boundaryWorkflows": [
+      "需要决定视觉方向、页面层级以及动效是否适合产品语境时，使用 UI 设计工作流。",
+      "仅涉及 SVG 路径绘制、图标动效和插画动效细节时，使用 SVG 动画工作流。",
+      "涉及 WebGL、shader、3D、粒子和 canvas 渲染动画时，使用 Canvas/Three.js 工作流。"
+    ],
+    "capabilityTags": [
+      "motion",
+      "interaction",
+      "animation",
+      "accessibility"
+    ]
+  },
+  "fec-nextjs-project-standard": {
+    "relatedSkills": [
+      "fec-react-project-standard",
+      "fec-route-protection",
+      "fec-data-fetching",
+      "fec-api-integration",
+      "fec-motion-interaction"
+    ],
+    "boundaryWorkflows": [
+      "涉及通用客户端组件架构和 hooks 组织时，使用 React 项目工作流。",
+      "涉及认证、RBAC、重定向和 middleware 安全边界时，使用路由保护工作流。",
+      "客户端服务端状态使用数据获取工作流；Next 服务端 fetch 和缓存策略保留在 Next 工作流中。"
+    ],
+    "capabilityTags": [
+      "nextjs",
+      "react",
+      "routing"
+    ]
+  },
+  "fec-nuxt-project-standard": {
+    "relatedSkills": [
+      "fec-vue3-project-standard",
+      "fec-route-protection",
+      "fec-data-fetching"
+    ],
+    "boundaryWorkflows": [
+      "涉及通用 Vue 组件、composable 和 Pinia 边界时，使用 Vue 项目工作流。",
+      "涉及登录态、受保护路由、重定向和 middleware 风险时，使用路由保护工作流。",
+      "客户端服务端状态或缓存模式使用数据获取工作流；Nuxt useFetch 和 useAsyncData 策略保留在 Nuxt 工作流中。"
+    ],
+    "capabilityTags": [
+      "nuxt",
+      "vue",
+      "routing"
+    ]
+  },
+  "fec-performance-optimization": {
+    "relatedSkills": [
+      "fec-validation-fix",
+      "fec-code-review",
+      "fec-list-virtualization",
+      "fec-web-workers",
+      "fec-vite-project-standard",
+      "fec-responsive-layout"
+    ],
+    "boundaryWorkflows": [
+      "性能优化变更后需要运行 build、typecheck、测试和性能相关脚本时，使用验证工作流。",
+      "当performance findings overlap architecture, rendering correctness, or maintainability时，使用code review工作流。",
+      "仅在对应 DOM 或主线程瓶颈明确时，才使用列表虚拟化或 worker 工作流。"
+    ],
+    "capabilityTags": [
+      "performance",
+      "web-vitals",
+      "bundle",
+      "runtime"
+    ]
+  },
+  "fec-pwa-implementation": {
+    "relatedSkills": [
+      "fec-data-fetching",
+      "fec-browser-storage",
+      "fec-validation-fix"
+    ],
+    "boundaryWorkflows": [
+      "涉及 API 服务端状态、缓存失效和乐观更新时，使用数据获取工作流。",
+      "涉及 IndexedDB、localStorage 和客户端持久化选择时，使用浏览器存储工作流。",
+      "PWA 变更后需要 build、Lighthouse 和端到端验证时，使用验证工作流。"
+    ],
+    "capabilityTags": [
+      "pwa",
+      "service-worker",
+      "offline-cache"
+    ]
+  },
+  "fec-react-project-standard": {
+    "relatedSkills": [
+      "fec-typescript-project-standard",
+      "fec-state-management",
+      "fec-tailwind-design-system",
+      "fec-responsive-layout",
+      "fec-form-handling",
+      "fec-data-fetching",
+      "fec-component-testing",
+      "fec-e2e-testing",
+      "fec-accessibility-check",
+      "fec-security-review",
+      "fec-list-virtualization",
+      "fec-svg-animation",
+      "fec-canvas-threejs",
+      "fec-api-integration",
+      "fec-motion-interaction"
+    ],
+    "boundaryWorkflows": [
+      "复杂表单、状态归属、TypeScript 契约、服务端状态、测试、无障碍、安全、大列表、动画或图形问题使用对应专项工作流。",
+      "通用 React 组件架构和 hooks 组织保留在 React 项目工作流中。"
+    ],
+    "capabilityTags": [
+      "react",
+      "project-standard",
+      "fec-architecture"
+    ]
+  },
+  "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-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",
+      "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",
+      "fec-responsive-layout"
+    ],
+    "boundaryWorkflows": [
+      "需要判断风险应落在 Storybook、组件测试、E2E 还是专项评审时，使用测试策略工作流。",
+      "涉及靠近 UI 代码的单元、组件和轻量集成测试时，使用组件测试工作流。",
+      "涉及真实浏览器跨页面旅程和页面级视觉回归时，使用 E2E 工作流。"
+    ],
+    "capabilityTags": [
+      "storybook",
+      "design-system",
+      "visual-regression"
+    ]
+  },
+  "fec-svg-animation": {
+    "capabilityTags": [
+      "svg",
+      "animation",
+      "motion"
+    ],
+    "relatedSkills": [
+      "fec-motion-interaction"
+    ]
+  },
+  "fec-tailwind-design-system": {
+    "relatedSkills": [
+      "fec-ui-design",
+      "fec-responsive-layout",
+      "fec-storybook-component-doc",
+      "fec-react-project-standard",
+      "fec-vue3-project-standard"
+    ],
+    "boundaryWorkflows": [
+      "编码 Tailwind tokens 前，需要先用 UI 设计明确产品专属视觉方向、层级和设计系统意图。",
+      "涉及跨设备行为、容器查询、数据密集布局和视口验证时，使用响应式布局工作流。",
+      "展示组件变体、状态和设计系统示例时，使用 Storybook 组件文档。"
+    ],
+    "capabilityTags": [
+      "tailwind",
+      "design-system",
+      "tokens",
+      "variants",
+      "dark-mode"
+    ]
+  },
+  "fec-tdd-workflow": {
+    "relatedSkills": [
+      "fec-component-testing",
+      "fec-e2e-testing",
+      "fec-testing-strategy",
+      "fec-validation-fix"
+    ],
+    "boundaryWorkflows": [
+      "涉及组件、hook、composable 和轻量集成测试时，使用组件测试工作流。",
+      "涉及真实浏览器关键路径时，使用 E2E 工作流。",
+      "现有检查失败后，使用验证工作流。"
+    ],
+    "capabilityTags": [
+      "tdd",
+      "testing",
+      "workflow"
+    ]
+  },
+  "fec-testing-strategy": {
+    "relatedSkills": [
+      "fec-component-testing",
+      "fec-e2e-testing",
+      "fec-storybook-component-doc",
+      "fec-validation-fix",
+      "fec-accessibility-check",
+      "fec-security-review",
+      "fec-code-review"
+    ],
+    "boundaryWorkflows": [
+      "测试层级和风险归属确定后，再使用专项测试工作流。",
+      "深度专项质量评审使用无障碍、安全或代码评审工作流。"
+    ],
+    "capabilityTags": [
+      "testing",
+      "strategy",
+      "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",
+      "fec-implement-from-design",
+      "fec-accessibility-check",
+      "fec-code-review",
+      "fec-tailwind-design-system",
+      "fec-responsive-layout",
+      "fec-storybook-component-doc",
+      "fec-web-video-presentation"
+    ],
+    "boundaryWorkflows": [
+      "当an external design file is the source of truth时，使用按设计实现工作流。",
+      "涉及键盘、焦点、ARIA、语义结构和对比度检查时，使用无障碍工作流。",
+      "当UI issues cross architecture, types, rendering performance, and maintainability时，使用code review工作流。",
+      "生成的设计系统建议只作为方向；外部设计文件、项目 tokens 和已发布组件 API 仍是权威来源。"
+    ],
+    "capabilityTags": [
+      "ui-design",
+      "design-direction",
+      "design-system",
+      "master-page-overrides",
+      "industry-ui",
+      "visual-identity",
+      "ui-polish",
+      "anti-generic",
+      "visual-qa",
+      "chart-ux",
+      "accessibility"
+    ]
+  },
+  "fec-vite-project-standard": {
+    "relatedSkills": [
+      "fec-react-project-standard",
+      "fec-vue3-project-standard",
+      "fec-monorepo-project-standard",
+      "fec-security-review",
+      "fec-motion-interaction"
+    ],
+    "boundaryWorkflows": [
+      "涉及组件架构、状态和目录结构时，使用框架项目工作流。",
+      "涉及 workspace 边界和任务编排时，使用 monorepo 工作流。",
+      "涉及客户端密钥、CSP、供应链和 XSS 风险时，使用安全审查工作流。"
+    ],
+    "capabilityTags": [
+      "vite",
+      "build",
+      "project-standard"
+    ]
+  },
+  "fec-vue3-project-standard": {
+    "relatedSkills": [
+      "fec-typescript-project-standard",
+      "fec-state-management",
+      "fec-tailwind-design-system",
+      "fec-responsive-layout",
+      "fec-form-handling",
+      "fec-data-fetching",
+      "fec-component-testing",
+      "fec-e2e-testing",
+      "fec-accessibility-check",
+      "fec-security-review",
+      "fec-list-virtualization",
+      "fec-svg-animation",
+      "fec-canvas-threejs"
+    ],
+    "boundaryWorkflows": [
+      "复杂表单、状态归属、TypeScript 契约、服务端状态、测试、无障碍、安全、大列表、动画或图形问题使用对应专项工作流。",
+      "通用 Vue 组件架构、composables 和 Pinia 边界保留在 Vue 项目工作流中。"
+    ],
+    "capabilityTags": [
+      "vue",
+      "project-standard",
+      "fec-architecture"
+    ]
+  },
+  "fec-web-video-presentation": {
+    "relatedSkills": [
+      "fec-ui-design",
+      "fec-image-generation",
+      "fec-motion-interaction",
+      "fec-responsive-layout",
+      "fec-accessibility-check"
+    ],
+    "boundaryWorkflows": [
+      "涉及产品专属视觉方向、资产策略、反通用设计和场景视觉 QA 时，使用 UI 设计工作流。",
+      "当the presentation needs custom raster assets, diagrams, storyboard frames, or generated visual references时，使用图像生成。",
+      "当scene transitions, reduced-motion behavior, viewport scaling, or recording stability need deeper treatment时，使用动效 and 响应式布局 workflows。"
+    ],
+    "capabilityTags": [
+      "web-video",
+      "presentation",
+      "recording",
+      "script-outline",
+      "step-driven-stage"
+    ]
+  },
+  "fec-web-workers": {
+    "relatedSkills": [
+      "fec-canvas-threejs",
+      "fec-list-virtualization",
+      "fec-validation-fix"
+    ],
+    "boundaryWorkflows": [
+      "复杂计算阻塞渲染时，渲染与动画循环使用图形工作流；只有计算卸载才使用 Workers。",
+      "大列表 DOM 渲染使用虚拟列表工作流；不要用 worker 替代虚拟滚动。",
+      "worker 变更后需要 build、typecheck 和关键交互验证时，使用验证工作流。"
+    ],
+    "capabilityTags": [
+      "web-workers",
+      "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"
+    ]
+  }
+}