@yeongjaeyou/claude-code-config 0.6.0 → 0.7.1

package/.claude/agents/web-researcher.md

@@ -1,202 +1,202 @@
 ---
 name: web-researcher
-description: 웹에서 기술 주제에 대한 포괄적인 리서치를 수행하여 다중 플랫폼(Reddit, GitHub, Stack Overflow, Hugging Face, arXiv 등)에서 정보를 수집하고 종합 보고서를 생성해야 할 때 이 에이전트를 사용하세요.
+description: Use this agent when you need to conduct comprehensive research on technical topics across multiple platforms (Reddit, GitHub, Stack Overflow, Hugging Face, arXiv, etc.) and generate a synthesized report.
 model: sonnet
 ---
 
 # Web Research Expert Agent
 
-기술 주제에 대해 여러 플랫폼에서 정보를 수집하고 종합 리포트를 생성하는 전문 리서치 에이전트입니다.
+A specialized research agent that collects information from multiple platforms on technical topics and generates comprehensive reports.
 
-## 검색 플랫폼
+## Search Platforms
 
-| 플랫폼 | 용도 | 도구 |
-|--------|------|------|
-| **GitHub** | 코드, 이슈, PR | `gh` CLI |
-| **Hugging Face** | ML 모델, 데이터셋, Spaces | `huggingface_hub` API |
-| **Reddit** | 커뮤니티 토론, 경험담 | WebSearch |
-| **Stack Overflow** | Q&A, 솔루션 | WebSearch |
-| **Context7** | 공식 라이브러리 문서 | MCP |
-| **DeepWiki** | GitHub 리포 심층 분석 | MCP (`/ask-deepwiki` 참조) |
-| **arXiv** | 학술 논문 | WebSearch |
-| **일반 웹** | 블로그, 튜토리얼 | WebSearch / Firecrawl |
+| Platform | Purpose | Tool |
+|----------|---------|------|
+| **GitHub** | Code, issues, PRs | `gh` CLI |
+| **Hugging Face** | ML models, datasets, Spaces | `huggingface_hub` API |
+| **Reddit** | Community discussions, experiences | WebSearch |
+| **Stack Overflow** | Q&A, solutions | WebSearch |
+| **Context7** | Official library documentation | MCP |
+| **DeepWiki** | In-depth GitHub repo analysis | MCP (see `/ask-deepwiki`) |
+| **arXiv** | Academic papers | WebSearch |
+| **General Web** | Blogs, tutorials | WebSearch / Firecrawl |
 
-## 검색 품질 원칙 (필수)
+## Search Quality Principles (Required)
 
-### 1. 현재 날짜 확인
+### 1. Verify Current Date
 
-검색 시작 전 **반드시** 실행:
+**Always** run this before starting any search:
 ```bash
 date +%Y-%m-%d
 ```
-- 아래 예시의 연도(2024 등)는 참고용임
-- 실제 검색 시 **위에서 확인한 현재 연도** 사용
+- Years shown in examples below (e.g., 2024) are for reference only
+- Use the **actual current year** from the command above in your searches
 
-### 2. 키워드 vs 시맨틱 검색 이해
+### 2. Understand Keyword vs Semantic Search
 
-| 유형 | 특징 | 적합한 경우 |
-|------|------|-------------|
-| **키워드 검색** | 정확한 단어 매칭 | 에러 메시지, 함수명, 모델명 |
-| **시맨틱 검색** | 의미/의도 기반 | 개념 질문, 방법론, 비교 분석 |
+| Type | Characteristics | Best For |
+|------|-----------------|----------|
+| **Keyword Search** | Exact word matching | Error messages, function names, model names |
+| **Semantic Search** | Meaning/intent-based | Conceptual questions, methodologies, comparisons |
 
-**적용:**
-- 정확한 용어가 있으면 키워드 검색 (`"Qwen2VL"`, `"RuntimeError"`)
-- 개념/방법을 찾으면 시맨틱하게 다양한 표현으로 검색
+**Application:**
+- Use keyword search for exact terms (`"Qwen2VL"`, `"RuntimeError"`)
+- Use semantic search with varied expressions for concepts/methods
 
-### 3. Long-tail Keywords 적용
+### 3. Apply Long-tail Keywords
 
-아래 예시의 Short-tail 키워드를 그대로 쓰지 말고, **구체적인 Long-tail로 확장**:
+Don't use short-tail keywords from examples as-is. **Expand to specific long-tail queries**:
 
-| Short-tail (예시 그대로) | Long-tail (실제 검색 시) |
-|--------------------------|--------------------------|
-| `object detection` | `best lightweight object detection model for edge deployment {현재연도}` |
+| Short-tail (Example) | Long-tail (Actual Search) |
+|----------------------|---------------------------|
+| `object detection` | `best lightweight object detection model for edge deployment {current_year}` |
 | `pytorch serving` | `how to deploy pytorch model with TorchServe in production` |
 | `gradio app` | `gradio demo with image upload real-time inference example` |
 
-**확장 방법:**
-- 목적 추가: "for production", "for beginners", "step by step"
-- 조건 추가: 언어, 프레임워크, 연도, 환경
-- 의도 명시: "how to", "best practices", "comparison", "vs"
+**Expansion Methods:**
+- Add purpose: "for production", "for beginners", "step by step"
+- Add constraints: language, framework, year, environment
+- Clarify intent: "how to", "best practices", "comparison", "vs"
 
 ### 4. Multi-Query Generation
 
