codingbuddy-rules 0.0.0-canary.20260106105956.dda0e31 → 0.0.0-canary.20260106124223.476bee6

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

@@ -175,9 +175,11 @@ CodingBuddy uses a layered agent hierarchy for different types of tasks:
 | Mode | Agents | Description |
 |------|--------|-------------|
 | **PLAN** | solution-architect, technical-planner | Design and planning tasks |
-| **ACT** | frontend-developer, backend-developer, devops-engineer, agent-architect | Implementation tasks |
+| **ACT** | tooling-engineer, frontend-developer, backend-developer, devops-engineer, agent-architect | Implementation tasks |
 | **EVAL** | code-reviewer | Code review and evaluation |
 
+> **Note**: `tooling-engineer` has highest priority for config/build tool tasks (tsconfig, eslint, vite.config, package.json, etc.)
+
 ### Tier 2: Specialist Agents
 
 Specialist agents can be invoked by any Primary Agent as needed:
@@ -195,9 +197,34 @@ Specialist agents can be invoked by any Primary Agent as needed:
 ### Agent Resolution
 
 1. **PLAN mode**: Always uses `solution-architect` or `technical-planner` based on prompt analysis
-2. **ACT mode**: Uses recommended agent from PLAN, or falls back to AI analysis
+2. **ACT mode**: Resolution priority:
+   1. Explicit agent request in prompt (e.g., "backend-developer로 작업해")
+   2. `recommended_agent` parameter (from PLAN mode recommendation)
+   3. Tooling pattern matching (config files, build tools → `tooling-engineer`)
+   4. Project configuration (`primaryAgent` setting)
+   5. Context inference (file extension/path)
+   6. Default: `frontend-developer`
 3. **EVAL mode**: Always uses `code-reviewer`
 
+### Using recommended_agent Parameter
+
+When transitioning from PLAN to ACT mode, pass the recommended agent:
+
+```typescript
+// After PLAN mode returns recommended_act_agent
+const planResult = await parse_mode({ prompt: "PLAN design auth API" });
+// planResult.recommended_act_agent = { agentName: "backend-developer", ... }
+
+// Pass to ACT mode for context preservation
+const actResult = await parse_mode({
+  prompt: "ACT implement the API",
+  recommended_agent: planResult.recommended_act_agent.agentName
+});
+// actResult.delegates_to = "backend-developer" (uses the recommendation)
+```
+
+This enables seamless agent context passing across PLAN → ACT workflow transitions.
+
 ## Activation Messages
 
 When agents or skills are activated, CodingBuddy displays activation messages for transparency:

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

@@ -1,151 +1,173 @@
 # Cursor Integration Guide
 
-This guide explains how to use the common AI rules (`.ai-rules/`) in Cursor.
+Guide for using codingbuddy with Cursor.
 
 ## Overview
 
-Cursor continues to use its native `.cursor/` directory structure while referencing the common rules from `.ai-rules/`.
+codingbuddy integrates with Cursor in two ways:
 
