codingbuddy-rules 4.4.0 → 5.0.0

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

@@ -30,9 +30,9 @@ End users access rules **only through MCP tools**. No local rule files needed.
 }
 ```
 
-> **Important:** Antigravity의 `roots/list` MCP capability 지원 여부는 미확인입니다.
-> `CODINGBUDDY_PROJECT_ROOT` 없이는 서버가 프로젝트의 `codingbuddy.config.json`을 찾지 못하여
-> `language` 등 설정이 기본값으로 동작합니다. 항상 이 환경변수를 프로젝트의 절대 경로로 설정하세요.
+> **Important:** Whether Antigravity supports the `roots/list` MCP capability has not been confirmed.
+> Without `CODINGBUDDY_PROJECT_ROOT`, the server cannot locate your project's `codingbuddy.config.json`,
+> causing settings such as `language` to use default values. Always set this environment variable to your project's absolute path.
 
 Optional: Create `.antigravity/rules/instructions.md` for basic integration:
 
@@ -567,7 +567,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 | Language | Keyword |
 |----------|---------|
 | English | `AUTO` |
-| Korean | `자동` |
+| Korean | `AUTO` |
 | Japanese | `自動` |
 | Chinese | `自动` |
 | Spanish | `AUTOMÁTICO` |
@@ -579,7 +579,7 @@ AUTO implement user authentication feature
 ```
 
 ```
-자동 사용자 인증 기능 구현해줘
+AUTO implement user authentication feature
 ```
 
 When AUTO keyword is detected, Antigravity calls `parse_mode` MCP tool which returns AUTO mode instructions.
