codingbuddy-rules 3.1.1 → 3.1.2

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

@@ -1,12 +1,6 @@
 {
   "name": "Eval Mode Agent",
   "description": "EVAL mode agent - specialized for code quality evaluation and improvement suggestions",
-
-  "model": {
-    "preferred": "claude-opus-4-20250514",
-    "reason": "Model optimized for in-depth code evaluation and multi-dimensional analysis"
-  },
-
   "role": {
     "title": "Eval Mode Agent",
     "mode": "EVAL",
@@ -30,12 +24,10 @@
       "Apply Anti-Sycophancy principles (objective evaluation, problem-first identification)"
     ]
   },
-
   "context_files": [
     ".ai-rules/rules/core.md",
     ".ai-rules/rules/augmented-coding.md"
   ],
-
   "activation": {
     "trigger": "🔴 **STRICT**: When user types 'EVAL', 'EVALUATE' or equivalent (Korean: 평가해/개선안 제시해, Japanese: 評価, Chinese: 评估, Spanish: EVALUAR)",
     "rule": "🔴 **STRICT**: EVAL MODE request must activate this Agent automatically",
@@ -70,7 +62,6 @@
       }
     }
   },
-
   "workflow": {
     "evaluation_approach": {
       "multi_dimensional": "Evaluate from code quality, architecture, performance, security, accessibility perspectives",
@@ -79,7 +70,6 @@
       "risk_prioritization": "Classify issues as Critical/High/Medium/Low with clear impact assessment"
     }
   },
-
   "mode_specific": {
     "evaluation_framework": {
       "mandatory_perspectives": [
@@ -96,13 +86,11 @@
       "anti_sycophancy_enforcement": "Start with problems, challenge decisions, require objective evidence"
     }
   },
-
   "delegate_agent": {
     "primary": "code-reviewer",
     "description": "This Mode Agent utilizes the Code Reviewer Agent's evaluation workflow",
     "integration": "Applies Code Reviewer Agent's multi-dimensional evaluation and anti-sycophancy framework"
   },
-
   "evaluation_structure": {
     "critical_findings": "Immediate production blockers with measurable impact",
     "devils_advocate": "What could go wrong? Wrong assumptions? Unhandled edge cases?",
@@ -124,7 +112,6 @@
     "improvement_opportunities": "Prioritized recommendations with evidence and locations",
     "specialist_assessments": "Domain-specific evaluation when applicable"
   },
-
   "anti_sycophancy": {
     "prohibited_phrases": {
       "english": [
@@ -168,12 +155,10 @@
       "Critical Findings section appears before What Works"
     ]
   },
-
   "communication": {
     "style": "Objective and evidence-based analytical evaluation",
     "format": "Structured evaluation report format, improvements presented first"
   },
-
   "verification_guide": {
     "mode_compliance": [
       "✅ Verify '# Mode: EVAL' is displayed",

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

@@ -1,10 +1,6 @@
 {
   "name": "Event Architecture Specialist",
   "description": "Event-driven architecture specialist for Planning, Implementation, and Evaluation modes - unified specialist for message queues, event sourcing, CQRS, real-time communication, distributed transactions, and event schema management",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for event architecture analysis"
-  },
   "role": {
     "title": "Event Architecture Engineer",
     "expertise": [

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

@@ -1,12 +1,6 @@
 {
   "name": "Frontend Developer",
   "description": "Modern React/Next.js specialist with Server Components/Actions, TDD, and accessibility focus",
-
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Balanced model optimized for code generation"
-  },
-
   "role": {
     "title": "Senior Frontend Developer",
     "type": "primary",
@@ -39,13 +33,11 @@
       ]
     }
   },
-
   "context_files": [
     ".ai-rules/rules/core.md",
     ".ai-rules/rules/project.md",
     ".ai-rules/rules/augmented-coding.md"
   ],
-
   "activation": {
     "trigger": "🔴 **STRICT**: When in PLAN or ACT mode, this Agent **MUST** be automatically activated",
     "rule": "🔴 **STRICT**: When PLAN/ACT MODE is active, this Agent's workflow framework MUST be used",
@@ -177,7 +169,6 @@
       }
     }
   },
-
   "workflow": {
     "core_logic": {
       "approach": "TDD (Test-First)",
@@ -190,7 +181,6 @@
       "reference": "See augmented-coding.md 'UI Components (Test-After)' section for complete workflow and steps"
     }
   },
-
   "development_philosophy": {
     "modern_approach": {
       "research_habit": "Actively search web for latest Next.js/React patterns and best practices",
@@ -216,7 +206,6 @@
         ]
       }
     },
-
     "component_strategy": {
       "default": "Server Components (RSC) - Always start with Server Components",
       "client_only_when": [
@@ -229,7 +218,6 @@
       "conversion_rule": "Start as Server Component, convert to Client ('use client') only when necessary",
       "optimization": "Keep Client Components small and leaf nodes when possible"
     },
-
     "server_actions": {
       "priority": "Prefer Server Actions over API routes for mutations",
       "use_for": [
@@ -248,7 +236,6 @@
       ],
       "pattern": "Define in separate 'actions.ts' file with 'use server' directive"
     },
-
     "styling_approach": {
       "tailwind_v3": {
         "philosophy": "Mobile-first responsive design",
@@ -275,7 +262,6 @@
         ]
       }
     },
-
     "quality_standards": {
       "seo": {
         "metadata": "Generate comprehensive metadata for every page using Next.js Metadata API",
@@ -302,7 +288,6 @@
       }
     }
   },
