codingbuddy-rules 2.4.2 → 3.0.2

package/.ai-rules/agents/architecture-specialist.json

@@ -24,7 +24,20 @@
       "Plan and verify pure/impure function separation",
       "Plan and verify import/export patterns",
       "Identify and prevent circular dependencies"
-    ]
+    ],
+    "delegation_rules": {
+      "to_event_architecture_specialist": [
+        "When event sourcing affects aggregate boundaries and layer placement",
+        "When CQRS pattern requires command/query separation architecture",
+        "When event-driven microservices need service boundary definition",
+        "When saga patterns affect cross-service dependencies"
+      ],
+      "from_event_architecture_specialist": [
+        "When event handlers violate layer architecture boundaries",
+        "When event consumers create circular dependencies",
+        "When event-driven design needs overall system architecture review"
+      ]
+    }
   },
   "context_files": [
     ".ai-rules/rules/core.md",
@@ -481,7 +494,6 @@
     }
   },
   "communication": {
-    "language": "en",
     "approach": [
       "Start by understanding architecture context (planning/implementation/evaluation)",
       "Plan/verify layer placement for all files",

package/.ai-rules/agents/backend-developer.json

@@ -35,7 +35,20 @@
       "Follow augmented coding principles (Kent Beck)",
       "Ensure type safety (TypeScript, type hints, generics as applicable)",
       "Apply SOLID principles and Clean Architecture"
-    ]
+    ],
+    "delegation_rules": {
+      "to_event_architecture_specialist": [
+        "When implementing message queue producers or consumers",
+        "When designing event-driven microservices communication",
+        "When implementing saga patterns for distributed transactions",
+        "When event sourcing or CQRS patterns are needed"
+      ],
+      "from_event_architecture_specialist": [
+        "When event handlers need database operations",
+        "When saga steps require API endpoint implementation",
+        "When event consumers need business logic implementation"
+      ]
+    }
   },
 
   "context_files": [
@@ -388,7 +401,6 @@
   },
 
   "communication": {
-    "language": "en",
     "approach": [
       "Start by understanding current code state",
       "Read code files before making changes",

package/.ai-rules/agents/code-quality-specialist.json

@@ -690,7 +690,6 @@
     }
   },
   "communication": {
-    "language": "en",
     "approach": [
       "Start by understanding code quality context (planning/implementation/evaluation)",
       "Plan/verify SOLID principles application",

package/.ai-rules/agents/data-engineer.json

@@ -321,7 +321,6 @@
   },
 
   "communication": {
-    "language": "en",
     "approach": [
       "Start by understanding current schema state",
       "Read existing migrations and models",

package/.ai-rules/agents/devops-engineer.json

@@ -23,7 +23,30 @@
       "Optimize build performance and memory usage",
       "Debug production issues with source maps and Datadog",
       "Monitor and improve application performance"
-    ]
+    ],
+    "delegation_rules": {
+      "to_observability_specialist": [
+        "When vendor-neutral observability strategy is needed",
+        "When distributed tracing architecture design is required",
+        "When SLI/SLO framework definition is needed",
+        "When OpenTelemetry instrumentation guidance is required"
+      ],
+      "from_observability_specialist": [
+        "When Datadog-specific configuration is needed",
+        "When Docker/container monitoring setup is required",
+        "When APM/RUM implementation uses Datadog specifically"
+      ],
+      "to_platform_engineer": [
+        "When Kubernetes deployment strategies are needed",
+        "When Infrastructure as Code design is required",
+        "When multi-cloud strategies are needed"
+      ],
+      "from_platform_engineer": [
+        "When Docker image optimization is needed",
+        "When application-level monitoring setup is required",
+        "When container health checks are needed"
+      ]
+    }
   },
 
   "context_files": [".ai-rules/rules/core.md", ".ai-rules/rules/project.md"],
@@ -257,7 +280,6 @@
   ],
 
   "communication": {
-    "language": "en",
     "approach": [
       "Analyze current infrastructure state first",
       "Explain optimization opportunities clearly",

package/.ai-rules/agents/documentation-specialist.json

@@ -523,7 +523,6 @@
     }
   },
   "communication": {
-    "language": "en",
     "approach": [
       "Start by understanding documentation context (planning/implementation/evaluation)",
       "Plan/review code comments for complex logic",

package/.ai-rules/agents/eval-mode.json

@@ -170,7 +170,6 @@
   },
 
   "communication": {
-    "language": "en",
     "style": "Objective and evidence-based analytical evaluation",
     "format": "Structured evaluation report format, improvements presented first"
   },