@@ -626,7 +626,7 @@ task_boundary(
 )
 ```
 
-> **Antigravity limitation:** AUTO mode에는 강제 루프 메커니즘이 없습니다. 자세한 내용은 [Known Limitations](#known-limitations)를 참조하세요.
+> **Antigravity limitation:** AUTO mode has no enforcement loop mechanism. See [Known Limitations](#known-limitations) for details.
 
 ## Context Document Management
 

package/.ai-rules/adapters/claude-code.md

@@ -191,8 +191,8 @@ Use `recommend_skills` MCP tool to get skill recommendations based on user promp
 recommend_skills({ prompt: "There is a bug in the login" })
 // => recommends: systematic-debugging
 
-recommend_skills({ prompt: "로그인에 버그가 있어" })
-// => recommends: systematic-debugging (Korean support)
+recommend_skills({ prompt: "There is a bug in the login" })
+// => recommends: systematic-debugging (multi-language support)
 
 recommend_skills({ prompt: "Build a dashboard component" })
 // => recommends: frontend-design
@@ -523,6 +523,109 @@ Each workflow mode activates different specialist agents:
 
 **Important:** Specialists from one mode do NOT carry over to the next mode. Each mode has its own recommended specialist set.
 
+### Auto-Dispatch Enforcement
+
+When `parse_mode` returns `dispatch="auto"` or `dispatchReady` with specialist agents, dispatching is **mandatory** — not optional.
+
+**Rule:** Every listed specialist MUST be dispatched. Skipping any specialist is a protocol violation.
+
+#### Teams-Based Specialist Dispatch (Preferred)
+
+Teams are preferred over the Agent tool for specialist dispatch because they enable structured coordination and message-based reporting:
+
+```
+1. TeamCreate({ team_name: "<task>-specialists" })
+2. Spawn specialists as teammates:
+   Agent({ team_name, name: "security-specialist", subagent_type: "general-purpose", prompt: ... })
+   Agent({ team_name, name: "code-quality-specialist", subagent_type: "general-purpose", prompt: ... })
+3. Create and assign tasks:
+   TaskCreate({ subject: "Security review of auth module" })
+   TaskUpdate({ taskId, owner: "security-specialist" })
+4. Specialists work autonomously, report via SendMessage:
+   SendMessage({ to: "team-lead", message: "## Security Findings\n- ...", summary: "Security review done" })
+5. Team lead collects all findings
+6. Shutdown: SendMessage({ to: "security-specialist", message: { type: "shutdown_request" } })
+```
+
+#### SendMessage-Based Reporting
+
+Specialists report findings through `SendMessage` to the team lead. This enables:
+- Structured collection of all specialist outputs
+- Consolidated summary for the user
+- Clear audit trail of what each specialist found
+
+**Report format:**
+```markdown
+## [Specialist Name] Findings
+
+### Critical
+- [finding]
+
+### High
+- [finding]
+
+### Medium
+- [finding]
+
+### Recommendations
+- [recommendation]
+```
+
+#### Fallback: Agent Tool
+
+If Teams-based dispatch fails, fall back to the Agent tool:
+- Use `run_in_background: true` for each specialist
+- Collect results via `TaskOutput`
+- Document the fallback reason in your response
+
+#### Red Flags
+
+| Thought | Reality |
+|---------|---------|
+| "I can handle this analysis myself" | Specialists have domain expertise. Dispatch them. |
+| "It's just a small change" | dispatch="auto" means the system determined specialists are needed. |
+| "I'll save time by skipping" | Skipping causes missed issues that cost more later. |
+| "I'll dispatch later" | Dispatch IMMEDIATELY when dispatch="auto" is returned. |
+
+### Execution Strategy Selection (MANDATORY)
+
+When `parse_mode` returns `availableStrategies`:
+
+1. **Check `availableStrategies`** in the response
+2. **If both strategies available** (`["subagent", "taskmaestro"]`), ask user with AskUserQuestion:
+   - Option A: "SubAgent (background agents, fast)" (Recommended)
+   - Option B: "TaskMaestro (tmux parallel panes, visual monitoring)"
+3. **If only `["subagent"]`** and `taskmaestroInstallHint` present:
+   - Ask: "TaskMaestro is not installed. Would you like to install it for tmux-based parallel execution?"
+   - Yes → invoke `/taskmaestro` skill to guide installation, then re-check
+   - No → proceed with subagent
+4. **Call `dispatch_agents`** with chosen `executionStrategy` parameter:
+   - `dispatch_agents({ mode, specialists, executionStrategy: "subagent" })` — existing Agent tool flow
+   - `dispatch_agents({ mode, specialists, executionStrategy: "taskmaestro" })` — returns tmux assignments
+5. **Execute** based on strategy:
+   - **subagent**: Use `dispatchParams` with Agent tool (`run_in_background: true`)
+   - **taskmaestro**: Follow `executionHint` — start panes, assign prompts, monitor, collect results
+
+### TaskMaestro Execution Flow
+
+When `executionStrategy: "taskmaestro"` is chosen, `dispatch_agents` returns:
+
+```json
+{
+  "taskmaestro": {
+    "sessionName": "eval-specialists",
+    "paneCount": 5,
+    "assignments": [
+      { "name": "security-specialist", "displayName": "Security Specialist", "prompt": "..." },
+      { "name": "performance-specialist", "displayName": "Performance Specialist", "prompt": "..." }
+    ]
+  },
+  "executionHint": "1. /taskmaestro start --panes 5\n2. ..."
+}
+```
+
+Execute by following the `executionHint` commands sequentially.
+
 ## PR All-in-One Skill
 
 Unified commit and PR workflow that:
@@ -582,7 +685,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 | Language | Keyword |
 |----------|---------|
 | English | `AUTO` |
-| Korean | `자동` |
+| Korean | `AUTO` |
 | Japanese | `自動` |
 | Chinese | `自动` |
 | Spanish | `AUTOMATICO` |
@@ -594,7 +697,7 @@ AUTO implement user authentication with JWT tokens
 ```
 
 ```
-자동 사용자 인증 기능을 JWT로 구현해줘
+AUTO implement user authentication with JWT
 ```
 
 ### Expected Behavior

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

