@bovinphang/frontend-craft 2.8.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,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": [
+      "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-refactoring-api": {
+    "relatedSkills": [
+      "fec-refactoring",
+      "fec-code-smells",
+      "fec-refactoring-catalog",
+      "fec-refactoring-validation",
+      "fec-api-integration",
+      "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",
+      "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": [
+      "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-control": {
+    "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",
+      "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": [
+      "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",
@@ -489,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": [
-      "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."
-    ],
-    "capabilityTags": [
-      "source-driven",
-      "official-docs",
-      "version-sensitive"
-    ]
-  },
   "fec-state-management": {
     "relatedSkills": [
       "fec-data-fetching",
@@ -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",

package/templates/shared/rules/fec-agent-workflow.md

@@ -41,6 +41,7 @@ Merge rules:
 ## Collaboration constraints
 
 - Clarify the scope, input and output before delegating, and do not leave ambiguous tasks to sub-agents.
+- For automatic review after edits, explicitly pass the current change scope (files and diff/PR/commit context). Unqualified review defaults to the entire project; specifying a file/directory alone requests full review of that scope, not incremental review.
 - Multiple independent problems can be analyzed in parallel; tasks that depend on each other are advanced in sequence.
 - Subagent output must lead to verifiable conclusions: reports, file paths, command results, or specific risks.
 - Subagent suggestions do not automatically equal implementation decisions; when they conflict with the existing contracts of the warehouse, the warehouse contracts take precedence.

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

@@ -1,31 +1,5 @@
-# Source-driven development rules
+# Frontend source checks
 
-When an implementation relies on a framework, library, browser, runtime, build tool, or platform behavior, confirm the source of truth before writing code or reviewing conclusions.
+For version-sensitive frontend decisions, inspect actual framework/library versions, routing/rendering modes, caches, build configuration, browser APIs and compatibility.
 
-## Fact source priority
-
-1. README, configuration, testing, templates and existing implementations within the project.
-2. Official documents, source code, type definitions, release notes, migration guide.
-3. Web standards, browser compatibility data, and platform documentation.
-4. Issues, discussions, blogs and third-party articles are only used as clues.
-
-## Usage scenarios
-
-- New versions of frameworks, routing, rendering modes, caching, build configurations, browser APIs.
-- Public interfaces, component APIs, design system tokens, CLI commands, and plugin metadata.
-- Dependency upgrade, migration, obsolete API replacement, cross-runtime compatibility.
-- Version-sensitive judgments related to security, performance, and accessibility.
-
-## Output requirements
-
-- Write down the source, version or project facts, decision conclusion, scope of influence and verification method.
-- If the current status of the project conflicts with official recommendations, explain the cause of the conflict and the gradual migration strategy.
-- Do not copy long external documents; only keep necessary conclusions, links or file paths within the project.
-- Mark uncertainties and matters requiring confirmation from the user/team when they cannot be verified.
-
-## Anti-pattern
-
-- Use version-sensitive APIs from memory.
-- Replace official documentation with outdated tutorials.
-- Overturn the stable project agreement in order to pursue new projects.
-- Scatter external library behavior assumptions throughout components instead of centralizing them in the adaptation layer.
+The product supplies the common source-driven method. Frontend-specific evidence includes component APIs, design tokens, browser security, performance, accessibility, package exports and runtime integration. Use project implementation and authoritative versioned sources; record versions, impact and observed verification instead of treating old tutorials as stable contracts.