@yeongjaeyou/claude-code-config 0.18.6 → 0.19.0

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

@@ -2,6 +2,7 @@
 name: web-researcher
 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. (project)
 model: inherit
+skills: code-explorer
 ---
 
 # Web Research Expert Agent
@@ -53,7 +54,7 @@ Detect keywords in the prompt to determine execution mode:
 ### Required Fields (Quick & Deep)
 
 ```yaml
-platform: github | reddit | hf | stackoverflow | docs | arxiv | web
+platform: github | reddit | hf | stackoverflow | docs | arxiv | web | twitter | threads
 query_used: "actual search query used"
 findings:
   - title: "finding title"
@@ -98,6 +99,8 @@ suggested_followups:
 | **DeepWiki** | In-depth GitHub repo analysis | MCP |
 | **arXiv** | Academic papers | WebSearch |
 | **General Web** | Blogs, tutorials | WebSearch / Firecrawl |
+| **Twitter/X** | Viral content, real-time buzz, tech announcements | WebSearch |
+| **Threads** | Meta ecosystem discussions, cross-platform takes | WebSearch |
 
 ---
 
@@ -161,7 +164,8 @@ Parallel execution (Task tool, run_in_background: true):
 ├── Task: HuggingFace search
 ├── Task: Reddit + StackOverflow search
 ├── Task: Context7 official docs
-└── Task: arXiv + general web (if needed)
+├── Task: arXiv + general web (if needed)
+└── Task: Twitter/X + Threads (for trending/viral topics)
 ```
 
 **Execution policy:**
@@ -189,7 +193,8 @@ Parallel execution (all platforms):
 ├── Task: HuggingFace Agent (structured output)
 ├── Task: Community Agent - Reddit/SO (structured output)
 ├── Task: Official Docs Agent - Context7/DeepWiki (structured output)
-└── Task: Academic Agent - arXiv (structured output)
+├── Task: Academic Agent - arXiv (structured output)
+└── Task: Social Media Agent - Twitter/X + Threads (structured output)
 ```
 
 **Each Task prompt MUST include:**
@@ -318,6 +323,8 @@ Terminate when any of the following is met:
 | Confirmed only in official docs (Context7/DeepWiki) | **HIGH** |
 | Single GitHub issue/PR | **MEDIUM** |
 | Single Reddit/SO answer | **MEDIUM** |
+| Viral Twitter/X thread (high engagement) | **MEDIUM** |
+| Single Threads post | **LOW** |
 | Date older than 2 years | **LOW** |
 | No source URL | **EXCLUDE** |
 
@@ -477,6 +484,62 @@ mcp__firecrawl__firecrawl_search
 
 ---
 
+### 9. Twitter/X Search (WebSearch)
+
+```
+WebSearch: site:x.com OR site:twitter.com {query} {year}
+```
+
+**Query patterns:**
+
+| Goal | Query Format |
+|------|--------------|
+| From specific user | `site:x.com from:username {query}` |
+| High engagement posts | `site:x.com {query} "likes" OR "retweets"` |
+| Tech announcements | `site:x.com {library} release OR launch {year}` |
+| Discussions/threads | `site:x.com {query} thread` |
+
+**Useful tech accounts:**
+
+- AI/ML: @_akhaliq, @AndrewYNg, @ylecun, @kaboranalytics
+- Open source: @GitHub, @HuggingFace
+- Dev tools: @veraborger, @raaborger
+
+**Caveats:**
+
+- WebSearch only indexes public, crawlable tweets
+- Real-time trending data not available via WebSearch
+- Rate-limited content may not appear in results
+
+---
+
+### 10. Threads Search (WebSearch)
+
+```
+WebSearch: site:threads.net {query} {year}
+```
+
+**Query patterns:**
+
+| Goal | Query Format |
+|------|--------------|
+| From specific user | `site:threads.net/@username {query}` |
+| Meta/Instagram topics | `site:threads.net {meta OR instagram} {query}` |
+
+**Best for:**
+
+- Cross-posted content from Instagram creators
+- Meta ecosystem updates and discussions
+- Alternative perspectives to Twitter/X
+
+**Caveats:**
+
+- Indexing coverage is more limited than Twitter/X
+- Newer platform, less historical data available
+- Search latency for recent posts
+
+---
+
 ## Report Template
 
 ```markdown
