codingbuddy-rules 2.0.0 → 2.2.0

package/.ai-rules/adapters/q.md

@@ -29,7 +29,7 @@ Refer to `.ai-rules/rules/core.md` for:
 ### Project Setup
 
 Refer to `.ai-rules/rules/project.md` for:
-- **Tech Stack**: 프로젝트의 package.json 참조
+- **Tech Stack**: See project package.json
 - **Architecture**: Layered structure (app → widgets → features → entities → shared)
 - **Development Rules**: File naming, import/export conventions
 
@@ -56,8 +56,8 @@ Refer to `.ai-rules/agents/*.json` for domain-specific knowledge:
 - Apply Q's cost optimization suggestions
 
 ### Language Support
-- Respond in Korean (한국어) as per project standard
-- Use technical Korean terminology
+- Follow project's configured language setting
+- Use appropriate technical terminology
 ```
 
 ## Directory Structure
@@ -84,7 +84,7 @@ Refer to `.ai-rules/agents/*.json` for domain-specific knowledge:
 ### In Amazon Q Chat
 
 ```
-You: 새로운 API 엔드포인트 만들어줘
+You: Build a new API endpoint
 
 Q: [Follows .ai-rules/rules/core.md workflow]
    [Applies .ai-rules/rules/augmented-coding.md TDD]
@@ -119,6 +119,63 @@ Combine Q's AWS expertise with project rules:
 - Let Q provide AWS-specific security guidance
 - Apply `.ai-rules/agents/devops-engineer.json` for deployment patterns
 
+## AUTO Mode
+
+AUTO mode enables autonomous PLAN -> ACT -> EVAL cycling until quality criteria are met.
+
+### Triggering AUTO Mode
+
+Use the `AUTO` keyword (or localized versions) at the start of your message:
+
+| Language | Keyword |
+|----------|---------|
+| English | `AUTO` |
+| Korean | `자동` |
+| Japanese | `自動` |
+| Chinese | `自动` |
+| Spanish | `AUTOMATICO` |
+
+### Example Usage
+
+```
+AUTO 새로운 Lambda 함수 만들어줘
+```
+
+### Workflow
+
+1. **PLAN Phase**: Creates implementation plan with quality criteria
+2. **ACT Phase**: Executes implementation following TDD workflow
+3. **EVAL Phase**: Evaluates quality against exit criteria
+4. **Loop/Exit**: Continues cycling until:
+   - Success: `Critical = 0 AND High = 0`
+   - Failure: Max iterations reached (default: 3)
+
+### AWS Integration with AUTO Mode
+
+Amazon Q's AWS expertise complements AUTO mode:
+- Leverages Q's security scanning during EVAL phase
+- Applies AWS best practices during ACT phase
+- Uses Q's cost optimization suggestions in planning
+
+### Configuration
+
+Configure in `codingbuddy.config.js`:
+
+```javascript
+module.exports = {
+  auto: {
+    maxIterations: 3
+  }
+};
+```
+
+### When to Use
+
+- Large feature implementations requiring multiple refinement cycles
+- Complex refactoring with quality verification
+- AWS service integrations needing thorough testing
+- Infrastructure as Code development with validation cycles
+
 ## Maintenance
 
 1. Update `.ai-rules/rules/*.md` for universal changes

package/.ai-rules/agents/README.md

@@ -28,6 +28,8 @@ AI Agent definitions for specialized development roles.
 | **Implementation Planning** | Technical Planner | `technical-planner.json` |
 | **React/Next.js Development** | Frontend Developer | `frontend-developer.json` |
 | **Backend API Development** | Backend Developer | `backend-developer.json` |
+| **Database/Schema Design** | Data Engineer | `data-engineer.json` |
+| **Mobile App Development** | Mobile Developer | `mobile-developer.json` |
 | **Code Review (EVAL)** | Code Reviewer | `code-reviewer.json` |
 | **Architecture Design** | Architecture Specialist | `architecture-specialist.json` |
 | **Test Strategy** | Test Strategy Specialist | `test-strategy-specialist.json` |
@@ -36,9 +38,11 @@ AI Agent definitions for specialized development roles.
 | **Accessibility Review** | Accessibility Specialist | `accessibility-specialist.json` |
 | **SEO Optimization** | SEO Specialist | `seo-specialist.json` |
 | **UI/UX Design** | UI/UX Designer | `ui-ux-designer.json` |
+| **Internationalization** | i18n Specialist | `i18n-specialist.json` |
 | **Documentation** | Documentation Specialist | `documentation-specialist.json` |
 | **Code Quality** | Code Quality Specialist | `code-quality-specialist.json` |
 | **Infrastructure/Deployment** | DevOps Engineer | `devops-engineer.json` |
+| **Config/Build Tools** | Tooling Engineer | `tooling-engineer.json` |
 | **Agent Management** | Agent Architect | `agent-architect.json` |
 
 ### Agent Summary
@@ -49,6 +53,8 @@ AI Agent definitions for specialized development roles.
 | Technical Planner | Low-level implementation planning with TDD and bite-sized tasks |
 | Frontend Developer | TDD-based frontend development with React/Next.js |
 | Backend Developer | Multi-stack backend API development (Node, Python, Go, Java, Rust) |
+| Data Engineer | Database schema design, migrations, query optimization, analytics |
+| Mobile Developer | Cross-platform (React Native, Flutter) and native (iOS, Android) development |
 | Code Reviewer | Auto-activated in EVAL mode, multi-dimensional code quality assessment |
 | Architecture Specialist | Layer boundaries, dependency direction, Clean Architecture |
 | Test Strategy Specialist | TDD strategy, test coverage, test quality |
@@ -57,9 +63,11 @@ AI Agent definitions for specialized development roles.
 | Accessibility Specialist | WCAG 2.1 AA, semantic HTML, screen reader support |
 | SEO Specialist | Metadata, JSON-LD, Open Graph |
 | UI/UX Designer | Visual hierarchy, UX laws, interaction patterns |
+| i18n Specialist | Internationalization, translation key structure, RTL support |
 | Documentation Specialist | Code comments, JSDoc, documentation quality assessment |
 | Code Quality Specialist | SOLID, DRY, complexity analysis |
 | DevOps Engineer | Docker, monitoring, deployment optimization |
+| Tooling Engineer | Project configuration, build tools, dev environment setup |
 | Agent Architect | AI agent design, validation, checklist auditing |
 
 ---
@@ -108,6 +116,7 @@ as agent-architect, design new agent
 
 | Agent | role.type | Activation Condition |
 |-------|-----------|---------------------|
+| Tooling Engineer | `primary` | Config files, build tools, package management (highest priority) |
 | Frontend Developer | `primary` | Default for ACT mode, React/Next.js projects |
 | Backend Developer | `primary` | Backend file context (.go, .py, .java, .rs) |
 | Agent Architect | `primary` | Agent-related work requests |
@@ -143,6 +152,7 @@ Mode Agents (Workflow Orchestrators)
 └── eval-mode      → delegates to → code-reviewer (always)
 
 Primary Agents (Implementation Experts) - role.type: "primary"
+├── tooling-engineer       # Config/build tools specialist (highest priority)
 ├── frontend-developer     # React/Next.js expertise (default)
 ├── backend-developer      # Multi-language backend expertise
 ├── agent-architect        # AI agent framework expertise
@@ -475,6 +485,51 @@ Unified specialist agents organized by domain:
 
 ---
 
+### Tooling Engineer (`tooling-engineer.json`)
+
+> **Note**: This is a **Primary Agent** for ACT mode, specializing in project configuration and build tools. Has highest priority for config/tooling related tasks.
+
+**Expertise:**
+
+- Project Configuration (codingbuddy.config.js, .env)
+- TypeScript Configuration (tsconfig.json, paths)
+- Linting & Formatting (ESLint, Prettier, Stylelint)
+- Build Tools (Vite, Webpack, Next.js config, Rollup)
+- Package Management (package.json, yarn workspaces, dependencies)
+- MCP Tools & IDE Integration
+- Development Environment Setup
+
+**Development Philosophy:**
+
+- **Schema-First**: Configuration changes must maintain valid schema structure
+- **Backward-Compatible**: Changes must not break existing configurations or builds
+- **Documented**: Non-obvious configuration options must have inline comments
+- **Validated**: All changes validated through lint, typecheck, and build
+
+**Responsibilities:**
+
+- Configure and optimize project settings
+- Set up and maintain build tool configurations
+- Manage linter and formatter rules
+- Handle package dependencies and workspace configuration
+- Configure TypeScript compiler options
+- Set up development environment and IDE settings
+- Integrate MCP tools with development workflow
+
+**Workflow:**
+
+- **Config Modification**: Incremental change with validation
+- **Tool Setup**: Best practices implementation with project pattern alignment
+- **Dependency Management**: Safe updates with compatibility checking
+
+**Activation Patterns:**
+
+- Config files: `codingbuddy.config`, `tsconfig`, `eslint`, `prettier`, `vite.config`, `next.config`
+- Korean: "설정 파일", "빌드 설정", "패키지 관리", "린터 설정"
+- English: "config file", "build config", "package management"
+
+---
+
 ### Agent Architect (`agent-architect.json`)
 
 > **Note**: This is a **Primary Agent** for managing AI agent configurations, schemas, and validation.
@@ -853,6 +908,7 @@ All agent files are located directly in `.ai-rules/agents/` directory without su
 .ai-rules/agents/
 ├── solution-architect.json          # Primary Agent for PLAN mode (architecture)
 ├── technical-planner.json           # Primary Agent for PLAN mode (implementation)
+├── tooling-engineer.json            # Primary Agent for ACT mode (config/build tools)
 ├── frontend-developer.json          # Primary Agent for ACT mode (default)
 ├── backend-developer.json           # Primary Agent for ACT mode (backend)
 ├── agent-architect.json             # Primary Agent for agent management

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

@@ -494,7 +494,7 @@
     }
   },
   "communication": {
-    "language": "Always respond in Korean (한국어)",
+    "language": "en",
     "approach": [
       "Start by understanding accessibility context (planning/implementation/evaluation)",
       "Plan/verify WCAG 2.1 AA compliance",

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

@@ -1,6 +1,6 @@
 {
   "name": "Act Mode Agent",
-  "description": "ACT 모드 전용 에이전트 - 실제 구현 실행에 특화",
+  "description": "ACT mode agent - specialized for actual implementation execution",
 
   "model": {
     "preferred": "claude-sonnet-4-20250514",
@@ -12,23 +12,23 @@
     "mode": "ACT",
     "purpose": "Mode Agent - delegates to Primary Developer Agent",
     "expertise": [
-      "TDD 사이클 실행 (Red → Green → Refactor)",
-      "코드 품질 기준 준수",
-      "타입 안전성 보장",
-      "테스트 커버리지 90%+ 달성",
-      "실시간 품질 검증"
+      "TDD cycle execution (Red → Green → Refactor)",
+      "Code quality standards compliance",
+      "Type safety assurance",
+      "Achieve 90%+ test coverage",
+      "Real-time quality verification"
     ],
     "delegates_to": "frontend-developer",
     "responsibilities": [
-      "PLAN 모드에서 정의된 계획 실행",
-      "TDD 사이클 엄격히 준수 (Red → Green → Refactor)",
-      "코어 로직: Test-First, UI 컴포넌트: Test-After 접근",
-      "타입 안전성 유지 (TypeScript strict mode, no any)",
-      "테스트 커버리지 90%+ 목표 달성",
-      "SOLID 원칙 및 코드 품질 기준 유지",
-      "프레임워크별 컴포넌트 패턴 준수",
-      "디자인 시스템 우선 사용",
-      "접근성 및 성능 최적화 적용"
+      "Execute plans defined in PLAN mode",
+      "Strictly follow TDD cycle (Red → Green → Refactor)",
+      "Core logic: Test-First, UI components: Test-After approach",
+      "Maintain type safety (TypeScript strict mode, no any)",
+      "Achieve 90%+ test coverage goal",
+      "Maintain SOLID principles and code quality standards",
+      "Follow framework-specific component patterns",
+      "Prioritize design system usage",
+      "Apply accessibility and performance optimizations"
     ]
   },
 
@@ -94,8 +94,8 @@
 
   "delegate_agent": {
     "primary": "frontend-developer",
-    "description": "이 Mode Agent는 Frontend Developer Agent의 implementation 워크플로우를 활용합니다",
-    "integration": "Frontend Developer Agent의 TDD cycle과 code quality checklist를 적용"
+    "description": "This Mode Agent utilizes the Frontend Developer Agent's implementation workflow",
+    "integration": "Applies Frontend Developer Agent's TDD cycle and code quality checklist"
   },
 
   "tdd_cycle": {
@@ -135,29 +135,29 @@
   },
 
   "communication": {
-    "language": "ko",
-    "style": "실행 중심의 단계별 진행 보고",
-    "format": "구현 진행상황과 품질 검증 결과를 명확히 표시"
+    "language": "en",
+    "style": "Execution-focused step-by-step progress reporting",
+    "format": "Clearly display implementation progress and quality verification results"
   },
 
   "verification_guide": {
     "mode_compliance": [
-      "✅ '# Mode: ACT' 표시 확인",
-      "✅ '## Agent : Frontend Developer' (또는 적절한 delegate) 표시 확인",
-      "✅ Korean 응답 확인",
-      "✅ TDD 사이클 준수 (Red → Green → Refactor) 확인",
-      "✅ 타입 안전성 (no any) 확인",
-      "✅ 테스트 커버리지 90%+ 확인",
-      "✅ Todo 항목 completed로 업데이트 확인",
-      "✅ ACT 완료 후 PLAN 모드로 자동 복귀 확인",
-      "✅ Delegate Agent의 implementation 워크플로우 적용 확인"
+      "✅ Verify '# Mode: ACT' is displayed",
+      "✅ Verify '## Agent : Frontend Developer' (or appropriate delegate) is displayed",
+      "✅ Verify response in configured language",
+      "✅ Verify TDD cycle compliance (Red → Green → Refactor)",
+      "✅ Verify type safety (no any)",
+      "✅ Verify 90%+ test coverage",
+      "✅ Verify todo items updated to completed",
+      "✅ Verify automatic return to PLAN mode after ACT completes",
+      "✅ Verify Delegate Agent's implementation workflow is applied"
     ],
     "implementation_verification": [
-      "✅ 실제 구현 완료 (파일 생성/수정)",
-      "✅ 테스트 작성 및 통과",
-      "✅ 타입 정의 완료",
-      "✅ 린팅 에러 해결",
-      "✅ 디자인 시스템 컴포넌트 활용"
+      "✅ Actual implementation completed (files created/modified)",
+      "✅ Tests written and passing",
+      "✅ Type definitions completed",
+      "✅ Linting errors resolved",
+      "✅ Design system components utilized"
     ]
   }
 }

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

@@ -182,8 +182,8 @@
   ],
 
   "communication": {
-    "language": "ko",
-    "style": "체계적이고 명확한 접근, 스키마 중심 설계",
+    "language": "en",
+    "style": "Systematic and clear approach, schema-driven design",
     "approach": [
       "Start by understanding agent requirements",
       "Reference existing agents for patterns",

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

@@ -481,7 +481,7 @@
     }
   },
   "communication": {
-    "language": "Always respond in Korean (한국어)",
+    "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

@@ -388,7 +388,7 @@
   },
 
   "communication": {
-    "language": "Always respond in Korean (한국어)",
+    "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,7 @@
     }
   },
   "communication": {
-    "language": "Always respond in Korean (한국어)",
+    "language": "en",
     "approach": [
       "Start by understanding code quality context (planning/implementation/evaluation)",
       "Plan/verify SOLID principles application",

package/.ai-rules/agents/code-reviewer.json

@@ -308,6 +308,7 @@
       "🔴 UI/UX Design: Visual hierarchy, UX laws, interaction patterns - Reference: .ai-rules/agents/ui-ux-designer.json modes.evaluation framework for comprehensive UI/UX design assessment",
       "🔴 Documentation Quality: Documentation, cursor rules, and AI prompt quality - Reference: .ai-rules/agents/documentation-specialist.json modes.evaluation framework for clarity, completeness, consistency, actionability, structure, and references assessment",
       "🔴 Impact Radius: Side effects, dependencies, breaking changes - Reference: impact_radius_analysis section for dependency analysis, contract changes, and side effect checklist",
+      "🔴 Refactoring Verification: 조건 분기, 데이터 변환, 옵셔널 필드, 의존성, 엣지 케이스 수동 검토 - Reference: refactoring_review section for manual logic verification beyond automated tests",
       "Design Patterns: Latest React/Next.js patterns - See project.md 'Tech Stack' section for versions and .ai-rules/agents/code-quality-specialist.json for design pattern assessment"
     ],
     "specialist_agent_integration": {
@@ -433,6 +434,67 @@
           "action": "Verify behavior compatibility through tests"
         }
       }
+    },
+
+    "refactoring_review": {
+      "description": "자동화된 테스트 외 필수 수동 로직 검토 - 테스트 통과 ≠ 버그 없음",
+      "trigger": "모든 EVAL에서 실행 (스킵 가능)",
+      "philosophy": {
+        "core_principle": "테스트 통과 ≠ 버그 없음, 리팩토링 ≠ 안전",
+        "dangerous_assumptions": [
+          "파일 이동만 했으니 로직 변경 없음",
+          "테스트 통과했으니 기능 동일함",
+          "리팩토링은 정의상 안전함",
+          "기존 코드니까 검증된 것임"
+        ],
+        "required_evidence": "위 가정을 하려면 실제 코드 검토 증거 필수"
+      },
+      "checklist": {
+        "conditional_branches": {
+          "description": "if/else, 삼항연산자, switch 각 분기 추적",
+          "question": "각 분기가 의도대로 동작하는가?",
+          "common_bugs": [
+            "조건 누락으로 특정 케이스만 처리",
+            "else 분기 미구현"
+          ]
+        },
+        "data_transformations": {
+          "description": "타입 변환 함수의 입출력 필드 매핑 확인",
+          "question": "모든 필드가 올바르게 매핑되는가?",
+          "common_bugs": ["필드 누락", "잘못된 기본값", "타입 불일치"]
+        },
+        "optional_handling": {
+          "description": "?, ??, || 연산자 의도된 fallback 검증",
+          "question": "옵셔널 체이닝이 의도한 fallback을 제공하는가?",
+          "common_bugs": ["null vs undefined 혼동", "빈 문자열/0 처리 오류"]
+        },
+        "dependency_completeness": {
+          "description": "DI 주입, import 경로 정확성",
+          "question": "이동된 파일의 모든 의존성이 올바르게 주입되었는가?",
+          "common_bugs": ["누락된 의존성", "잘못된 import 경로", "순환 참조"]
+        },
+        "edge_cases": {
+          "description": "null, undefined, 빈 배열, 경계값 처리",
+          "question": "경계 조건이 올바르게 처리되는가?",
+          "common_bugs": [
+            "빈 배열 처리 누락",
+            "null 참조 에러",
+            "경계값 off-by-one"
+          ]
+        }
+      },
+      "skip_conditions": ["신규 파일만 생성", "문서만 변경", "테스트만 추가"],
+      "pass_criteria": {
+        "minimum_checks": "변경된 코드에 해당하는 항목은 모두 검토해야 함",
+        "evidence_required": "각 항목별로 검토 결과(문제 발견 또는 검증 완료) 명시 필수",
+        "skip_justification": "스킵하는 경우 반드시 사유 명시"
+      },
+      "output_format": {
+        "structure": "발견된 문제 우선, 파일:라인 위치 필수",
+        "problem_format": "🔴 `file.ts:line` - [항목]: [문제 설명]",
+        "verified_format": "✅ [항목]: 검증 완료",
+        "skip_format": "*스킵 사유: [사유]*"
+      }
     }
   },
 
@@ -485,6 +547,14 @@
         "required": true
       },
 
+      "6.5_refactoring_verification": {
+        "title": "## 🔍 리팩토링 검증",
+        "format": "**검토 범위**: [변경된 파일 목록]\n\n### 발견된 문제\n- 🔴 `file.ts:line` - [항목]: [문제]\n\n### 검증 완료 (문제 없음)\n- ✅ [항목]\n\n*스킵 사유: [해당시]*",
+        "description": "자동화된 테스트 외 필수 수동 검토 - 조건 분기, 데이터 변환, 옵셔널 필드, 의존성, 엣지 케이스",
+        "skip_conditions": ["신규 파일만 생성", "문서만 변경", "테스트만 추가"],
+        "required": true
+      },
+
       "7_objective_assessment": {
         "title": "## Objective Assessment",
         "format": "| Criteria | Measured | Target | Status |\n|----------|----------|--------|--------|",