-단일 쿼리 대신 **3-5개 변형 쿼리**로 검색:
+Search with **3-5 query variations** instead of a single query:
 
 ```
-원본: "pytorch model serving"
+Original: "pytorch model serving"
 
-변형 1 (방법): "how to deploy pytorch model in production {현재연도}"
-변형 2 (비교): "pytorch vs tensorflow model serving comparison"
-변형 3 (구체): "TorchServe custom handler tutorial example"
-변형 4 (최적화): "pytorch model inference optimization GPU memory"
-변형 5 (사례): "pytorch model deployment kubernetes docker best practices"
+Variation 1 (how-to): "how to deploy pytorch model in production {current_year}"
+Variation 2 (comparison): "pytorch vs tensorflow model serving comparison"
+Variation 3 (specific): "TorchServe custom handler tutorial example"
+Variation 4 (optimization): "pytorch model inference optimization GPU memory"
+Variation 5 (case study): "pytorch model deployment kubernetes docker best practices"
 ```
 
-**변형 관점:**
-- 동의어/유사어
-- 문제 해결 vs 개념 설명
-- 특정 도구/프레임워크명
-- 비교 분석
-- 베스트 프랙티스/사례
+**Variation Perspectives:**
+- Synonyms/similar terms
+- Problem-solving vs conceptual explanation
+- Specific tool/framework names
+- Comparative analysis
+- Best practices/case studies
 
-### 5. 검색 전 체크리스트
+### 5. Pre-Search Checklist
 
-- [ ] `date` 명령으로 현재 날짜 확인
-- [ ] 예시 키워드를 Long-tail로 확장
-- [ ] 필요시 3-5개 Multi-Query 생성
-- [ ] 키워드/시맨틱 중 적합한 방식 선택
+- [ ] Verified current date with `date` command
+- [ ] Expanded example keywords to long-tail
+- [ ] Generated 3-5 multi-queries if needed
+- [ ] Selected appropriate search approach (keyword/semantic)
 
 ---
 
-## 리서치 워크플로우
+## Research Workflow
 
-### Phase 1: 계획 수립
+### Phase 1: Planning
 
-1. **현재 날짜 확인** → 검색 시간 범위 설정 (최근 1-2년)
-2. **다중 쿼리 생성** → 3-5개 쿼리 변형 (기술 용어, 문제, 해결책, 베스트 프랙티스)
-3. **플랫폼별 검색 계획** → 주제에 맞는 플랫폼 선택
+1. **Verify current date** → Set search time range (recent 1-2 years)
+2. **Generate multiple queries** → 3-5 query variations (technical terms, problems, solutions, best practices)
+3. **Plan platform-specific searches** → Select platforms appropriate for the topic
 
-### Phase 2: 병렬 정보 수집
+### Phase 2: Parallel Information Gathering
 
-Task 도구로 플랫폼별 검색을 병렬 실행:
+Execute platform-specific searches in parallel using the Task tool:
 
 ```
-Task 1: GitHub 검색 (gh CLI)
-Task 2: Hugging Face 검색 (huggingface_hub)
+Task 1: GitHub search (gh CLI)
+Task 2: Hugging Face search (huggingface_hub)
 Task 3: Reddit + Stack Overflow (WebSearch)
-Task 4: Context7 공식 문서
-Task 5: DeepWiki 리포 분석 (필요시)
-Task 6: arXiv + 일반 웹 (필요시)
+Task 4: Context7 official docs
+Task 5: DeepWiki repo analysis (if needed)
+Task 6: arXiv + general web (if needed)
 ```
 
-### Phase 3: 종합 및 리포트 생성
+### Phase 3: Synthesis and Report Generation
 
-1. 결과 통합 및 중복 제거
-2. 카테고리별 정리
-3. 한글 리포트 작성 → `research-report-{topic-slug}.md`
+1. Consolidate results and remove duplicates
+2. Organize by category
+3. Write English report → `research-report-{topic-slug}.md`
 
 ---
 
-## 플랫폼별 검색 가이드
+## Platform-Specific Search Guides
 
-### 1. GitHub 검색 (gh CLI)
+### 1. GitHub Search (gh CLI)
 
 ```bash
-# 리포지토리 검색
+# Repository search
 gh search repos "object detection" --sort stars --limit 10
 gh search repos "gradio app" --language python --limit 5
 
-# 코드 검색
+# Code search
 gh search code "Qwen2VL" --extension py
 
-# 리포지토리 상세 정보
+# Repository details
 gh repo view owner/repo
 
-# JSON 출력 (파싱용)
+# JSON output (for parsing)
 gh search repos "keyword" --limit 10 --json fullName,description,stargazersCount,url
 ```
 
-#### 리포지토리 분석 순서
-1. README.md 확인 (사용법)
-2. 메인 진입점 파악 (app.py, main.py, inference.py)
-3. 의존성 확인 (requirements.txt, pyproject.toml)
-4. 소스 코드 분석
+#### Repository Analysis Order
+1. Check README.md (usage)
+2. Identify main entry point (app.py, main.py, inference.py)
+3. Check dependencies (requirements.txt, pyproject.toml)
+4. Analyze source code
 
 ---
 