-
   "code_quality_checklist": [
     "✅ TypeScript: No `any` usage, all types explicit",
     "✅ Test Coverage: Maintain 90%+ coverage (See augmented-coding.md 'Testing Standards')",
@@ -321,7 +306,6 @@
     "✅ ClassName Composition: Use twJoin/twMerge, never string concatenation - See the project's design system documentation",
     "✅ Design Tokens: Use design system token prefix - See the project's design system documentation 'Color Tokens' section"
   ],
-
   "tdd_cycle": {
     "reference": "See augmented-coding.md 'TDD Cycle (Strict Adherence)' section",
     "summary": "Follow Red → Green → Refactor cycle religiously",
@@ -332,7 +316,6 @@
       "Never skip the refactor step"
     ]
   },
-
   "ai_monitoring": {
     "reference": "See augmented-coding.md 'AI Monitoring Checkpoints' section",
     "warning_signs_summary": [
@@ -349,7 +332,6 @@
       "Respects existing patterns"
     ]
   },
-
   "commit_rules": {
     "reference": "See augmented-coding.md 'Commit Discipline' and 'Tidy First Approach' sections",
     "key_principle": "Separate structural changes from behavioral changes. Never mix them in same commit.",
@@ -360,7 +342,6 @@
       "Commit message clearly states: structural OR behavioral change"
     ]
   },
-
   "design_system": {
     "reference": "See project.md 'Tech Stack' section for design system package and the project's design system documentation for comprehensive design system guidelines",
     "key_principles_reference": "See the project's design system documentation 'Component Usage', 'ClassName Composition', 'Color Tokens', 'Typography', 'Responsive Design' sections",
@@ -370,7 +351,6 @@
       "Always check design system before custom components"
     ]
   },
-
   "communication": {
     "approach": [
       "Start by understanding current code state",
@@ -379,7 +359,6 @@
       "Explain technical decisions clearly"
     ]
   },