@@ -30,10 +30,10 @@ End users access rules **only through MCP tools**. No local rule files needed.
 }
 ```
 
-> **Important:** Codex(GitHub Copilot)의 `roots/list` MCP capability 지원 여부는 미확인입니다.
-> `CODINGBUDDY_PROJECT_ROOT` 없이는 서버가 프로젝트의 `codingbuddy.config.json`을 찾지 못하여
-> `language` 등 설정이 기본값으로 동작합니다. 항상 이 환경변수를 프로젝트의 절대 경로로 설정하세요.
-> Codex가 `${workspaceFolder}` 변수 확장을 지원하는 경우, 절대 경로 대신 사용할 수 있습니다.
+> **Important:** Whether Codex (GitHub Copilot) supports the `roots/list` MCP capability has not been confirmed.
+> Without `CODINGBUDDY_PROJECT_ROOT`, the server cannot locate your project's `codingbuddy.config.json`,
+> causing settings such as `language` to use default values. Always set this environment variable to your project's absolute path.
+> If Codex supports `${workspaceFolder}` variable expansion, you can use it instead of an absolute path.
 
 ### Monorepo Contributors
 
@@ -599,7 +599,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 | Language | Keyword |
 |----------|---------|
 | English | `AUTO` |
-| Korean | `자동` |
+| Korean | `AUTO` |
 | Japanese | `自動` |
 | Chinese | `自动` |
 | Spanish | `AUTOMATICO` |

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

@@ -403,7 +403,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 | Language | Keyword |
 |----------|---------|
 | English | `AUTO` |
-| Korean | `자동` |
+| Korean | `AUTO` |
 | Japanese | `自動` |
 | Chinese | `自动` |
 | Spanish | `AUTOMATICO` |
@@ -415,7 +415,7 @@ AUTO implement user authentication feature
 ```
 
 ```
-자동 사용자 인증 기능 구현해줘
+AUTO implement user authentication feature
 ```
 
 When AUTO keyword is detected, Cursor calls `parse_mode` MCP tool which returns AUTO mode instructions.

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

@@ -30,9 +30,9 @@ End users access rules **only through MCP tools**. No local rule files needed.
 }
 ```
 
-> **Important:** Kiro의 `roots/list` MCP capability 지원 여부는 미확인입니다.
-> `CODINGBUDDY_PROJECT_ROOT` 없이는 서버가 프로젝트의 `codingbuddy.config.json`을 찾지 못하여
-> `language` 등 설정이 기본값으로 동작합니다. 항상 이 환경변수를 프로젝트의 절대 경로로 설정하세요.
+> **Important:** Whether Kiro supports the `roots/list` MCP capability has not been confirmed.
+> Without `CODINGBUDDY_PROJECT_ROOT`, the server cannot locate your project's `codingbuddy.config.json`,
+> causing settings such as `language` to use default values. Always set this environment variable to your project's absolute path.
 
 Optional: Create `.kiro/rules/guidelines.md` for basic integration:
 
@@ -85,8 +85,8 @@ MCP server configuration for codingbuddy tools:
 }
 ```
 
-> **Note:** Kiro는 `${VARIABLE}` 문법으로 환경변수 확장을 지원합니다.
-> `${workspaceFolder}` 가 지원되는 경우 절대 경로 대신 사용할 수 있습니다.
+> **Note:** Kiro supports environment variable expansion using the `${VARIABLE}` syntax.
+> If `${workspaceFolder}` is supported, you can use it instead of an absolute path.
 
 **MCP configuration paths:**
 - **Project-level**: `.kiro/settings/mcp.json`
@@ -526,7 +526,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 | Language | Keyword |
 |----------|---------|
 | English | `AUTO` |
-| Korean | `자동` |
+| Korean | `AUTO` |
 | Japanese | `自動` |
 | Chinese | `自动` |
 | Spanish | `AUTOMÁTICO` |
@@ -538,7 +538,7 @@ AUTO implement user authentication feature
 ```
 
 ```
-자동 사용자 인증 기능 구현해줘
+AUTO implement user authentication feature
 ```
 
 When AUTO keyword is detected, Kiro calls `parse_mode` MCP tool which returns AUTO mode instructions.
@@ -571,7 +571,7 @@ module.exports = {
 - Bug fixes needing comprehensive testing
 - Code quality improvements with measurable criteria
 
-> **Kiro limitation:** AUTO mode에는 강제 루프 메커니즘이 없습니다. 자세한 내용은 [Known Limitations](#known-limitations)를 참조하세요.
+> **Kiro limitation:** AUTO mode has no enforcement loop mechanism. See [Known Limitations](#known-limitations) for details.
 
 ## Context Document Management
 

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

@@ -184,9 +184,9 @@ Add to your MCP configuration:
 }
 ```
 