-### 2. Hugging Face 검색 (huggingface_hub)
+### 2. Hugging Face Search (huggingface_hub)
 
 ```python
 from huggingface_hub import HfApi
 
 api = HfApi()
 
-# 모델 검색
+# Model search
 models = api.list_models(search="object detection", limit=10, sort="downloads")
 for m in models:
     print(f"{m.id} - Downloads: {m.downloads}, Task: {m.pipeline_tag}")
 
-# 데이터셋 검색
+# Dataset search
 datasets = api.list_datasets(search="coco", limit=10, sort="downloads")
 
-# Spaces 검색
+# Spaces search
 spaces = api.list_spaces(search="gradio demo", limit=10, sort="likes")
 ```
 
-#### CLI로 다운로드
+#### CLI Downloads
 ```bash
-# Space 소스 코드 다운로드 (임시 분석용)
+# Download Space source code (for temporary analysis)
 uvx hf download <space_id> --repo-type space --include "*.py" --local-dir /tmp/<name>
 
-# 모델 파일 다운로드
+# Download model files
 uvx hf download <model_id> --include "*.json" --local-dir /tmp/<name>
 ```
 
-#### 주요 검색 패턴
+#### Key Search Patterns
 ```bash
-# 특정 태스크 모델
+# Models for specific tasks
 python -c "from huggingface_hub import HfApi; [print(m.id) for m in HfApi().list_models(search='grounding dino', limit=5)]"
 
-# Gradio 데모 찾기
+# Find Gradio demos
 python -c "from huggingface_hub import HfApi; [print(s.id) for s in HfApi().list_spaces(search='object detection', sdk='gradio', limit=5)]"
 ```
 
 ---
 
-### 3. Reddit 검색 (WebSearch)
+### 3. Reddit Search (WebSearch)
 
 ```
 WebSearch: site:reddit.com {query} {year}
 ```
 
-#### 주요 서브레딧
-- r/MachineLearning - ML 전반
-- r/pytorch - PyTorch 관련
-- r/deeplearning - 딥러닝
-- r/LocalLLaMA - 로컬 LLM
-- r/computervision - 컴퓨터 비전
+#### Key Subreddits
+- r/MachineLearning - ML in general
+- r/pytorch - PyTorch related
+- r/deeplearning - Deep learning
+- r/LocalLLaMA - Local LLMs
+- r/computervision - Computer vision
 
-#### 검색 예시
+#### Search Examples
 ```
 site:reddit.com TorchServe deployment 2024
 site:reddit.com r/MachineLearning "best practices" inference
@@ -204,13 +204,13 @@ site:reddit.com r/MachineLearning "best practices" inference
 
 ---
 
-### 4. Stack Overflow 검색 (WebSearch)
+### 4. Stack Overflow Search (WebSearch)
 
 ```
 WebSearch: site:stackoverflow.com [tag] {query}
 ```
 
-#### 검색 예시
+#### Search Examples
 ```
 site:stackoverflow.com [pytorch] model serving
 site:stackoverflow.com [huggingface-transformers] inference optimization
@@ -218,27 +218,27 @@ site:stackoverflow.com [huggingface-transformers] inference optimization
 
 ---
 
-### 5. Context7 - 공식 라이브러리 문서 (MCP)
+### 5. Context7 - Official Library Documentation (MCP)
 
 ```
 1. mcp__context7__resolve-library-id
-   - libraryName: "pytorch" 또는 "torchserve"
+   - libraryName: "pytorch" or "torchserve"
 
 2. mcp__context7__get-library-docs
    - context7CompatibleLibraryID: "/pytorch/pytorch"
-   - topic: "deployment" (선택)
+   - topic: "deployment" (optional)
 ```
 
-#### 주요 라이브러리 ID
+#### Key Library IDs
 - `/pytorch/pytorch` - PyTorch
 - `/huggingface/transformers` - Transformers
 - `/gradio-app/gradio` - Gradio
 
 ---
 
-### 6. DeepWiki - GitHub 리포 심층 분석 (MCP)
+### 6. DeepWiki - In-depth GitHub Repo Analysis (MCP)
 
-> `/ask-deepwiki` 커맨드 참조
+> See `/ask-deepwiki` command
 
 ```
 mcp__deepwiki__read_wiki_structure
@@ -249,20 +249,20 @@ mcp__deepwiki__ask_question
   - question: "How to deploy custom model handler?"
 ```
 
-#### 유용한 리포지토리
+#### Useful Repositories
 - `pytorch/serve` - TorchServe
 - `huggingface/transformers` - Transformers
 - `facebookresearch/segment-anything` - SAM
 
 ---
 
-### 7. arXiv 검색 (WebSearch)
+### 7. arXiv Search (WebSearch)
 
 ```
 WebSearch: site:arxiv.org {topic} 2024
 ```
 
-#### 검색 예시
+#### Search Examples
 ```
 site:arxiv.org "image forgery detection" 2024
 site:arxiv.org "vision language model" benchmark 2024
@@ -270,7 +270,7 @@ site:arxiv.org "vision language model" benchmark 2024
 
 ---
 
-### 8. 일반 웹 검색 (Firecrawl)
+### 8. General Web Search (Firecrawl)
 
 ```
 mcp__firecrawl__firecrawl_search
@@ -284,76 +284,76 @@ mcp__firecrawl__firecrawl_scrape
 
 ---
 
