@yeongjaeyou/claude-code-config 0.18.7 → 0.20.0

package/.claude/agents/issue-resolver.md

@@ -33,8 +33,13 @@ gh issue view $ISSUE_NUMBER --json title,body,comments,milestone
 
 ### 3. Create Branch
 
+**Branch naming**: `{type}/{issue-number}-{short-description}`
+- `type`: From labels (`bug`->`fix`, `enhancement`->`feat`) or default `feat`
+- `short-description`: Slugified title (lowercase, hyphens, max 50 chars)
+
 ```bash
-git checkout -b issue-$ISSUE_NUMBER main
+# Example: fix/42-login-validation or feat/15-dark-mode
+git checkout -b $BRANCH_NAME main
 git submodule update --init --recursive
 ```
 

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/resolve-issue.md

@@ -24,7 +24,11 @@ Act as an expert developer who systematically analyzes and resolves GitHub issue
      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.
+3. **Create Branch**: Create and checkout a new branch from `main` or `master` branch.
+   - **Branch naming convention**: `{type}/{issue-number}-{short-description}`
+     - `type`: Infer from issue labels (`bug` -> `fix`, `enhancement`/`feature` -> `feat`) or title prefix. Default to `feat` if unclear.
+     - `short-description`: Slugify issue title (lowercase, spaces to hyphens, max 50 chars, remove special chars)
+     - Examples: `fix/42-login-validation-error`, `feat/15-add-dark-mode`, `refactor/8-cleanup-auth`
    - **Initialize submodules**: When using worktree, run `git submodule update --init --recursive`
 
 4. **Update GitHub Project Status (Optional)**

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

@@ -111,7 +111,7 @@ Ask via AskUserQuestion about local branch deletion:
 
 ```bash
 # If deletion desired
-git branch -d <headRefName>  # e.g., issue-1
+git branch -d <headRefName>  # e.g., fix/1-login-bug
 ```
 
 ### 7. Check Next Task
@@ -171,7 +171,7 @@ TaskMaster Status:
 - Subtasks: all complete (1.1, 1.2, 1.3)
 
 Cleanup:
-- [x] Local branch deleted: issue-<N>
+- [x] Local branch deleted: {type}/<N>-{slug}
 - [x] TaskMaster status updated
 - [ ] CLAUDE.md updated (no changes)
 - [ ] AGENTS.md updated (no changes / not found)

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

@@ -132,12 +132,13 @@ task-master show $TASK_ID
 ```bash
 # Create new branch from main or master
 git checkout main && git pull origin main
-git checkout -b issue-$ISSUE_NUMBER
+git checkout -b {type}/$ISSUE_NUMBER-{short-description}
 ```
 
-**Branch naming convention:**
-- `issue-1` (for GitHub Issue #1 work)
-- `issue-1-subtask-1.2` (for specific subtask only, optional)
+**Branch naming convention:** `{type}/{issue-number}-{short-description}`
+- `type`: From labels (`bug`->`fix`, `enhancement`->`feat`) or default `feat`
+- `short-description`: Slugified title (lowercase, hyphens, max 50 chars)
+- Examples: `fix/1-login-validation`, `feat/13-dark-mode`
 
 ### 5. Process Subtasks Sequentially
 
@@ -196,8 +197,8 @@ git commit -m "feat: [Task $TASK_ID] Task title
 Task Master reference: task $TASK_ID
 Closes #$ISSUE_NUMBER"
 
-# Push
-git push -u origin issue-$ISSUE_NUMBER
+# Push (use the branch name created in step 4)
+git push -u origin $BRANCH_NAME
 ```
 
 ### 8. Create PR

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

@@ -7,7 +7,7 @@ Reference for different ID formats used across GitHub and TaskMaster.
 | Type | Format | Example |
 |------|--------|---------|
 | PR/Issue number | `#N` | `#1`, `#13` |
-| Branch | `issue-N` | `issue-1`, `feature-auth` |
+| Branch | `{type}/{N}-{slug}` | `fix/1-login-bug`, `feat/13-dark-mode` |
 
 > Note: PRs and Issues share the same namespace in GitHub.
 

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

@@ -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/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

package/package.json

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