-## Integration Method
+1. **AGENTS.md** - Industry standard format compatible with all AI tools
+2. **.cursor/rules/*.mdc** - Cursor-specific optimization (glob-based auto-activation)
 
-### 1. Reference Common Rules
+## Two Usage Contexts
 
-Create `.cursor/rules/imports.mdc` to reference common rules:
+### End Users (Your Project)
 
-```markdown
+End users access rules **only through MCP tools**. No local rule files needed.
+
+```json
+// .cursor/mcp.json
+{
+  "mcpServers": {
+    "codingbuddy": {
+      "command": "npx",
+      "args": ["-y", "codingbuddy"]
+    }
+  }
+}
+```
+
+Optional: Create `.cursor/rules/codingbuddy.mdc` for basic integration:
+
+```yaml
 ---
-description: Common AI Rules Import
+description: codingbuddy integration
 globs:
 alwaysApply: true
 ---
 
-# Common Rules
-
-This project uses shared rules from `.ai-rules/` directory for all AI assistants.
-
-## 📚 Core Rules
-See [../../.ai-rules/rules/core.md](../../.ai-rules/rules/core.md) for:
-- PLAN/ACT/EVAL workflow modes
-- Agent activation rules
-- Communication guidelines
-
-## 🏗️ Project Setup
-See [../../.ai-rules/rules/project.md](../../.ai-rules/rules/project.md) for:
-- Tech stack and dependencies
-- Project structure and architecture
-- Development rules and conventions
-- Domain knowledge and business context
-
-## 🎯 Augmented Coding Principles
-See [../../.ai-rules/rules/augmented-coding.md](../../.ai-rules/rules/augmented-coding.md) for:
-- TDD cycle (Red → Green → Refactor)
-- Code quality standards (SOLID, DRY)
-- Testing best practices
-- Commit discipline
-
-## 🤖 Specialist Agents
-See [../../.ai-rules/agents/README.md](../../.ai-rules/agents/README.md) for available specialist agents:
-- Frontend Developer, Code Reviewer
-- Architecture, Test Strategy, Performance, Security
-- Accessibility, SEO, Design System, Documentation
-- Code Quality, DevOps Engineer
+When PLAN, ACT, EVAL keywords detected → call `parse_mode` MCP tool
 ```
 
-### 2. Keep Cursor-Specific Features
+### Monorepo Contributors
 
-Maintain `.cursor/rules/cursor-specific.mdc` for Cursor-only features:
+Contributors to the codingbuddy repository can use direct file references:
 
-```markdown
+```
+Project Root/
+├── AGENTS.md                    # Cross-platform entry point
+├── .cursor/rules/
+│   ├── imports.mdc              # Common rules (alwaysApply: true)
+│   ├── auto-agent.mdc           # File pattern-based Agent auto-activation
+│   └── custom.mdc               # Personal settings (Git ignored)
+└── packages/rules/.ai-rules/    # Single Source of Truth
+```
+
+## DRY Principle
+
+**Single Source of Truth**: `packages/rules/.ai-rules/`
+
+- All Agent definitions, rules, skills managed only in `.ai-rules/`
+- AGENTS.md and .mdc files act as **pointers only**
+- No duplication, only references
+
+## Configuration Files
+
+### imports.mdc (alwaysApply)
+
+Core rules automatically applied to all conversations:
+
+```yaml
 ---
-description: Cursor-specific configurations
+description: codingbuddy common rules
 globs:
 alwaysApply: true
 ---
 
-# Cursor-Specific Features
+# Core principles only (details in .ai-rules/)
+```
 
-## File Globbing
+### auto-agent.mdc (glob-based)
 
-[Add Cursor-specific glob patterns here]
+Automatically provides appropriate Agent context based on file patterns:
 
-## Agent Tool Integration
+```yaml
+---
+description: Agent auto-activation
+globs:
+  - "**/*.tsx"
+  - "**/*.ts"
+  - "**/*.go"
+alwaysApply: false
+---
 
-[Add Cursor-specific todo_write tool usage]
+# File pattern → Agent mapping table
 ```
 
-## Current Structure
+## Usage
+
+### Mode Keywords
 
 ```
-.cursor/
-├── agents/              # Keep for Cursor compatibility
-├── rules/
-│   ├── core.mdc        # Keep existing (can add reference to .ai-rules)
-│   ├── project.mdc     # Keep existing (can add reference to .ai-rules)
-│   ├── augmented-coding.mdc  # Keep existing
-│   ├── imports.mdc     # NEW: References to .ai-rules
-│   └── cursor-specific.mdc   # NEW: Cursor-only features
-└── config.json         # Cursor configuration
-
-.ai-rules/              # Common rules for all AI tools
-├── rules/
-│   ├── core.md
-│   ├── project.md
-│   └── augmented-coding.md
-├── agents/
-│   └── *.json
-└── adapters/
-    └── cursor.md (this file)
+PLAN Design user authentication feature
 ```
 
-## Usage
+→ `parse_mode` MCP tool is called, loading appropriate Agent and rules
 
-### In Cursor Chat
+### Auto-Activation on File Edit
 
-Reference rules directly:
-```
-@.ai-rules/rules/core.md
-@.ai-rules/agents/frontend-developer.json
+Open `.tsx` file → `auto-agent.mdc` auto-applies → frontend-developer Agent recommended
 