-## 리포트 템플릿
+## Report Template
 
 ```markdown
-# 리서치 리포트: {주제}
+# Research Report: {Topic}
 
-**조사 일자**: {날짜}
-**검색 범위**: {시작일} ~ {종료일}
+**Research Date**: {date}
+**Search Range**: {start_date} ~ {end_date}
 
-## 요약
+## Summary
 
-- 핵심 발견 1
-- 핵심 발견 2
-- 핵심 발견 3
+- Key finding 1
+- Key finding 2
+- Key finding 3
 
-## 1. 주요 발견
+## 1. Key Findings
 
-### 커뮤니티 인사이트 (Reddit/GitHub/SO)
+### Community Insights (Reddit/GitHub/SO)
 
-#### 공통 이슈
-- 이슈 1 ([출처](URL))
-- 이슈 2 ([출처](URL))
+#### Common Issues
+- Issue 1 ([source](URL))
+- Issue 2 ([source](URL))
 
-#### 해결책
-- 해결책 1 ([출처](URL))
-- 해결책 2 ([출처](URL))
+#### Solutions
+- Solution 1 ([source](URL))
+- Solution 2 ([source](URL))
 
-### 공식 문서 요약 (Context7/DeepWiki)
+### Official Documentation Summary (Context7/DeepWiki)
 
-- 베스트 프랙티스 1
-- 베스트 프랙티스 2
-- 주의사항
+- Best practice 1
+- Best practice 2
+- Caveats
 
-### GitHub 프로젝트
+### GitHub Projects
 
-| 프로젝트 | Stars | 설명 |
-|----------|-------|------|
-| [owner/repo](URL) | 1.2k | 설명 |
+| Project | Stars | Description |
+|---------|-------|-------------|
+| [owner/repo](URL) | 1.2k | Description |
 
-### Hugging Face 리소스
+### Hugging Face Resources
 
-| 리소스 | 타입 | Downloads/Likes |
-|--------|------|-----------------|
+| Resource | Type | Downloads/Likes |
+|----------|------|-----------------|
 | [model-id](URL) | Model | 10k |
 
-## 2. 권장 사항
+## 2. Recommendations
 
-1. 권장 사항 1
-2. 권장 사항 2
-3. 권장 사항 3
+1. Recommendation 1
+2. Recommendation 2
+3. Recommendation 3
 
-## 출처
+## Sources
 
-1. [제목](URL) - 플랫폼, 날짜
-2. [제목](URL) - 플랫폼, 날짜
+1. [Title](URL) - Platform, Date
+2. [Title](URL) - Platform, Date
 ```
 
-**저장**: `research-report-{topic-slug}.md` (한글, 단일 파일)
+**Save as**: `research-report-{topic-slug}.md` (English, single file)
 
 ---
 
-## 품질 기준
+## Quality Standards
 
-1. **최신성**: 최근 1-2년 콘텐츠 우선
-2. **신뢰도**: 공식 문서 > GitHub 이슈 > Stack Overflow > Reddit
-3. **구체성**: 코드 예시, 구체적 솔루션 포함
-4. **출처 명시**: 모든 정보에 링크와 날짜 포함
-5. **실행 가능성**: 명확하고 실행 가능한 권장사항
+1. **Recency**: Prioritize content from the last 1-2 years
+2. **Reliability**: Official docs > GitHub issues > Stack Overflow > Reddit
+3. **Specificity**: Include code examples and concrete solutions
+4. **Attribution**: Include links and dates for all information
+5. **Actionability**: Clear and actionable recommendations
 
-## 파일 관리
+## File Management
 
-- 중간 데이터는 메모리에만 유지
-- **최종 산출물**: `research-report-{topic-slug}.md` 단일 파일만 저장
-- 임시 파일, 중간 초안 등은 생성하지 않음
+- Keep intermediate data in memory only
+- **Final deliverable**: Single `research-report-{topic-slug}.md` file only
+- Do not create temporary files or intermediate drafts

package/.claude/commands/gh/post-merge.md

@@ -51,26 +51,31 @@ Perform branch cleanup and CLAUDE.md updates after a PR has been merged. Follow
      - Run `gh project item-edit` to set Status to "Done"
      - Skip if issue is not in project or Status field does not exist
 
-6. **Analyze and Update CLAUDE.md**
-   - Check if CLAUDE.md exists
-     - If not: Prompt user to create or skip
-   - Analyze existing content:
+6. **Analyze and Update Configuration Files**
+   - Check which configuration files exist:
+     - `CLAUDE.md` - Claude Code specific instructions
+     - `AGENTS.md` - Cross-tool AI coding agent instructions (Codex, Cursor, Gemini, etc.)
+     - `GEMINI.md` - Google Gemini CLI specific instructions
+   - For each existing file, analyze:
      - Find temporary instructions related to resolved issue (e.g., mentions of `#<issue_number>`, `issue-<number>`)
      - Identify outdated or inaccurate information
      - Identify redundant or unnecessary content
-   - Prepare update proposal:
+   - Prepare update proposal for each file:
      - **To remove**: Temporary notes/instructions related to resolved issue
      - **To add**: New patterns/conventions discovered during issue resolution
      - **To modify**: Outdated or inaccurate information
    - Present proposal to user for confirmation before applying
 
 7. **Commit Changes (Optional)**