@@ -554,5 +617,6 @@ mcp__firecrawl__firecrawl_search
 ## File Management
 
 - Keep intermediate data in memory only
-- **Final deliverable**: Single `research-report-{topic-slug}.md` file only
+- **Output directory**: `docs/research/`
+- **Final deliverable**: Single `docs/research/research-report-{topic-slug}.md` file
 - Do not create temporary files or intermediate drafts

package/.claude/commands/gh/auto-review-loop.md

@@ -51,7 +51,7 @@ MAX_ITERATIONS=10
 
 ### Step 2: Wait for All Checks
 
-`gh pr checks`로 CodeRabbit과 Actions 상태를 한 번에 확인.
+Check CodeRabbit and Actions status at once with `gh pr checks`.
 
 ```bash
 wait_for_all_checks() {
@@ -81,7 +81,7 @@ wait_for_all_checks() {
 
 ### Step 3: Check Unresolved Threads (GraphQL)
 
-CodeRabbit 리뷰 코멘트 중 미해결 건수 확인. This is the ground truth.
+Check unresolved CodeRabbit review comment count. This is the ground truth.
 
 ```bash
 check_unresolved_threads() {

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

@@ -14,9 +14,9 @@ Break down large work items into manageable, independent issues. Follow project
    - Detect test frameworks (jest.config.*, pytest.ini, vitest.config.*, pyproject.toml, etc.)
 3. **Check TDD applicability** (if user hasn't specified):
    - Analyze work type: code implementation vs docs/infra/config
-   - If test framework detected + code work → Ask: "TDD 기반으로 이슈 생성하시겠어요?"
-   - If no test framework → Inform: "TDD 반영이 필요없습니다. (이유: 테스트 프레임워크 미감지)"
-   - If non-code work (docs/infra) → Inform: "TDD 반영이 필요없습니다. (이유: 비코드 작업)"
+   - If test framework detected + code work → Ask: "Create issues with TDD approach?"
+   - If no test framework → Inform: "TDD not required. (Reason: No test framework detected)"
+   - If non-code work (docs/infra) → Inform: "TDD not required. (Reason: Non-code work)"
    - If TDD selected: Add `<!-- TDD: enabled -->` marker to each issue body
 4. Analyze work: Understand core requirements and objectives
 5. Decompose work: Split major tasks into smaller, manageable sub-tasks or issues. **Aim for optimal count over excessive issues (keep it manageable)**
@@ -164,14 +164,14 @@ Always include an ASCII diagram in the issue body to visualize the execution flo
 
 ## Verification Guidelines
 
-이슈 작업 완료 시 반드시 실행 검증 수행:
+Verification is mandatory when issue work is complete:
 
-| 작업 유형 | 검증 방법 |
-|-----------|-----------|
-| Python 코드 | `python -m py_compile file.py` + 실제 실행 |
-| TypeScript/JS | `tsc --noEmit` 또는 빌드 |
-| API/서버 | 엔드포인트 호출 테스트 |
-| CLI 도구 | 기본 명령어 실행 |
-| 설정 파일 | 관련 도구로 로드 확인 |
+| Work Type | Verification Method |
+|-----------|---------------------|
+| Python code | `python -m py_compile file.py` + actual execution |
+| TypeScript/JS | `tsc --noEmit` or build |
+| API/Server | Endpoint call test |
+| CLI tools | Run basic commands |
+| Config files | Verify loading with related tools |
 
-**파일만 생성하고 실행 검증 없이 완료 처리 금지**
+**Never mark complete if only files are created without execution verification**

package/.claude/commands/gh/resolve-and-review.md

@@ -4,7 +4,7 @@ description: Full issue resolution pipeline with automated code review
 
 # Resolve and Review
 
-Issue 해결부터 CodeRabbit 리뷰 처리까지 자동화된 전체 파이프라인.
+Automated full pipeline from issue resolution to CodeRabbit review handling.
 
 ## Arguments
 

package/.claude/guidelines/id-reference.md

@@ -20,7 +20,7 @@ Reference for different ID formats used across GitHub and TaskMaster.
 
 ## Linking GitHub and TaskMaster
 
-- PR body: `Task Master 참조: task N` or `TaskMaster: task N`
+- PR body: `TaskMaster: task N` or `Task Master ref: task N`
 - Issue closing: `Closes #N` (GitHub Issue)
 
 ## Example
@@ -28,7 +28,7 @@ Reference for different ID formats used across GitHub and TaskMaster.
 ```
 PR #13: "feat: Add authentication"
 ├── Closes #1 (GitHub Issue)
-└── Task Master 참조: task 1
+└── TaskMaster: task 1
     ├── task 1.1 (subtask)
     └── task 1.2 (subtask)
 ```

package/.claude/guidelines/prd-guide.md

@@ -1,36 +1,36 @@
-# PRD 초안 템플릿
+# PRD Draft Template
 
-여기에 아이디어를 자유롭게 작성하세요.
-`/tm:convert-prd` 커맨드로 TaskMaster PRD 포맷으로 변환됩니다.
+Write your ideas freely here.
+Use `/tm:convert-prd` command to convert to TaskMaster PRD format.
 
 ---
 
-## 뭘 만들고 싶은지
+## What to Build
 
-(프로젝트 목적, 해결하려는 문제)
+(Project purpose, problem to solve)
 
 
 
-## 주요 기능
+## Key Features
 
-(만들고 싶은 기능들 나열)
+(List of features to build)
 
 
 
-## 기술 스택
+## Tech Stack
 
-(사용할 기술, 프레임워크 등)
+(Technologies, frameworks to use)
 
 
 
-## 만드는 순서
+## Build Order
 
-(먼저 만들 것, 나중에 만들 것)
+(What to build first, what to build later)
 
 
 
-## 기타
+## Notes
 
-(걱정되는 점, 참고사항 등)
+(Concerns, references, etc.)
 
 

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

@@ -23,7 +23,7 @@ Write like a human, not a chatbot. Applies to ALL text: responses, documentation
 - Over-explanation: Explaining obvious things, restating the question
 - Hedging phrases: "I think maybe...", "It might be possible that..."
 - Hollow transitions: "Now, let's...", "Moving on to...", "Next, we'll..."
-- Colon headers: "**항목:** 설명", "**Topic:** content" - just write naturally without label-colon-content structure
+- Colon headers: "**Item:** description", "**Topic:** content" - just write naturally without label-colon-content structure
 
 **DO:**
 - Get to the point immediately
@@ -150,11 +150,25 @@ When Built-in LSP returns "No LSP server available" error:
 | `insert_after_symbol` / `insert_before_symbol` | Add new code at precise locations |
 | `search_for_pattern` | Flexible regex search across codebase |
 
+**Session Management:**
+- Call `activate_project` at the start of each new conversation session
+- Once activated, remains active for the entire session
+- Prompt: "activate serena" or "serena activate project"
+
+**Onboarding & Memory:**
+- Onboarding: Run once per project initial setup (`onboarding` tool)
+- Indexing: LSP-based real-time analysis, no periodic refresh needed
+- Memory updates (`edit_memory`): Only when structure changes
+  - New modules/adapters added
+  - Architecture patterns changed
+  - Build/test commands modified
+
 **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
+5. Never use Grep/Read before trying Serena tools first
 
 ### Self-Verification (MANDATORY)
 

package/.claude/hooks/notify_osc.sh

@@ -1,11 +1,11 @@
 #!/bin/bash
 # Claude Code OSC Notification Script
-# /dev/tty로 출력하여 터미널에 직접 전달
+# Output to /dev/tty to deliver directly to terminal
 
-# stdin에서 JSON 읽기 (timeout으로 blocking 방지)
+# Read JSON from stdin (prevent blocking with timeout)
 INPUT=$(timeout 1 cat 2>/dev/null || true)
 
-# JSON 파싱
+# JSON parsing
 if command -v jq &>/dev/null && [ -n "$INPUT" ]; then
     SESSION_ID=$(echo "$INPUT" | jq -r '.session_id // empty' 2>/dev/null)
     CWD=$(echo "$INPUT" | jq -r '.cwd // empty' 2>/dev/null)
@@ -16,12 +16,12 @@ if command -v jq &>/dev/null && [ -n "$INPUT" ]; then
     FOLDER=$(basename "${CWD:-$PWD}" 2>/dev/null)
     SHORT_ID="${SESSION_ID:0:8}"
 
-    # 제목 구성
+    # Title construction
     TITLE="Claude"
     [ -n "$FOLDER" ] && TITLE="$TITLE - $FOLDER"
     [ -n "$SHORT_ID" ] && TITLE="$TITLE [$SHORT_ID]"
 
-    # 본문 구성
+    # Message body construction
     case "$EVENT" in
         "Stop")
             BODY="Task completed"
@@ -42,8 +42,8 @@ else
     BODY="${2:-Task completed}"
 fi
 
-# OSC 777 알림 출력 (OSC 9는 중복 알림 발생하므로 제외)
-# /dev/tty 사용 가능 시 직접 출력, 아니면 stdout
+# OSC 777 notification output (excluding OSC 9 as it causes duplicate notifications)
+# Output directly to /dev/tty if available, otherwise stdout
 {
     printf '\033]777;notify;%s;%s\007' "$TITLE" "$BODY"
 } > /dev/tty 2>/dev/null || {

package/.claude/skills/code-explorer/SKILL.md

@@ -16,53 +16,53 @@ To search and analyze code repositories across GitHub and Hugging Face platforms
 | **GitHub** | Repositories, Code | `gh` CLI |
 | **Hugging Face** | Models, Datasets, Spaces | `uvx hf` CLI + `huggingface_hub` API |
 
-## 검색 품질 원칙 (필수)
+## Search Quality Principles (Required)
 
-### 1. 현재 날짜 확인
+### 1. Verify Current Date
 
 ```bash
 date +%Y-%m-%d
 ```
-아래 예시의 연도는 참고용. 실제 검색 시 **현재 연도** 사용.
+Years in examples below are for reference. Use **current year** in actual searches.
 
-### 2. Long-tail Keywords 적용
+### 2. Apply Long-tail Keywords
 
-예시의 Short-tail을 그대로 쓰지 말고 확장:
+Don't use short-tail examples as-is, expand them:
 
-| 예시 (참고용) | 실제 검색 (Long-tail) |
-|---------------|----------------------|
-| `"object detection"` | `"open vocabulary object detection pytorch inference {현재연도}"` |
+| Example (Reference) | Actual Search (Long-tail) |
+|---------------------|---------------------------|
+| `"object detection"` | `"open vocabulary object detection pytorch inference {current_year}"` |
 | `"gradio demo"` | `"gradio image segmentation interactive demo huggingface"` |
 | `"qwen vl"` | `"qwen2-vl vision language model zero-shot example code"` |
 
-### 3. Multi-Query 적용
+### 3. Apply Multi-Query
 
-한 번에 찾기 어려우면 **2-3개 관점**으로 검색:
+If hard to find at once, search from **2-3 perspectives**:
 
 ```bash
-# 모델명 중심
+# Model name focus
 gh search repos "qwen2-vl" --sort stars
 
-# 기능 중심
+# Feature focus
 gh search repos "vision language open vocabulary detection" --sort stars
 
-# 구현 중심
+# Implementation focus
 gh search repos "vl model gradio demo inference" --sort stars
 ```
 
-### 4. 필터 활용
+### 4. Use Filters
 
 ```bash
-# 최신 + 품질 필터 (현재 연도 적용)
-gh search repos "keyword" stars:>50 pushed:>{현재연도-1}-01-01 --language python
+# Recent + quality filter (apply current year)
+gh search repos "keyword" stars:>50 pushed:>{current_year-1}-01-01 --language python
 ```
 
-### 5. 검색 전 체크리스트
+### 5. Pre-Search Checklist
 
-- [ ] 현재 날짜 확인했는가?
-- [ ] Short-tail을 Long-tail로 변환했는가?
-- [ ] 필요시 2-3개 변형 쿼리로 검색했는가?
-- [ ] 적절한 필터(언어, 스타, 날짜) 적용했는가?
+- [ ] Verified current date?
+- [ ] Converted short-tail to long-tail?
+- [ ] Searched with 2-3 query variations if needed?
+- [ ] Applied appropriate filters (language, stars, date)?
 
 ---
 

package/.claude/skills/interview-methodology/SKILL.md

@@ -0,0 +1,196 @@
+---
+name: interview-methodology
+description: This skill should be used when conducting in-depth user interviews, "gathering requirements", "interview me", "ask me questions", "understand my needs before implementing", "spec-based development", or when preparing comprehensive specifications before implementation.
+version: 0.2.0
+---
+
+# Interview Methodology
+
+A comprehensive framework for conducting thorough requirement-gathering interviews that uncover hidden needs, constraints, and edge cases.
+
+## Trigger Examples
+
+<example>
+Context: User wants to implement a new feature without detailed spec
+user: "I want to add dark mode to my app"
+assistant: Loads interview-methodology skill to thoroughly understand requirements first.
+<commentary>
+Feature request without detailed specification - perfect trigger for deep interview before implementation.
+</commentary>
+</example>
+
+<example>
+Context: User explicitly requests interview-style requirements gathering
+user: "Interview me about this feature before you start coding"
+assistant: Loads interview-methodology skill to conduct thorough interview.
+<commentary>
+Explicit interview request - direct trigger.
+</commentary>
+</example>
+
+## Critical Rules
+
+1. **Use AskUserQuestion tool** for all questions - never just ask in plain text
+2. **Questions must NOT be obvious** - avoid basic questions the user has already answered
+3. **Continue interviewing until complete** - don't stop after 2-3 questions
+4. **Probe deeper on every answer** - each response should spawn follow-up questions
+5. **Write the final spec to a file** when the interview is complete
+
+## Core Principle: Non-Obvious Questions
+
+**Never ask questions the user has already implicitly answered.** Instead, probe the gaps, assumptions, and unstated requirements.
+
+### Bad Questions (Obvious)
+- "What feature do you want?" (they already told you)
+- "Do you want it to work well?" (obviously yes)
+- "Should it be fast?" (obviously yes)
+
+### Good Questions (Non-Obvious)
+- "What happens when X fails? Should it retry, fail silently, or notify?"
+- "Who else might use this besides you? Do they have different needs?"
+- "What's the worst thing that could happen if this feature misbehaves?"
+
+## Question Framework by Category
+
+### 1. Technical Implementation
+- What existing systems does this need to integrate with?
+- Are there performance constraints (response time, memory, etc.)?
+- What's the expected scale? 10 users or 10,000?
+- Are there security or compliance requirements?
+- Should this work offline? On mobile?
+- What happens during network failures or timeouts?
+
+### 2. User Interface & Experience
+- Who are the different user personas interacting with this?
+- What's the primary device/platform? Secondary?
+- Are there accessibility requirements?
+- What's the user's technical proficiency level?
+- What should happen on errors - technical message or friendly guidance?
+- Are there existing UI patterns in the app this should follow?
+
+### 3. Edge Cases & Error Handling
+- What inputs are considered invalid? How should they be handled?
+- What if the user does X when they should do Y?
+- What's the behavior when data is missing or malformed?
+- How should concurrent/conflicting operations be handled?
+- What are the failure modes and recovery strategies?
+
+### 4. Constraints & Tradeoffs
+- What's more important: speed of delivery or completeness?
+- Are there budget/resource limitations?
+- What can we cut if we run out of time?
+- What's the minimum viable version vs. ideal version?
+- Are there dependencies on other teams or systems?
+
+### 5. Business Context
+- Why is this feature needed now?
+- What problem does this solve for the business?
+- How will success be measured?
+- What's the cost of NOT doing this?
+- Are there regulatory or legal considerations?
+
+## Interview Flow
+
+### Phase 1: Context Gathering (2-3 questions)
+Understand the big picture before diving into details.
+- What triggered this request?
+- What's the current pain point?
+- What does success look like?
+
+### Phase 2: Deep Dive (5-10 questions)
+Systematically cover each category above. Use AskUserQuestion with multiple-choice options when possible to make answering easier.
+
+### Phase 3: Edge Case Exploration (3-5 questions)
+Focus on "what if" scenarios. These often reveal the most important requirements.
+
+### Phase 4: Prioritization (2-3 questions)
+Help the user distinguish must-haves from nice-to-haves.
+
+### Phase 5: Validation (1-2 questions)
+Summarize understanding and confirm before finalizing.
+
+## AskUserQuestion Best Practices
+
+### Structure Questions with Options
+```
+Question: "How should the system handle authentication failures?"
+Options:
+1. Show error and retry (simple)
+2. Lock account after 3 attempts (secure)
+3. Send email notification (audit trail)
+4. Custom handling...
+```
+
+### Use multiSelect for Non-Exclusive Choices
+```
+Question: "Which platforms need to be supported?"
+multiSelect: true
+Options:
+1. Web browser
+2. iOS app
+3. Android app
+4. Desktop app
+```
+
+### Provide Context in Descriptions
+Each option should explain implications, not just the choice itself.
+
+## Interview Completion
+
+When you've gathered sufficient information:
+1. Summarize all requirements back to the user
+2. Ask for confirmation using AskUserQuestion
+3. Write the comprehensive spec to `SPEC.md` or a user-specified file
+4. The spec should be detailed enough for implementation without further questions
+
+## Spec Output Format
+
+After interview completion, write a spec file with:
+
+```markdown
+# Feature Specification: [Feature Name]
+
+## Overview
+[1-2 sentence summary]
+
+## User Stories
+- As a [user type], I want [goal] so that [benefit]
+
+## Requirements
+
+### Must Have (P0)
+- [ ] Requirement 1
+- [ ] Requirement 2
+
+### Should Have (P1)
+- [ ] Requirement 3
+
+### Nice to Have (P2)
+- [ ] Requirement 4
+
+## Technical Constraints
+- [List technical requirements and limitations]
+
+## UI/UX Requirements
+- [List interface requirements]
+
+## Edge Cases
+| Scenario | Expected Behavior |
+|----------|------------------|
+| Case 1   | Behavior 1       |
+
+## Out of Scope
+- [Explicitly list what this feature does NOT include]
+
+## Open Questions
+- [Any unresolved items for future discussion]
+```
+
+## Interviewing Anti-Patterns to Avoid
+
+1. **Assuming you know best** - Always verify assumptions
+2. **Leading questions** - Don't bias the answer
+3. **Stopping too early** - Keep probing until truly complete
+4. **Ignoring contradictions** - Surface and resolve conflicts
+5. **Forgetting to summarize** - Always validate understanding
+6. **Skipping prioritization** - Everything can't be P0