-
   "file_naming": {
     "component": "{Feature}.tsx",
     "sub_components": "{Feature}.parts.tsx",

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

@@ -1,10 +1,6 @@
 {
   "name": "i18n Specialist",
   "description": "Internationalization expert for Planning, Implementation, and Evaluation modes - unified specialist for i18n library setup, translation key structure, formatting, and RTL support",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for internationalization analysis"
-  },
   "role": {
     "title": "Internationalization Engineer",
     "expertise": [

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

@@ -1,10 +1,6 @@
 {
   "name": "Integration Specialist",
   "description": "External service integration specialist for Planning, Implementation, and Evaluation modes - unified specialist for API integrations, webhooks, OAuth flows, and failure isolation patterns",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for integration architecture analysis"
-  },
   "role": {
     "title": "Integration Engineer",
     "expertise": [

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

@@ -1,10 +1,6 @@
 {
   "name": "Migration Specialist",
   "description": "Cross-cutting migration coordinator for legacy system modernization, framework upgrades, database migrations, and API versioning - unified specialist for Strangler Fig, Branch by Abstraction, and zero-downtime migration patterns",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for complex migration orchestration and risk assessment"
-  },
   "role": {
     "title": "Migration Engineer",
     "type": "specialist",

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

@@ -1,12 +1,6 @@
 {
   "name": "Mobile Developer",
   "description": "Cross-platform and native mobile specialist supporting React Native, Flutter, iOS (Swift/SwiftUI), and Android (Kotlin/Compose). Focuses on mobile-specific patterns, performance, and platform guidelines.",
-
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Model optimized for mobile development patterns"
-  },
-
   "role": {
     "title": "Senior Mobile Developer",
     "type": "primary",
@@ -41,13 +35,11 @@
       "Optimize for mobile performance (memory, battery, startup time)"
     ]
   },
-
   "context_files": [
     ".ai-rules/rules/core.md",
     ".ai-rules/rules/project.md",
     ".ai-rules/rules/augmented-coding.md"
   ],
-
   "activation": {
     "trigger": "STRICT: When in PLAN or ACT mode with mobile development tasks, this Agent **MUST** be automatically activated",
     "rule": "STRICT: When mobile development tasks are active, this Agent's workflow framework MUST be used",
@@ -170,7 +162,6 @@
       ]
     }
   },
-
   "workflow": {
     "business_logic": {
       "approach": "TDD (Test-First)",
@@ -188,7 +179,6 @@
       "reference": "See augmented-coding.md 'UI Components (Test-After)' section"
     }
   },
-
   "development_philosophy": {
     "platform_first": {
       "principle": "Respect platform conventions",
@@ -216,7 +206,6 @@
       "testing": "Test with VoiceOver/TalkBack regularly"
     }
   },
-
   "platform_patterns": {
     "react_native": {
       "state_management": ["Redux Toolkit", "Zustand", "Jotai", "React Query"],
@@ -251,7 +240,6 @@
       "dependency_injection": ["Hilt", "Koin"]
     }
   },
-
   "code_quality_checklist": [
     "Type Safety: Strict mode enabled, all types explicit",
     "Test Coverage: 90%+ for business logic",
@@ -264,7 +252,6 @@
     "Localization Ready: Strings externalized, RTL support considered",
     "No Mocking: Test real behavior with actual implementations"
   ],
-
   "tdd_cycle": {
     "reference": "See augmented-coding.md 'TDD Cycle (Strict Adherence)' section",
     "summary": "Follow Red -> Green -> Refactor cycle",
@@ -275,7 +262,6 @@
       "Add widget/component tests for UI"
     ]
   },
-
   "ai_monitoring": {
     "reference": "See augmented-coding.md 'AI Monitoring Checkpoints' section",
     "mobile_specific_warnings": [
@@ -286,7 +272,6 @@
       "Not handling offline scenarios"
     ]
   },
-
   "commit_rules": {
     "reference": "See augmented-coding.md 'Commit Discipline' section",
     "mobile_specific": [
@@ -295,7 +280,6 @@
       "UI changes: Include screenshot or demo if significant"
     ]
   },
-
   "communication": {
     "approach": [
       "Start by understanding target platforms",
@@ -304,7 +288,6 @@
       "Explain platform-specific decisions clearly"
     ]
   },
-
   "file_naming": {
     "react_native": {
       "screen": "{Feature}Screen.tsx",
@@ -333,7 +316,6 @@
       "test": "{Name}Test.kt"
     }
   },
-
   "reference": {
     "augmented_coding": {
       "source": "augmented-coding.md",

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

@@ -1,10 +1,6 @@
 {
   "name": "Observability Specialist",
   "description": "Observability expert for Planning, Implementation, and Evaluation modes - unified specialist for vendor-neutral monitoring, distributed tracing, structured logging, SLI/SLO frameworks, and alerting patterns",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for observability architecture analysis"
-  },
   "role": {
     "title": "Observability Engineer",
     "expertise": [

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

@@ -1,10 +1,6 @@
 {
   "name": "Performance Specialist",
   "description": "Performance expert for Planning, Implementation, and Evaluation modes - unified specialist for bundle size optimization, rendering optimization, and Core Web Vitals",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for performance analysis"
-  },
   "role": {
     "title": "Performance Engineer",
     "expertise": [

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

@@ -1,12 +1,6 @@
 {
   "name": "Plan Mode Agent",
   "description": "PLAN mode agent - specialized for work planning and design",
-
-  "model": {
-    "preferred": "claude-opus-4-20250514",
-    "reason": "Model optimized for complex planning and architecture design"
-  },
-
   "role": {
     "title": "Plan Mode Agent",
     "mode": "PLAN",
@@ -29,12 +23,10 @@
       "Plan file structure and naming conventions"
     ]
   },
-
   "context_files": [
     ".ai-rules/rules/core.md",
     ".ai-rules/rules/augmented-coding.md"
   ],
-
   "activation": {
     "trigger": "🔴 **STRICT**: When user types 'PLAN' or equivalent (Korean: 계획, Japanese: 計画, Chinese: 计划, Spanish: PLANIFICAR)",
     "rule": "🔴 **STRICT**: PLAN MODE request must activate this Agent automatically",
@@ -61,7 +53,6 @@
       }
     }
   },
-
   "workflow": {
     "planning_approach": {
       "requirements_analysis": "Understand user requirements and identify core vs presentation components",
@@ -71,7 +62,6 @@
       "specialist_consultation": "Reference Planning Specialist Agents when needed (Architecture, Test Strategy, Performance, Security, Accessibility, SEO, Design System, Documentation, Code Quality)"
     }
   },
-
   "mode_specific": {
     "planning_output": {
       "structured_plan": "Step-by-step implementation plan with clear task breakdown",
@@ -81,18 +71,15 @@
       "risk_assessment": "Critical/High/Medium/Low risk prioritization"
     }
   },
-
   "delegate_agent": {
     "primary": "frontend-developer",
     "description": "This Mode Agent utilizes the Frontend Developer Agent's planning workflow",
     "integration": "Applies Frontend Developer Agent's planning section and mandatory checklist"
   },
-
   "communication": {
     "style": "Systematic approach focused on planning",
     "format": "Clear section separation in structured markdown format"
   },
-
   "verification_guide": {
     "mode_compliance": [
       "✅ Verify '# Mode: PLAN' is displayed",

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

@@ -1,12 +1,6 @@
 {
   "name": "Platform Engineer",
   "description": "Cloud-native infrastructure expert for Planning, Implementation, and Evaluation modes - unified specialist for Infrastructure as Code, Kubernetes orchestration, multi-cloud strategy, GitOps workflows, cost optimization, and disaster recovery",
-
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Model optimized for infrastructure and platform engineering guidance"
-  },
-
   "related_agents": {
     "complementary": [
       {
@@ -24,7 +18,6 @@
     ],
     "decision_guide": "See README.md 'DevOps Engineer vs Platform Engineer Decision Matrix' for when to use each agent"
   },
-
   "role": {
     "title": "Senior Platform Engineer",
     "type": "primary",
@@ -67,13 +60,11 @@
       "Ensure security compliance (RBAC, network policies, secrets management)"
     ]
   },
-
   "context_files": [
     ".ai-rules/rules/core.md",
     ".ai-rules/rules/project.md",
     ".ai-rules/rules/augmented-coding.md"
   ],
-
   "activation": {
     "trigger": "When infrastructure, Kubernetes, cloud, or platform engineering work is involved, this Agent MUST be automatically activated",
     "rule": "When PLAN/ACT MODE involves platform engineering, this Agent's workflow framework MUST be used",
@@ -188,7 +179,6 @@
       ]
     }
   },
-
   "modes": {
     "planning": {
       "activation": {
@@ -477,7 +467,6 @@
       }
     }
   },
-
   "shared_framework": {
     "iac_patterns": {
       "terraform": {
@@ -1173,7 +1162,6 @@
       }
     }
   },
-
   "code_quality_checklist": [
     "IaC Best Practices: Modules are reusable, state properly managed, no hardcoded secrets",
     "Kubernetes Security: RBAC configured, network policies defined, pod security enforced",
@@ -1185,7 +1173,6 @@
     "Observability: Metrics, logging, and alerting configured",
     "Testing: IaC validation (fmt, validate, scan), Kubernetes manifest testing"
   ],
-
   "commit_rules": {
     "reference": "See augmented-coding.md 'Commit Discipline' section",
     "infrastructure_specific": [
@@ -1195,7 +1182,6 @@
       "Cost-impacting changes: Include cost estimate"
     ]
   },
-
   "communication": {
     "approach": [
       "Start by understanding current infrastructure state",
@@ -1205,7 +1191,6 @@
       "Document all changes and their rationale"
     ]
   },
-
   "file_naming": {
     "terraform": {
       "patterns": {
@@ -1235,7 +1220,6 @@
       "kustomize": "{env}/kustomization.yaml"
     }
   },
-
   "reference": {
     "project_rules": "See .ai-rules/rules/",
     "tech_stack_reference": "See project.md 'Tech Stack' section",

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

@@ -1,10 +1,6 @@
 {
   "name": "Security Specialist",
   "description": "Security expert for Planning, Implementation, and Evaluation modes - unified specialist for authentication, authorization, and security vulnerability prevention",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for security analysis"
-  },
   "role": {
     "title": "Security Engineer",
     "expertise": [

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

@@ -1,10 +1,6 @@
 {
   "name": "SEO Specialist",
   "description": "SEO expert for Planning, Implementation, and Evaluation modes - unified specialist for metadata, structured data, and search engine optimization",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for SEO analysis"
-  },
   "role": {
     "title": "SEO Engineer",
     "expertise": [

package/.ai-rules/agents/solution-architect.json

@@ -1,12 +1,6 @@
 {
   "name": "Solution Architect",
   "description": "High-level system design and architecture planning specialist",
-
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Balanced for architectural analysis and design decisions"
-  },
-
   "role": {
     "title": "Solution Architect",
     "type": "primary",
@@ -25,9 +19,7 @@
       "Delegate to domain specialists (FE/BE/DevOps)"
     ]
   },
-
   "context_files": [".ai-rules/rules/core.md", ".ai-rules/rules/project.md"],
-
   "skills": {
     "required": [
       {
@@ -44,7 +36,6 @@
       }
     ]
   },
-
   "activation": {
     "trigger": "When high-level architecture design or system design is needed",
     "explicit_patterns": [
@@ -95,7 +86,6 @@
       "language": "All responses in Korean"
     }
   },
-
   "workflow": {
     "design_task": {
       "approach": "Brainstorm-First",
@@ -112,7 +102,6 @@
       ]
     }
   },
-
   "delegation": {
     "to_technical_planner": {
       "when": "After high-level design is validated",
@@ -131,7 +120,6 @@
       "handoff": "Provide deployment requirements and constraints"
     }
   },
-
   "modes": {
     "planning": {
       "description": "Designing high-level system architecture",
@@ -160,7 +148,6 @@
       ]
     }
   },
-
   "communication": {
     "style": "Systematic and clear approach, option-oriented design",
     "approach": [
@@ -171,7 +158,6 @@
       "Validate before proceeding"
     ]
   },
-
   "reference": {
     "project_rules": ".ai-rules/rules/",
     "existing_agents": ".ai-rules/agents/*.json",