@yeongjaeyou/claude-code-config 0.23.0 → 0.24.0

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

@@ -60,12 +60,12 @@ findings:
   - title: "finding title"
     summary: "summary"
     url: "https://..."
-    date: "2024-01-15"
+    date: "2026-01-15"
     reliability: high | medium | low
 sources:
   - url: "https://..."
     title: "source title"
-    date: "2024-01-15"
+    date: "2026-01-15"
     platform: "github"
 confidence: 0.8  # 0.0-1.0 (information sufficiency)
 ```
@@ -80,7 +80,7 @@ conflicts:
   - "Reddit recommends A, but official docs recommend B"
 suggested_followups:
   - platform: "arxiv"
-    query: "benchmark comparison 2024"
+    query: "benchmark comparison 2026"
     reason: "Need performance data"
 ```
 
@@ -345,8 +345,8 @@ When conflicts remain unresolved:
 
 | Source | Position | Date | Reliability |
 |--------|----------|------|-------------|
-| [Official Docs](URL) | Recommends approach A | 2024-01 | HIGH |
-| [Reddit](URL) | Approach B more practical | 2024-06 | MEDIUM |
+| [Official Docs](URL) | Recommends approach A | 2026-01 | HIGH |
+| [Reddit](URL) | Approach B more practical | 2025-06 | MEDIUM |
 
 **Analysis**: Official docs recommend A, but community finds B more effective in practice. Choose based on your situation.
 ```

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

@@ -19,7 +19,7 @@ Break down large work items into manageable, independent issues. Follow project
    - 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)**
+5. Decompose work: Split major tasks into **context-completable units** - each issue should be completable in a single Claude session without context switching. Group related features together rather than splitting by individual functions
 6. Analyze dependencies: Identify prerequisite tasks
 7. Suggest milestone name: Propose a milestone to group decomposed tasks
 8. Check related PRs (optional): Run `gh pr list --state closed --limit 20` for similar work references (skip if none)
@@ -33,6 +33,33 @@ Break down large work items into manageable, independent issues. Follow project
    - If project exists: Ask user via AskUserQuestion whether to add issues
    - If yes: Run `gh project item-add <project-number> --owner <owner> --url <issue-url>` for each issue
 
+## Issue Sizing Principle
+
+### Context-Completable Units
+Each issue should be designed to be **completable in a single Claude session**:
+
+- **Group related features** rather than splitting by individual functions
+- **Minimize context switching** - all necessary information should be within the issue
+- **Include implementation details** - specific enough that no external lookup is needed during execution
+
+### Sizing Guidelines
+
+| Good (Context-Completable) | Bad (Over-Fragmented) |
+|---------------------------|----------------------|
+| "Add user authentication with login/logout/session" | "Add login button", "Add logout button", "Add session handling" (3 separate issues) |
+| "Implement CRUD API for products" | "Add create endpoint", "Add read endpoint", "Add update endpoint", "Add delete endpoint" (4 separate issues) |
+| "Setup CI/CD pipeline with test and deploy stages" | "Add test stage", "Add deploy stage" (2 separate issues) |
+
+### Issue Content Depth
+Since issues are larger, content must be **more detailed**:
+
+1. **Implementation order** - numbered steps for execution sequence
+2. **File-by-file changes** - specific modifications per file
+3. **Code snippets** - key patterns or structures to implement
+4. **Edge cases** - known gotchas or considerations
+
+---
+
 ## Milestone Description Guidelines
 
 Milestone description must include:
@@ -59,12 +86,20 @@ Examples (vary by project, for reference only):
 
 **Purpose**: [Why this is needed]
 
-**Tasks**:
-- [ ] Specific requirement 1
-- [ ] Specific requirement 2
+**Implementation Steps** (in order):
+1. [ ] Step 1 - description with specific details
+2. [ ] Step 2 - description with specific details
+3. [ ] Step 3 - description with specific details
 
 **Files to modify**:
-- `path/filename` - Change description
+- `path/filename` - Specific change (add/modify/remove what)
+- `path/filename2` - Specific change with code pattern if needed
+
+**Key Implementation Details**:
+```
+// Include code snippets, patterns, or structures when helpful
+// This reduces need for external lookup during execution
+```
 
 **Completion criteria**:
 - [ ] Implementation complete (all tasks checked)

package/.claude/guidelines/ml-guidelines.md

@@ -47,6 +47,21 @@ img = annotator.annotate(img, detections)  # BGR colors on RGB image -> inverted
 plt.imshow(img)
 ```
 