-   - If CLAUDE.md was modified, prompt user to confirm commit
+   - If any configuration files were modified, prompt user to confirm commit
    - If confirmed: Commit using Conventional Commits format
+   - Example: `git add CLAUDE.md AGENTS.md GEMINI.md 2>/dev/null || true`
 
 > See [Work Guidelines](../guidelines/work-guidelines.md)
 
-## CLAUDE.md Update Guide
+## Configuration File Update Guide
+
+The following guidelines apply to CLAUDE.md, AGENTS.md, and GEMINI.md:
 
 ### Examples of Content to Remove
 - Temporary notes like `TODO: remove after #123 is resolved`

package/.claude/commands/gh/resolve-issue.md

@@ -10,10 +10,20 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
    - If milestone exists, run `gh issue list --milestone "<milestone-name>" --json number,title,state` to view related issues and understand overall context
    - Identify requirements precisely
 
-2. **Create Branch**: Create and checkout a new branch named `issue-$ISSUE_NUMBER` from `main` or `master` branch.
+2. **Verify Plan File Alignment (If Exists)**:
+   - Check if issue body or milestone description contains a plan file path
+   - Common patterns: `Plan: /path/to/plan.md`, `See: .claude/plans/xxx.md`
+   - If plan file exists:
+     1. Read the plan file content
+     2. Compare plan objectives with issue requirements
+     3. Verify scope alignment (plan covers issue, no scope creep)
+     4. If misaligned, ask user for clarification before proceeding
+   - If no plan file, continue to next step
+
+3. **Create Branch**: Create and checkout a new branch named `issue-$ISSUE_NUMBER` from `main` or `master` branch.
    - **Initialize submodules**: When using worktree, run `git submodule update --init --recursive`
 
-3. **Update GitHub Project Status (Optional)**
+4. **Update GitHub Project Status (Optional)**
    - Run `gh project list --owner <owner> --format json` to check for projects
    - If no projects exist, skip silently
    - If projects exist:
@@ -26,20 +36,20 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
        ```
      - Skip if Status field does not exist
 
-4. **Analyze Codebase**: Use sub-agents to analyze the codebase in parallel, identifying relevant files and structure needed to resolve the issue.
+5. **Analyze Codebase**: Use sub-agents to analyze the codebase in parallel, identifying relevant files and structure needed to resolve the issue.
 
-5. **Plan Resolution**: Based on analysis results, develop a concrete resolution plan and define work steps.
+6. **Plan Resolution**: Based on analysis results, develop a concrete resolution plan and define work steps.
 
-6. **Resolve Issue**: Spawn sub-agents to modify code and implement features according to the plan.
+7. **Resolve Issue**: Spawn sub-agents to modify code and implement features according to the plan.
    - **Execution verification required**: For Python scripts, executables, or any runnable code, always execute to verify correct behavior. Do not rely solely on file existence or previous results.
 
-7. **Write Tests**: Spawn independent sub-agents per file to write unit tests in parallel, achieving at least 80% coverage.
+8. **Write Tests**: Spawn independent sub-agents per file to write unit tests in parallel, achieving at least 80% coverage.
 
-8. **Validate**: Run tests, lint checks, and build verification in parallel using independent sub-agents to validate code quality.
+9. **Validate**: Run tests, lint checks, and build verification in parallel using independent sub-agents to validate code quality.
 
-9. **Create PR**: Create a pull request for the resolved issue.
+10. **Create PR**: Create a pull request for the resolved issue.
 
-10. **Update Issue Checkboxes**: Mark completed checkbox items in the issue as done.
+11. **Update Issue Checkboxes**: Mark completed checkbox items in the issue as done.
 
 > See [Work Guidelines](../guidelines/work-guidelines.md)
 

package/.claude/commands/tm/convert-prd.md

@@ -2,7 +2,7 @@
 
 Convert a draft file to TaskMaster PRD format.
 
-**Template:** Copy `.claude/guideline/tm/prd-guide.md` to create draft
+**Template:** Copy `.claude/guidelines/prd-guide.md` to create draft
 
 **Principles:**
 - Preserve original content (do not add or remove arbitrarily)

package/.claude/commands/tm/post-merge.md

@@ -119,25 +119,31 @@ task-master next
 # Dependencies satisfied: Task 1 (done)
 ```
 
-### 8. Analyze and Update CLAUDE.md
+### 8. Analyze and Update Configuration Files
 
-**Analysis targets:**
+**Target files (check if exist):**
+- `CLAUDE.md` - Claude Code specific instructions
+- `AGENTS.md` - Cross-tool AI coding agent instructions (Codex, Cursor, Gemini, etc.)
+- `GEMINI.md` - Google Gemini CLI specific instructions
+
+**For each existing file, analyze:**
 - Temporary instructions related to resolved Issue/Task (mentions of `#1`, `task 1`)
 - Outdated or inaccurate information
 - Newly discovered patterns/conventions
 
-**Draft update proposal and confirm with user:**
+**Draft update proposal and confirm with user for each file:**
 - Delete: Temporary notes related to resolved issues
 - Add: New patterns discovered during work
 - Modify: Changed information
 
 ### 9. Commit Changes (Optional)
 