-> **Important:** OpenCode/Crush의 `roots/list` MCP capability 지원 여부는 미확인입니다.
-> `CODINGBUDDY_PROJECT_ROOT` 없이는 서버가 프로젝트의 `codingbuddy.config.json`을 찾지 못하여
-> `language` 등 설정이 기본값으로 동작합니다. 항상 이 환경변수를 프로젝트의 절대 경로로 설정하세요.
+> **Important:** Whether OpenCode/Crush supports the `roots/list` MCP capability has not been confirmed.
+> Without `CODINGBUDDY_PROJECT_ROOT`, the server cannot locate your project's `codingbuddy.config.json`,
+> causing settings such as `language` to use default values. Always set this environment variable to your project's absolute path.
 
 #### Available MCP Tools
 
@@ -526,9 +526,9 @@ npx codingbuddy@latest mcp
 
 **4. Project Config Not Detected**
 ```bash
-# CODINGBUDDY_PROJECT_ROOT가 MCP env에 설정되어 있는지 확인
-# 이 환경변수 없이는 codingbuddy.config.json을 찾지 못합니다
-# .opencode.json 또는 crush.json의 mcp 섹션에 추가:
+# Verify that CODINGBUDDY_PROJECT_ROOT is set in MCP env
+# Without this environment variable, codingbuddy.config.json cannot be found
+# Add to the mcp section of .opencode.json or crush.json:
 "env": {
   "CODINGBUDDY_PROJECT_ROOT": "/absolute/path/to/your/project"
 }
@@ -752,7 +752,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 | Language | Keyword |
 |----------|---------|
 | English | `AUTO` |
-| Korean | `자동` |
+| Korean | `AUTO` |
 | Japanese | `自動` |
 | Chinese | `自动` |
 | Spanish | `AUTOMÁTICO` |

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

@@ -178,7 +178,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 | Language | Keyword |
 |----------|---------|
 | English | `AUTO` |
-| Korean | `자동` |
+| Korean | `AUTO` |
 | Japanese | `自動` |
 | Chinese | `自动` |
 | Spanish | `AUTOMATICO` |
@@ -186,7 +186,7 @@ Use the `AUTO` keyword (or localized versions) at the start of your message:
 ### Example Usage
 
 ```
-AUTO 새로운 Lambda 함수 만들어줘
+AUTO create a new Lambda function
 ```
 
 ### Workflow

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

@@ -165,9 +165,9 @@ Primary Agent is dynamically determined based on the following priority:
 
 **Korean:**
 ```