+### Exception: Ultralytics YOLO
+
+Ultralytics YOLO handles BGR to RGB conversion internally. Do NOT manually convert before passing to YOLO.
+
+```python
+# Correct: Pass BGR directly to YOLO (handles conversion internally)
+img = cv2.imread(path)  # BGR
+results = yolo_model(img)  # YOLO converts BGR->RGB internally
+
+# Wrong: Manual conversion causes double conversion
+img = cv2.imread(path)
+img = cv2.cvtColor(img, cv2.COLOR_BGR2RGB)  # Unnecessary
+results = yolo_model(img)  # YOLO converts again -> RGB->BGR (inverted)
+```
+
 ## Ultralytics WandB Integration
 
 Ultralytics YOLO has WandB disabled by default.

package/.claude/hooks/auto-format-python.py

@@ -0,0 +1,53 @@
+#!/usr/bin/env python3
+"""Auto-fix Python files with ruff after Write/Edit operations."""
+
+import json
+import sys
+import subprocess
+import os
+
+
+def main():
+    """Main hook handler."""
+    try:
+        data = json.load(sys.stdin)
+    except json.JSONDecodeError:
+        sys.exit(0)
+
+    file_path = data.get("tool_input", {}).get("file_path")
+    if not file_path:
+        sys.exit(0)
+
+    # Only process Python files
+    if not file_path.endswith((".py", ".pyi")):
+        sys.exit(0)
+
+    # Skip if file doesn't exist
+    if not os.path.isfile(file_path):
+        sys.exit(0)
+
+    project_dir = os.environ.get("CLAUDE_PROJECT_DIR", os.getcwd())
+
+    try:
+        # Lint fix
+        subprocess.run(
+            ["uv", "run", "ruff", "check", "--fix", file_path],
+            cwd=project_dir,
+            capture_output=True,
+            timeout=30,
+        )
+        # Format
+        subprocess.run(
+            ["uv", "run", "ruff", "format", file_path],
+            cwd=project_dir,
+            capture_output=True,
+            timeout=30,
+        )
+    except (subprocess.TimeoutExpired, FileNotFoundError):
+        pass
+
+    sys.exit(0)
+
+
+if __name__ == "__main__":
+    main()

package/.claude/settings.json

@@ -10,6 +10,30 @@
                     }
                 ]
             }
+        ],
+        "PreToolUse": [
+            {
+                "matcher": "Edit|Write",
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "python3 -c \"import json,sys; p=json.load(sys.stdin).get('tool_input',{}).get('file_path',''); blocked=['.env','.env.local','package-lock.json','.git/','secrets']; sys.exit(2 if any(b in p for b in blocked) else 0)\"",
+                        "timeout": 5
+                    }
+                ]
+            }
+        ],
+        "PostToolUse": [
+            {
+                "matcher": "Edit|Write",
+                "hooks": [
+                    {
+                        "type": "command",
+                        "command": "python3 .claude/hooks/auto-format-python.py",
+                        "timeout": 60
+                    }
+                ]
+            }
         ]
     }
 }

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

@@ -140,11 +140,20 @@ Each option should explain implications, not just the choice itself.
 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
+3. Write the comprehensive spec to `.claude/spec/{YYYY-MM-DD}-{feature-name}.md`
+   - Date: Interview completion date (ISO format)
+   - Feature name: kebab-case (e.g., `dark-mode`, `user-authentication`)
+   - Create `.claude/spec/` directory if it doesn't exist
 4. The spec should be detailed enough for implementation without further questions
 
 ## Spec Output Format
 
+**File path**: `.claude/spec/{YYYY-MM-DD}-{feature-name}.md`
+
+**Examples**:
+- `.claude/spec/2026-01-20-dark-mode.md`
+- `.claude/spec/2026-01-20-api-rate-limiting.md`
+
 After interview completion, write a spec file with:
 
 ```markdown

package/package.json

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

package/.mcp.json

@@ -1,35 +0,0 @@
-{
-  "mcpServers": {
-    "mcpdocs": {
-      "type": "stdio",
-      "command": "npx",
-      "args": [
-        "@hapus/mcp-cache",
-        "uvx",
-        "--from",
-        "mcpdoc",
-        "mcpdoc",
-        "--urls",
-        "ClaudeCode:https://code.claude.com/docs/llms.txt",
-        "Cursor:https://docs.cursor.com/llms.txt",
-        "--allowed-domains",
-        "*"
-      ]
-    },
-    "deepwiki": {
-      "type": "http",
-      "url": "https://mcp.deepwiki.com/mcp"
-    },
-    "serena": {
-      "type": "stdio",
-      "command": "uvx",
-      "args": [
-        "--from",
-        "git+https://github.com/oraios/serena",
-        "serena-mcp-server",
-        "--enable-web-dashboard",
-        "false"
-      ]
-    }
-  }
-}