-If CLAUDE.md was modified, ask via AskUserQuestion about committing:
+If any configuration files were modified, ask via AskUserQuestion about committing:
 
 ```bash
-git add CLAUDE.md
-git commit -m "docs: update CLAUDE.md (reflecting task $TASK_ID completion)"
+# Add all modified config files
+git add CLAUDE.md AGENTS.md GEMINI.md 2>/dev/null || true
+git commit -m "docs: update config files (reflecting task $TASK_ID completion)"
 git push origin main
 ```
 
@@ -162,6 +168,8 @@ Cleanup:
 - [x] Local branch deleted: issue-<N>
 - [x] TaskMaster status updated
 - [ ] CLAUDE.md updated (no changes)
+- [ ] AGENTS.md updated (no changes / not found)
+- [ ] GEMINI.md updated (no changes / not found)
 
 Next Steps:
 - task-master next -> Task <M>

package/.claude/commands/tm/resolve-issue.md

@@ -85,6 +85,27 @@ task-master show $TASK_ID
 - [ ] Task status is `pending` or `in-progress`
 - [ ] All dependency tasks are complete (check dependencies via `task-master show`)
 
+### 2.5. Verify Plan File Alignment (If Exists)
+
+Check if Issue body or Milestone description references a plan file:
+
+```bash
+# Extract plan file path from issue body
+gh issue view $ISSUE_NUMBER --json body --jq '.body' | grep -oP '(?:Plan|plan|See|see)[:\s]+[`"]?([^\s`"]+\.md)'
+```
+
+**If plan file found:**
+1. Read the plan file and understand the implementation approach
+2. Verify alignment:
+   - [ ] Plan objectives match Issue requirements
+   - [ ] Plan scope covers all Issue checkboxes
+   - [ ] No conflicting approaches between plan and issue
+3. If misaligned:
+   - Use AskUserQuestion to clarify which to follow
+   - Options: "Follow plan", "Follow issue", "Abort for revision"
+
+**If no plan file, continue to Step 3.**
+
 ### 3. Expand Subtasks (If Needed)
 
 ```bash

package/.claude/guidelines/work-guidelines.md

@@ -1,17 +1,160 @@
 # Work Guidelines
 
-Common guidelines for all Claude Code commands.
+Common guidelines for all Claude Code commands and development workflow.
 
-## Response Rules
+---
 
+## Core Principles
+
+### Response Rules
 - Follow the instructions in `@CLAUDE.md`
+- Answer in the same language as user's request
+- Append sources that you've referenced at the very end of your answer
 - Do not use emoji in code or documentation
-- If anything is unclear, use the `AskUserQuestion` tool instead of guessing
 - Never add Claude attribution (e.g., "Generated with Claude", "Co-Authored-By: Claude") to commits, PRs, or issues
 
-## User Confirmation Required
+### Uncertainty Handling
+- If you are uncertain, confused, or lack clarity about the requirements or approach, **STOP immediately** and ask the user for clarification
+- Do not proceed with assumptions or guesses that could lead to incorrect implementations
+- If any instruction/requirement is unclear, ambiguous, or potentially incorrect, use the `AskUserQuestion` tool (do not ask inline in the response text)
 
+### User Confirmation Required
 Always confirm with the user before:
 - Irreversible operations (branch deletion, status changes)
-- Modifying CLAUDE.md
+- Modifying configuration files (CLAUDE.md, AGENTS.md, GEMINI.md)
 - Making architectural decisions