-backend-developer로 작업해      # "Work with backend-developer" (~로 작업해 = "work with ~")
-agent-architect으로 해줘        # "Do it with agent-architect" (~으로 해줘 = "do with ~")
-devops-engineer로 개발해        # "Develop with devops-engineer" (~로 개발해 = "develop with ~")
+backend-developer work with      # "Work with backend-developer"
+agent-architect do with          # "Do it with agent-architect"
+devops-engineer develop with     # "Develop with devops-engineer"
 ```
 
 **English:**
@@ -202,6 +202,7 @@ as agent-architect, design new agent
 | Data Scientist | `primary` | EDA, ML modeling, Jupyter notebooks, data analysis and visualization |
 | Systems Developer | `primary` | Rust/C/C++, FFI bindings, embedded systems, low-level performance optimization |
 | Software Engineer | `primary` | Universal fallback — any language, any domain, when no specific agent matches |
+| Parallel Orchestrator | `primary` | Parallel issue execution, taskMaestro orchestration, Wave planning |
 
 ### EVAL Mode
 
@@ -637,7 +638,7 @@ Unified specialist agents organized by domain:
 **Activation Patterns:**
 
 - Files: `*.tf`, `*.tfvars`, `Chart.yaml`, `kustomization.yaml`, `Pulumi.yaml`, `argocd/`, `flux-system/`
-- Korean: "인프라 코드", "쿠버네티스", "테라폼", "비용 최적화", "재해 복구"
+- Korean: "infrastructure code", "Kubernetes", "Terraform", "cost optimization", "disaster recovery"
 - English: "terraform", "kubernetes", "k8s", "helm", "pulumi", "gitops", "argocd", "infrastructure as code"
 
 **Auto-Activation:** Supported via MCP server. Platform Engineer is automatically selected when prompts contain IaC/Kubernetes keywords or when working with infrastructure files.
@@ -684,7 +685,7 @@ Unified specialist agents organized by domain:
 **Activation Patterns:**
 
 - Config files: `codingbuddy.config`, `tsconfig`, `eslint`, `prettier`, `vite.config`, `next.config`
-- Korean: "설정 파일", "빌드 설정", "패키지 관리", "린터 설정"
+- Korean: "config file", "build config", "package management", "linter config"
 - English: "config file", "build config", "package management"
 
 ---
@@ -767,7 +768,7 @@ Unified specialist agents organized by domain:
 
 **Activation Patterns:**
 
-- Korean: "LLM 통합", "RAG 구현", "프롬프트 엔지니어링", "AI 안전"
+- Korean: "LLM integration", "RAG implementation", "prompt engineering", "AI safety"
 - English: "LLM integration", "RAG implementation", "prompt engineering", "AI safety"
 
 ---
@@ -812,7 +813,7 @@ Unified specialist agents organized by domain:
 **Activation Patterns:**
 
 - Files: `*.ipynb`, `*eda*.py`, `*analysis*.py`, `*model*.py`, `notebooks/`
-- Korean: "데이터 분석", "탐색적 분석", "EDA", "시각화", "회귀", "분류", "주피터"
+- Korean: "data analysis", "exploratory analysis", "EDA", "visualization", "regression", "classification", "Jupyter"
 - English: "EDA", "exploratory", "data analysis", "visualization", "regression", "classification", "pandas", "scikit-learn", "jupyter"
 
 ---
@@ -860,7 +861,7 @@ Unified specialist agents organized by domain:
 
 **Activation Patterns:**
 
-- Korean: "Rust로 구현", "C++ 최적화", "FFI 바인딩", "메모리 관리", "임베디드 개발", "WASM 구현"
+- Korean: "Rust implementation", "C++ optimization", "FFI binding", "memory management", "embedded development", "WASM implementation"
 - English: "rust implementation", "FFI binding", "memory management", "embedded", "WASM", "low-level", "systems programming"
 
 ---
@@ -957,7 +958,7 @@ Software Engineer is the **fallback of last resort** — it has no intent patter
 **Activation Patterns:**
 
 - Files: API clients, webhook handlers, OAuth implementations, external service integrations
-- Korean: "외부 서비스 연동", "웹훅", "API 통합", "서킷 브레이커"
+- Korean: "external service integration", "webhook", "API integration", "circuit breaker"
 - English: "external API", "webhook", "integration", "circuit breaker", "third-party service"
 
 **Auto-Activation:** Supported via MCP server. Integration Specialist is automatically selected when prompts contain external service integration keywords or when working with API client/webhook files.
@@ -1013,7 +1014,7 @@ Software Engineer is the **fallback of last resort** — it has no intent patter
 **Activation Patterns:**
 
 - Files: `**/events/**`, `**/kafka/**`, `**/rabbitmq/**`, `**/sqs/**`, `**/eventgrid/**`, `**/pubsub/**`, `**/eventbridge/**`, `**/*producer*.ts`, `**/*consumer*.ts`, `**/*saga*.ts`, `**/*event-store*.ts`, `**/websocket/**`
-- Korean: "이벤트 아키텍처", "메시지 큐", "카프카", "사가 패턴", "이벤트 소싱"
+- Korean: "event architecture", "message queue", "Kafka", "saga pattern", "event sourcing"
 - English: "event-driven", "message queue", "kafka", "rabbitmq", "saga pattern", "event sourcing", "CQRS", "websocket"
 
 **Auto-Activation:** Supported via MCP server. Event Architecture Specialist is automatically selected when prompts contain event-driven architecture keywords or when working with message queue/event sourcing files.
@@ -1079,7 +1080,7 @@ Software Engineer is the **fallback of last resort** — it has no intent patter
 **Activation Patterns:**
 
 - Keywords: "observability", "distributed tracing", "OpenTelemetry", "SLI", "SLO", "error budget", "structured logging", "Prometheus", "Grafana", "Jaeger"
-- Korean: "관측 가능성", "분산 추적", "SLI/SLO", "에러 버짓"
+- Korean: "observability", "distributed tracing", "SLI/SLO", "error budget"
 - English: "observability", "distributed tracing", "SLI/SLO", "error budget", "OpenTelemetry"
 
 **Auto-Activation:** Supported via MCP server. Observability Specialist is automatically selected when prompts contain observability-related keywords or when working with tracing/monitoring files.
@@ -1156,7 +1157,7 @@ Software Engineer is the **fallback of last resort** — it has no intent patter
 **Activation Patterns:**
 
 - Keywords: "migration", "migrate", "legacy", "upgrade", "strangler fig", "rollback", "cutover", "deprecation", "backward compatibility"
-- Korean: "마이그레이션", "이전", "레거시", "업그레이드", "롤백", "호환성", "전환"
+- Korean: "migration", "transfer", "legacy", "upgrade", "rollback", "compatibility", "transition"
 - English: "migration", "legacy modernization", "framework upgrade", "zero-downtime", "api versioning"
 
 **Auto-Activation:** Supported via MCP server. Migration Specialist is automatically selected when prompts contain migration-related keywords or when working with migration/upgrade files.
@@ -1631,6 +1632,8 @@ Some specialist agents define **delegation rules** to clarify when work should b
 Each agent JSON contains:
 
 - **name**: Agent identifier
+- **description**: Brief description of the agent
+- **color**: Unique hex color code for visual identification (e.g., `#61DAFB`)
 - **role**: Title and expertise areas
 - **context_files**: Rules to reference
 - **modes**: Planning, implementation, and evaluation frameworks (for unified specialists)
@@ -1642,6 +1645,52 @@ Each agent JSON contains:
 - **design_system**: UI component guidelines
 - **communication**: Response language and style
 
+### Color Reference
+
+Each agent has a unique `color` field (hex code) for visual identification in UIs and dashboards.
+
+| Agent | Color | Hex |
+|-------|-------|-----|
+| **Mode Agents** | | |
+| Plan Mode | ![#6C8EBF](https://via.placeholder.com/12/6C8EBF/6C8EBF.png) Steel Blue | `#6C8EBF` |
+| Act Mode | ![#82B366](https://via.placeholder.com/12/82B366/82B366.png) Sage Green | `#82B366` |
+| Eval Mode | ![#D4A843](https://via.placeholder.com/12/D4A843/D4A843.png) Golden | `#D4A843` |
+| Auto Mode | ![#B85450](https://via.placeholder.com/12/B85450/B85450.png) Rust Red | `#B85450` |
+| **Primary Agents** | | |
+| Solution Architect | ![#4A90D9](https://via.placeholder.com/12/4A90D9/4A90D9.png) Royal Blue | `#4A90D9` |
+| Technical Planner | ![#7B68EE](https://via.placeholder.com/12/7B68EE/7B68EE.png) Slate Blue | `#7B68EE` |
+| Frontend Developer | ![#61DAFB](https://via.placeholder.com/12/61DAFB/61DAFB.png) React Cyan | `#61DAFB` |
+| Backend Developer | ![#68A063](https://via.placeholder.com/12/68A063/68A063.png) Node Green | `#68A063` |
+| Mobile Developer | ![#A4C639](https://via.placeholder.com/12/A4C639/A4C639.png) Android Green | `#A4C639` |
+| Data Engineer | ![#E97451](https://via.placeholder.com/12/E97451/E97451.png) Burnt Sienna | `#E97451` |
+| Agent Architect | ![#9B59B6](https://via.placeholder.com/12/9B59B6/9B59B6.png) Amethyst | `#9B59B6` |
+| Platform Engineer | ![#3498DB](https://via.placeholder.com/12/3498DB/3498DB.png) Dodger Blue | `#3498DB` |
+| Tooling Engineer | ![#95A5A6](https://via.placeholder.com/12/95A5A6/95A5A6.png) Concrete | `#95A5A6` |
+| AI/ML Engineer | ![#FF6F61](https://via.placeholder.com/12/FF6F61/FF6F61.png) Coral | `#FF6F61` |
+| DevOps Engineer | ![#2ECC71](https://via.placeholder.com/12/2ECC71/2ECC71.png) Emerald | `#2ECC71` |
+| Test Engineer | ![#F39C12](https://via.placeholder.com/12/F39C12/F39C12.png) Orange | `#F39C12` |
+| Security Engineer | ![#E74C3C](https://via.placeholder.com/12/E74C3C/E74C3C.png) Alizarin | `#E74C3C` |
+| Software Engineer | ![#1ABC9C](https://via.placeholder.com/12/1ABC9C/1ABC9C.png) Turquoise | `#1ABC9C` |
+| Data Scientist | ![#8E44AD](https://via.placeholder.com/12/8E44AD/8E44AD.png) Wisteria | `#8E44AD` |
+| Systems Developer | ![#D35400](https://via.placeholder.com/12/D35400/D35400.png) Pumpkin | `#D35400` |
+| **Domain Specialists** | | |
+| Architecture | ![#2C3E80](https://via.placeholder.com/12/2C3E80/2C3E80.png) Navy | `#2C3E80` |
+| Test Strategy | ![#F1C40F](https://via.placeholder.com/12/F1C40F/F1C40F.png) Sunflower | `#F1C40F` |
+| Performance | ![#E67E22](https://via.placeholder.com/12/E67E22/E67E22.png) Carrot | `#E67E22` |
+| Security | ![#C0392B](https://via.placeholder.com/12/C0392B/C0392B.png) Pomegranate | `#C0392B` |
+| Accessibility | ![#27AE60](https://via.placeholder.com/12/27AE60/27AE60.png) Nephritis | `#27AE60` |
+| SEO | ![#16A085](https://via.placeholder.com/12/16A085/16A085.png) Green Sea | `#16A085` |
+| UI/UX Designer | ![#E91E63](https://via.placeholder.com/12/E91E63/E91E63.png) Pink | `#E91E63` |
+| Documentation | ![#607D8B](https://via.placeholder.com/12/607D8B/607D8B.png) Blue Gray | `#607D8B` |
+| Integration | ![#00BCD4](https://via.placeholder.com/12/00BCD4/00BCD4.png) Cyan | `#00BCD4` |
+| Event Architecture | ![#FF5722](https://via.placeholder.com/12/FF5722/FF5722.png) Deep Orange | `#FF5722` |
+| Observability | ![#795548](https://via.placeholder.com/12/795548/795548.png) Brown | `#795548` |
+| Migration | ![#FF9800](https://via.placeholder.com/12/FF9800/FF9800.png) Amber | `#FF9800` |
+| i18n | ![#009688](https://via.placeholder.com/12/009688/009688.png) Teal | `#009688` |
+| **Utility Agents** | | |
+| Code Quality | ![#8BC34A](https://via.placeholder.com/12/8BC34A/8BC34A.png) Light Green | `#8BC34A` |
+| Code Reviewer | ![#673AB7](https://via.placeholder.com/12/673AB7/673AB7.png) Deep Purple | `#673AB7` |
+
 ---
 
 ## Adding New Agents
@@ -1667,6 +1716,7 @@ Create a new JSON file following this structure:
 {
   "name": "Agent Name",
   "description": "Brief description",
+  "color": "#HEXCOD",
   "role": {
     "title": "Role Title",
     "expertise": [],
@@ -1723,7 +1773,7 @@ Add a regex pattern to detect specialist-relevant keywords in user prompts:
 // apps/mcp-server/src/keyword/keyword.service.ts
 {
   pattern:
-    /keyword1|keyword2|한국어키워드|english\s*pattern/i,
+    /keyword1|keyword2|korean_keyword|english\s*pattern/i,
   specialist: '{domain}-specialist',
 },
 ```
@@ -1810,8 +1860,8 @@ describe('{domain}-specialist pattern', () => {
   });
 
   it.each([
-    '한국어 키워드 1',
-    '한국어 키워드 2',
+    'Korean keyword 1',
+    'Korean keyword 2',
     // ... more Korean patterns
   ])('detects {domain}-specialist for Korean: %s', async prompt => {
     const result = await service.parseMode(`PLAN ${prompt}`);
@@ -1869,7 +1919,7 @@ When modifying an existing specialist's integration:
 pattern: /existing|keywords/i,
 
 // After
-pattern: /existing|keywords|new_keyword|새키워드/i,
+pattern: /existing|keywords|new_keyword|new_korean_keyword/i,
 ```
 
 #### Adding New File Patterns

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

@@ -1,6 +1,7 @@
 {
   "name": "Accessibility Specialist",
   "description": "Accessibility expert for Planning, Implementation, and Evaluation modes - unified specialist for WCAG 2.1 AA compliance, ARIA attributes, and keyboard navigation",
+  "color": "#27AE60",
   "role": {
     "title": "Accessibility Engineer",
     "expertise": [
@@ -305,7 +306,7 @@
         "auto_activate_conditions": [
           "UI component development or modifications",
           "Form component creation",
-          "User explicitly requests accessibility review (A11Y, 접근성 검토)",
+          "User explicitly requests accessibility review (A11Y, accessibility review)",
           "Code Reviewer identifies accessibility concerns"
         ],
         "mandatory_checklist": {

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

@@ -1,6 +1,7 @@
 {
   "name": "Act Mode Agent",
   "description": "ACT mode agent - specialized for actual implementation execution",
+  "color": "#82B366",
   "role": {
     "title": "Act Mode Agent",
     "mode": "ACT",
@@ -31,7 +32,7 @@
     ".ai-rules/rules/augmented-coding.md"
   ],
   "activation": {
-    "trigger": "🔴 **STRICT**: When user types 'ACT' or equivalent (Korean: 실행, Japanese: 実行, Chinese: 执行, Spanish: ACTUAR)",
+    "trigger": "🔴 **STRICT**: When user types 'ACT' or equivalent (Korean: execute, Japanese: 実行, Chinese: 执行, Spanish: ACTUAR)",
     "rule": "🔴 **STRICT**: ACT MODE request must activate this Agent automatically",
     "mandatory_checklist": {
       "🔴 language": {

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

@@ -1,6 +1,7 @@
 {
   "name": "Agent Architect",
   "description": "Primary Agent for creating, validating, and managing AI agent configurations",
+  "color": "#9B59B6",
   "role": {
     "title": "AI Agent Framework Architect",
     "type": "primary",
@@ -29,19 +30,19 @@
   "activation": {
     "trigger": "When user requests agent-related tasks: create agent, validate agent, audit checklist, manage agents",
     "explicit_patterns": [
-      "에이전트 만들어",
-      "agent 생성",
       "create agent",
-      "새 에이전트",
-      "에이전트 검증",
+      "agent creation",
+      "create agent",
+      "new agent",
+      "validate agent",
       "validate agent",
       "agent validation",
-      "체크리스트 감사",
+      "audit checklist",
       "audit checklist",
       "checklist audit",
-      "에이전트 관리",
       "manage agent",
-      "agent-architect로"
+      "manage agent",
+      "as agent-architect"
     ],
     "mandatory_checklist": {
       "🔴 schema_compliance": {

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

@@ -1,6 +1,7 @@
 {
   "name": "AI/ML Engineer",
   "description": "AI/ML expert for Planning, Implementation, and Evaluation modes - unified specialist for LLM integration, prompt engineering, RAG architecture, AI safety, and testing non-deterministic systems",
+  "color": "#FF6F61",
   "role": {
     "title": "Senior AI/ML Engineer",
     "type": "primary",

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

@@ -1,6 +1,7 @@
 {
   "name": "Architecture Specialist",
   "description": "Architecture expert for Planning, Implementation, and Evaluation modes - unified specialist for layer placement, dependency direction, and type safety",
+  "color": "#2C3E80",
   "role": {
     "title": "Architecture Engineer",
     "expertise": [

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

@@ -1,6 +1,7 @@
 {
   "name": "Auto Mode Agent",
   "description": "AUTO mode agent - autonomous PLAN → ACT → EVAL cycle until quality targets met",
+  "color": "#B85450",
   "role": {
     "title": "Auto Mode Agent",
     "mode": "AUTO",
@@ -20,7 +21,8 @@
       "EVAL phase: Multi-dimensional quality evaluation with anti-sycophancy",
       "Iterate until Critical=0 AND High=0 issues remaining",
       "Maintain context continuity across cycle iterations",
-      "Track iteration count and quality metrics progression"
+      "Track iteration count and quality metrics progression",
+      "Execute all tasks continuously without stopping between steps — only pause for RESULT.json at completion"
     ]
   },
   "context_files": [
@@ -29,7 +31,7 @@
     ".ai-rules/rules/augmented-coding.md"
   ],
   "activation": {
-    "trigger": "🔴 **STRICT**: When user types 'AUTO' or equivalent (Korean: 자동, Japanese: 自動, Chinese: 自动, Spanish: AUTOMÁTICO)",
+    "trigger": "🔴 **STRICT**: When user types 'AUTO' or equivalent (Korean: automatic, Japanese: 自動, Chinese: 自动, Spanish: AUTOMÁTICO)",
     "rule": "🔴 **STRICT**: AUTO MODE request must activate this Agent automatically",
     "mandatory_checklist": {
       "🔴 language": {