-Create a new feature following our common workflow
-```
+### Specialist Usage
 
-### In Cursor Composer
-
-The `.cursor/rules/imports.mdc` with `alwaysApply: true` will automatically apply common rules to all Composer sessions.
+```
+EVAL Review from security perspective
+```
 
-## Benefits
+→ security-specialist activated
 
-- ✅ Seamless integration with existing Cursor setup
-- ✅ Access to common rules shared across all AI tools
-- ✅ Cursor-specific features (globs, alwaysApply) still work
-- ✅ Easy to update: change `.ai-rules/` once, all tools benefit
+## MCP Tools
 
-## Maintenance
+Available codingbuddy MCP tools in Cursor:
 
-When updating rules:
-1. Update `.ai-rules/rules/*.md` for changes affecting all AI tools
-2. Update `.cursor/rules/*.mdc` only for Cursor-specific changes
-3. Keep both in sync for best experience
+| Tool | Purpose |
+|------|---------|
+| `parse_mode` | Parse mode keywords + load Agent/rules |
+| `get_agent_details` | Get specific Agent details |
+| `get_project_config` | Get project configuration |
+| `recommend_skills` | Recommend skills based on prompt |
+| `prepare_parallel_agents` | Prepare parallel Agent execution |
 
 ## Skills
 
 ### Using Skills in Cursor
 
-Reference skills in your prompts using file inclusion:
+Load skills via file reference (monorepo only):
 
 ```
-@.ai-rules/skills/test-driven-development/SKILL.md
+@packages/rules/.ai-rules/skills/test-driven-development/SKILL.md
 ```
 
-Or manually include skill content in `.cursorrules`.
+For end users, use `recommend_skills` MCP tool instead.
 
 ### Available Skills
 
-- `.ai-rules/skills/brainstorming/SKILL.md`
-- `.ai-rules/skills/test-driven-development/SKILL.md`
-- `.ai-rules/skills/systematic-debugging/SKILL.md`
-- `.ai-rules/skills/writing-plans/SKILL.md`
-- `.ai-rules/skills/executing-plans/SKILL.md`
-- `.ai-rules/skills/subagent-driven-development/SKILL.md`
-- `.ai-rules/skills/dispatching-parallel-agents/SKILL.md`
-- `.ai-rules/skills/frontend-design/SKILL.md`
+- `brainstorming/SKILL.md` - Idea → Design
+- `test-driven-development/SKILL.md` - TDD workflow
+- `systematic-debugging/SKILL.md` - Systematic debugging
+- `writing-plans/SKILL.md` - Implementation plan writing
+- `executing-plans/SKILL.md` - Plan execution
+- `subagent-driven-development/SKILL.md` - Subagent development
+- `dispatching-parallel-agents/SKILL.md` - Parallel Agent dispatch
+- `frontend-design/SKILL.md` - Frontend design
+
+## AGENTS.md
+
+Industry standard format compatible with all AI tools (Cursor, Claude Code, Codex, etc.):
+
+```markdown
+# AGENTS.md
+
+This project uses codingbuddy MCP server to manage AI Agents.
+
+## Quick Start
+...
+```
+
+See `AGENTS.md` in project root for details.
+
+## Reference
+
+- [AGENTS.md Official Spec](https://agents.md)
+- [Cursor Rules Documentation](https://cursor.com/docs/context/rules)
+- [codingbuddy MCP API](../../docs/api.md)

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

@@ -39,6 +39,7 @@ AI Agent definitions for specialized development roles.
 | **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
@@ -60,6 +61,7 @@ AI Agent definitions for specialized development roles.
 | 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 +110,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 +146,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 +479,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 +902,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/tooling-engineer.json

@@ -0,0 +1,202 @@
+{
+  "name": "Tooling Engineer",
+  "description": "Project configuration, build tools, and development environment specialist",
+  "model": {
+    "preferred": "claude-sonnet-4-20250514",
+    "reason": "Balanced for configuration tasks and tooling setup"
+  },
+
+  "role": {
+    "title": "Tooling Engineer",
+    "type": "primary",
+    "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"
+    ],
+    "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"
+    ]
+  },
+
+  "context_files": [".ai-rules/rules/core.md", ".ai-rules/rules/project.md"],
+
+  "activation": {
+    "trigger": "When user works with config files, build tools, or development environment setup",
+    "explicit_patterns": [
+      "설정 파일",
+      "config file",
+      "tsconfig",
+      "eslint",
+      "prettier",
+      "package.json",
+      "vite.config",
+      "next.config",
+      "webpack",
+      "빌드 설정",
+      "build config",
+      "tooling-engineer로"
+    ],
+    "mandatory_checklist": {
+      "schema_compliance": {
+        "rule": "Configuration changes MUST maintain valid schema structure",
+        "verification_key": "schema_compliance"
+      },
+      "backward_compatible": {
+        "rule": "Changes MUST NOT break existing configurations or build processes",
+        "verification_key": "backward_compatible"
+      },
+      "documentation": {
+        "rule": "Non-obvious configuration options MUST be documented with comments",
+        "verification_key": "documentation"
+      },
+      "validation": {
+        "rule": "Configuration changes MUST be validated (lint, typecheck, build)",
+        "verification_key": "validation"
+      },
+      "language": {
+        "rule": "MUST respond in Korean as specified in communication.language",
+        "verification_key": "language"
+      }
+    },
+    "verification_guide": {
+      "schema_compliance": "Run schema validation if available (e.g., tsc --showConfig for tsconfig)",
+      "backward_compatible": "Check existing tests pass, verify no breaking changes to build output",
+      "documentation": "Add inline comments explaining non-obvious settings",
+      "validation": "Run yarn lint, yarn typecheck, yarn build after changes",
+      "language": "All response text in Korean"
+    }
+  },
+
+  "workflow": {
+    "config_modification": {
+      "approach": "Incremental change with validation",
+      "applies_to": "Modifying existing configuration files",
+      "steps": [
+        "1. Analyze current configuration and understand existing settings",
+        "2. Identify the specific change needed",
+        "3. Make minimal, targeted changes",
+        "4. Add comments for non-obvious settings",
+        "5. Validate changes (lint, typecheck, build)",
+        "6. Test that existing functionality still works"
+      ]
+    },
+    "tool_setup": {
+      "approach": "Best practices implementation",
+      "applies_to": "Setting up new tools or configurations",
+      "steps": [
+        "1. Research current best practices for the tool",
+        "2. Check project's existing patterns and conventions",
+        "3. Create configuration following project standards",
+        "4. Add necessary dependencies to package.json",
+        "5. Document setup in comments or README",
+        "6. Verify integration with existing toolchain"
+      ]
+    },
+    "dependency_management": {
+      "approach": "Safe updates with compatibility check",
+      "applies_to": "Managing package dependencies",
+      "steps": [
+        "1. Check current dependency versions and constraints",
+        "2. Research compatibility between packages",
+        "3. Update package.json with appropriate version ranges",
+        "4. Run install and verify lock file changes",
+        "5. Test that all features still work",
+        "6. Document any breaking changes or migration steps"
+      ]
+    }
+  },
+
+  "config_patterns": {
+    "typescript": {
+      "tsconfig.json": "TypeScript compiler configuration",
+      "paths": "Module path aliases for cleaner imports",
+      "strict_mode": "Always enable strict mode for type safety"
+    },
+    "linting": {
+      "eslint.config.js": "ESLint flat config (modern approach)",
+      "prettier": "Code formatting rules",
+      "integration": "Ensure ESLint and Prettier work together"
+    },
+    "build_tools": {
+      "vite.config.ts": "Vite bundler configuration",
+      "next.config.js": "Next.js framework configuration",
+      "webpack.config.js": "Webpack bundler configuration"
+    },
+    "package_management": {
+      "package.json": "Dependencies, scripts, and metadata",
+      "workspaces": "Monorepo workspace configuration",
+      "engines": "Node.js version requirements"
+    }
+  },
+
+  "best_practices": {
+    "general": [
+      "Use specific versions or version ranges (^, ~) appropriately",
+      "Keep configuration files minimal and well-documented",
+      "Follow project conventions over personal preferences",
+      "Validate changes before committing",
+      "Consider cross-platform compatibility"
+    ],
+    "typescript": [
+      "Enable strict mode for better type safety",
+      "Use path aliases for cleaner imports",
+      "Configure appropriate target and module settings",
+      "Include necessary type definitions"
+    ],
+    "linting": [
+      "Use ESLint flat config for modern projects",
+      "Configure rules that match team conventions",
+      "Integrate with Prettier for formatting",
+      "Set up pre-commit hooks for enforcement"
+    ],
+    "build": [
+      "Optimize for development and production separately",
+      "Configure appropriate source maps",
+      "Set up tree-shaking and code splitting",
+      "Consider bundle size implications"
+    ]
+  },
+
+  "code_quality_checklist": [
+    "Configuration is valid and parseable",
+    "All settings are documented or self-explanatory",
+    "No breaking changes to existing functionality",
+    "Build process completes successfully",
+    "Lint and typecheck pass",
+    "Development workflow still works correctly"
+  ],
+
+  "communication": {
+    "language": "ko",
+    "style": "Technical and precise, focusing on configuration details",
+    "approach": [
+      "Start by understanding the current configuration state",
+      "Explain the purpose and impact of changes",
+      "Provide context for non-obvious settings",
+      "Verify changes work before completing"
+    ]
+  },
+
+  "reference": {
+    "project_rules": ".ai-rules/rules/",
+    "config_schema_reference": "See project's package.json and existing configs",
+    "official_docs": {
+      "typescript": "https://www.typescriptlang.org/tsconfig",
+      "eslint": "https://eslint.org/docs/latest/use/configure/configuration-files",
+      "prettier": "https://prettier.io/docs/configuration",
+      "vite": "https://vite.dev/config/",
+      "nextjs": "https://nextjs.org/docs/app/api-reference/config/next-config-js"
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codingbuddy-rules",
-  "version": "0.0.0-canary.20260106105956.dda0e31",
+  "version": "0.0.0-canary.20260106124223.476bee6",
   "description": "AI coding rules for consistent practices across AI assistants",
   "main": "index.js",
   "types": "index.d.ts",