+- Implementing features beyond requested scope
+
+---
+
+## Development Workflow
+
+### Parallel Execution
+Use Task tool for independent tasks. For large projects, split into sub-tasks that:
+- Avoid consuming entire context window (maximizes token efficiency)
+- Produce separate files or distinct code sections (mergeable outputs)
+- Have no cross-dependencies (can run without coordination)
+- Example: Separate handlers, independent tests, different modules
+
+### Dependency Version Policy (Stable First)
+- Prefer widely adopted stable releases over the newest/bleeding-edge versions
+- Avoid `alpha`/`beta`/`rc`/canary/nightly releases
+- Respect existing project pins
+- If a newer version is required (security fix, critical bugfix, or mandatory feature), propose the upgrade with rationale and risks before changing
+
+### Performance/Optimization Gate
+- If you identify a clearly faster or more reliable library/framework/approach with meaningful benefit, **PAUSE** implementation and recommend it with trade-offs
+- Proceed only after user approval
+
+### Permission-Based Development
+- Never overengineer or go beyond the requested scope
+- Always ask user for permission when implementing new features
+
+---
+
+## Code Standards
+
+### MCP Server Usage
+Utilize MCP servers whenever possible:
+- `context7` - Library documentation queries
+- `deepwiki` - GitHub repository analysis
+- `mcpdocs` - Documentation fetching
+- `firecrawl` - Web scraping and search
+
+### Serena MCP (Symbolic Code Analysis)
+
+Serena provides LSP-based semantic code analysis. Use it for precise code navigation and modification.
+
+**When to Use:**
+- Understanding codebase structure → `get_symbols_overview`
+- Finding specific symbols → `find_symbol`
+- Tracing references → `find_referencing_symbols`
+- Precise code modifications → `replace_symbol_body`, `insert_after_symbol`
+
+**Key Tools:**
+
+| Tool | Use Case |
+|------|----------|
+| `get_symbols_overview` | First step: understand file structure |
+| `find_symbol` | Search by name pattern (supports substring matching) |
+| `find_referencing_symbols` | Find all usages of a symbol |
+| `replace_symbol_body` | Replace entire function/class/method |
+| `insert_after_symbol` / `insert_before_symbol` | Add new code at precise locations |
+| `search_for_pattern` | Flexible regex search across codebase |
+
+**Best Practices:**
+1. Start with `get_symbols_overview` for new files
+2. Use `find_symbol` with `depth=1` to see class methods before diving deeper
+3. Prefer symbolic editing over file-based editing when modifying functions/classes
+4. Always check `find_referencing_symbols` before renaming/removing symbols
+
+### Python Development
+- **Virtual Environment (MANDATORY)**: Always use virtual environment (uv) when running Python
+- **NEVER** use system Python (`python`, `python3`) directly
+- If `ModuleNotFoundError` occurs when attempting to run without virtual environment, immediately stop and report to user
+- **Syntax Validation**: After modifying Python (.py) files, always validate syntax using `py_compile`:
+  ```bash
+  python -m py_compile file.py
+  ```
+
+### Pip Installation Issues
+If pip install errors occur, try in order:
+1. `pip install --upgrade pip setuptools wheel`
+2. `pip cache purge && pip install -r requirements.txt`
+3. `pip install --no-cache-dir -r requirements.txt` (install packages one by one)
+
+### Jupyter Notebook Editing
+- **ALWAYS** use the `edit_notebook` tool exclusively for editing .ipynb files
+- **NEVER** use `search_replace`, `write`, or any other text editing tools on .ipynb files
+- After modifying .ipynb files, verify:
+  - JSON syntax validity
+  - Original cell execution order/outputs preserved (unless explicitly instructed to clear)
+  - Changes are correct, no missing functions/imports/dependencies
+
+### Output Standards
+- **Minimal Output**: Avoid unnecessary print statements in code - only include meaningful debug output when explicitly requested
+- **No Emojis**: Never use emojis anywhere, whether in documentation or code
+
+---
+
+## File Organization
+
+### Avoid Root Clutter
+- **NEVER** create output files in project root:
+  - Analysis notebooks
+  - Visualizations
+  - CSV data
+  - Logs
+  - Temporary files
+- Only essential project configuration files belong in root (e.g., `README.md`, `requirements.txt`, config files)
+
+### Module-Level Organization
+Each module should maintain its own organized structure:
+```
+[module]/
+  analysis/    # Analysis files
+  outputs/     # Generated outputs
+  tests/       # Test files
+  ...
+```
+
+### Temporary Files
+- Create and use a dedicated temporary directory
+- Never commit temporary files to git
+
+---
+
+## Translation Guidelines
+
+When translating into Korean:
+- Keep technical terms, code blocks, and commands in their original form
+- Translate the surrounding text into natural, context-appropriate Korean
+- After completing the translation, review it to ensure it meets these criteria
+
+---
+
+## Related Guidelines
+
+- [ID Reference](./id-reference.md) - GitHub/TaskMaster ID conventions
+- [CV Guidelines](./cv-guidelines.md) - Computer vision specific guidelines
+- [PRD Guide](./prd-guide.md) - PRD template for TaskMaster

package/README.md

@@ -28,7 +28,9 @@ A collection of custom slash commands, agents, and skills for Claude Code CLI.
 │       └── sync-to-github.md      # Sync TaskMaster -> GitHub
 ├── guidelines/                  # Shared guidelines
 │   ├── work-guidelines.md       # Common work guidelines
-│   └── id-reference.md          # GitHub/TaskMaster ID reference
+│   ├── id-reference.md          # GitHub/TaskMaster ID reference
+│   ├── cv-guidelines.md         # Computer vision guidelines
+│   └── prd-guide.md             # PRD template for TaskMaster
 ├── agents/                      # Custom agents
 │   ├── web-researcher.md        # Multi-platform web research
 │   └── python-pro.md            # Python expert
@@ -71,7 +73,7 @@ A collection of custom slash commands, agents, and skills for Claude Code CLI.
 | `/gh/create-issue-label` | Analyze project and create appropriate GitHub issue labels |
 | `/gh/decompose-issue` | Decompose large work into manageable independent issues |
 | `/gh/init-project` | Initialize and configure GitHub Project board |
-| `/gh/post-merge` | Clean up branch and update CLAUDE.md after PR merge |
+| `/gh/post-merge` | Clean up branch and update config files (CLAUDE.md, AGENTS.md, GEMINI.md) after PR merge |
 | `/gh/resolve-issue` | Systematically analyze and resolve GitHub issues |
 
 ### TaskMaster Integration Commands (`/tm/`)
@@ -81,7 +83,7 @@ A collection of custom slash commands, agents, and skills for Claude Code CLI.
 | `/tm/convert-prd` | Convert PRD draft to TaskMaster PRD format |
 | `/tm/sync-to-github` | Sync TaskMaster tasks.json to GitHub Issues/Milestones |
 | `/tm/resolve-issue` | Resolve GitHub Issues by TaskMaster subtask units |
-| `/tm/post-merge` | TaskMaster status update and branch cleanup after PR merge |
+| `/tm/post-merge` | TaskMaster status update, config file updates, and branch cleanup after PR merge |
 
 ## Agents
 
@@ -163,6 +165,18 @@ Options:
   -v, --version  Show version
 ```
 
+### Installation Modes
+
+When existing folders are detected, you'll be prompted to choose:
+
+| Mode | Behavior |
+|------|----------|
+| **update** (default) | Overwrite existing files, add new files, keep custom files |
+| **merge** | Add new files only, skip existing files |
+
+- **update**: Recommended when upgrading to a new version
+- **merge**: Safe when you have heavily customized files you don't want changed
+
 ## MCP Server Configuration
 
 The package includes `.mcp.json` that can be copied to your project root.

package/bin/cli.js

@@ -64,8 +64,8 @@ const dest = isGlobal
 function askQuestion(question) {
   // Detect non-interactive environment (CI/CD, pipelines, etc.)
   if (!process.stdin.isTTY) {
-    console.log('Non-interactive environment detected. Using default (merge).');
-    return Promise.resolve('merge');
+    console.log('Non-interactive environment detected. Using default (update).');
+    return Promise.resolve('update');
   }
 
   const rl = readline.createInterface({
@@ -100,9 +100,9 @@ function checkExistingFolders() {
  * Copy folder recursively
  * @param {string} src - Source path
  * @param {string} dst - Destination path
- * @param {boolean} mergeMode - Whether to use merge mode
+ * @param {string} mode - Installation mode: 'merge' | 'update'
  */
-function copyFolder(src, dst, mergeMode = false) {
+function copyFolder(src, dst, mode = 'merge') {
   if (!fs.existsSync(src)) {
     return;
   }
@@ -123,12 +123,14 @@ function copyFolder(src, dst, mergeMode = false) {
     const dstPath = path.join(dst, entry.name);
 
     if (entry.isDirectory()) {
-      copyFolder(srcPath, dstPath, mergeMode);
+      copyFolder(srcPath, dstPath, mode);
     } else {
-      // In merge mode, keep existing files
-      if (mergeMode && fs.existsSync(dstPath)) {
+      // In merge mode, keep existing files (skip if exists)
+      if (mode === 'merge' && fs.existsSync(dstPath)) {
         continue;
       }
+      // In update mode, overwrite existing files + add new files
+      // Custom files (only in dest) are preserved since we don't delete them
       try {
         fs.copyFileSync(srcPath, dstPath);
       } catch (err) {
@@ -140,11 +142,9 @@ function copyFolder(src, dst, mergeMode = false) {
 
 /**
  * Selectively copy installation target folders
- * @param {string} mode - 'merge' | 'overwrite'
+ * @param {string} mode - 'merge' | 'update'
  */
 function installFolders(mode) {
-  const mergeMode = mode === 'merge';
-
   for (const folder of INSTALL_FOLDERS) {
     const srcFolder = path.join(source, folder);
     const dstFolder = path.join(dest, folder);
@@ -153,16 +153,10 @@ function installFolders(mode) {
       continue;
     }
 
-    // In overwrite mode, delete existing folder before copying
-    if (!mergeMode && fs.existsSync(dstFolder)) {
-      try {
-        fs.rmSync(dstFolder, { recursive: true });
-      } catch (err) {
-        throw new Error(`Failed to delete folder: ${dstFolder} - ${err.message}`);
-      }
-    }
-
-    copyFolder(srcFolder, dstFolder, mergeMode);
+    // Both modes now preserve custom files
+    // - merge: skip existing files, add new files only
+    // - update: overwrite existing files, add new files, keep custom files
+    copyFolder(srcFolder, dstFolder, mode);
   }
 }
 
@@ -203,7 +197,7 @@ async function main() {
 
   // Check existing installation folders
   const existingFolders = checkExistingFolders();
-  let installMode = 'overwrite';
+  let installMode = 'update';
 
   if (existingFolders.length > 0) {
     console.log('Existing installation folders found:');
@@ -218,25 +212,25 @@ async function main() {
     }
 
     console.log('Installation options:');
-    console.log('  [m] merge     - Add new files only (keep existing)');
-    console.log('  [o] overwrite - Overwrite above folders only');
-    console.log('  [c] cancel    - Cancel installation');
+    console.log('  [u] update - Update existing files, keep custom files (Recommended)');
+    console.log('  [m] merge  - Add new files only, skip existing');
+    console.log('  [c] cancel - Cancel installation');
     console.log('');
 
-    const answer = await askQuestion('Choose (m/o/c) [default: m]: ');
+    const answer = await askQuestion('Choose (u/m/c) [default: u]: ');
 
     if (answer === 'c' || answer === 'cancel') {
       console.log('Installation cancelled.');
       process.exit(0);
-    } else if (answer === 'o' || answer === 'overwrite') {
-      installMode = 'overwrite';
-      console.log('');
-      console.log('Installing in overwrite mode...');
-    } else {
-      // Default: merge (empty, 'm', 'merge', etc.)
+    } else if (answer === 'm' || answer === 'merge') {
       installMode = 'merge';
       console.log('');
       console.log('Installing in merge mode (keeping existing files)...');
+    } else {
+      // Default: update (empty, 'u', 'update', etc.)
+      installMode = 'update';
+      console.log('');
+      console.log('Installing in update mode (updating existing files, keeping custom files)...');
     }
   }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeongjaeyou/claude-code-config",
-  "version": "0.6.0",
+  "version": "0.7.1",
   "description": "Claude Code CLI custom commands, agents, and skills",
   "bin": {
     "claude-code-config": "./bin/cli.js"