@yeongjaeyou/claude-code-config 0.5.1 → 0.6.0

package/README.md

@@ -14,7 +14,7 @@ A collection of custom slash commands, agents, and skills for Claude Code CLI.
 │   ├── commit-and-push.md       # Automate Git commit and push
 │   ├── council.md               # Consult multiple AI models (LLM Council)
 │   ├── edit-notebook.md         # Safely edit Jupyter Notebooks
-│   ├── plan.md                  # Create implementation plan (before coding)
+│   ├── generate-llmstxt.md      # Generate llms.txt from URL or directory
 │   ├── gh/
 │   │   ├── create-issue-label.md  # Create GitHub issue labels
 │   │   ├── decompose-issue.md     # Decompose large work into issues
@@ -25,21 +25,21 @@ A collection of custom slash commands, agents, and skills for Claude Code CLI.
 │       ├── convert-prd.md         # Convert PRD draft to TaskMaster format
 │       ├── post-merge.md          # TaskMaster-integrated post-merge cleanup
 │       ├── resolve-issue.md       # TaskMaster-based issue resolution
-│       ├── review-prd-with-codex.md # Review PRD with Codex
 │       └── sync-to-github.md      # Sync TaskMaster -> GitHub
 ├── guidelines/                  # Shared guidelines
 │   ├── work-guidelines.md       # Common work guidelines
 │   └── id-reference.md          # GitHub/TaskMaster ID reference
 ├── agents/                      # Custom agents
 │   ├── web-researcher.md        # Multi-platform web research
-│   ├── python-pro.md            # Python expert
-│   ├── generate-llmstxt.md      # Generate llms.txt
-│   └── langconnect-rag-expert.md # RAG-based document search
+│   └── python-pro.md            # Python expert
 └── skills/                      # Skills (reusable tool collections)
     ├── code-explorer/           # GitHub/HuggingFace code exploration
     │   ├── SKILL.md
     │   ├── scripts/
     │   └── references/
+    ├── feature-implementer/     # TDD-based feature planning
+    │   ├── SKILL.md
+    │   └── plan-template.md
     ├── notion-md-uploader/      # Upload Markdown to Notion
     │   ├── SKILL.md
     │   ├── scripts/
@@ -55,10 +55,10 @@ A collection of custom slash commands, agents, and skills for Claude Code CLI.
 
 | Command | Description |
 |---------|-------------|
-| `/plan` | Analyze requirements and create implementation plan (no coding) |
 | `/commit-and-push` | Analyze changes and commit with Conventional Commits format |
 | `/code-review` | Process external code review results and apply auto-fixes |
 | `/edit-notebook` | Safely edit Jupyter Notebook files with NotebookEdit tool |
+| `/generate-llmstxt` | Generate llms.txt from URL or local directory |
 | `/ask-deepwiki` | Deep query GitHub repositories via DeepWiki MCP |
 | `/ask-codex` | Request code review via Codex MCP (with Claude cross-check) |
 | `/ask-gemini` | Request code review via Gemini CLI (with Claude cross-check) |
@@ -81,7 +81,6 @@ 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/review-prd-with-codex` | Review PRD with Codex MCP and Claude cross-check |
 | `/tm/post-merge` | TaskMaster status update and branch cleanup after PR merge |
 
 ## Agents
@@ -90,8 +89,6 @@ A collection of custom slash commands, agents, and skills for Claude Code CLI.
 |-------|-------------|
 | `web-researcher` | Multi-platform tech research (Reddit, GitHub, SO, HF, arXiv, etc.) |
 | `python-pro` | Python advanced features expert (decorators, generators, async/await) |
-| `generate-llmstxt` | Generate llms.txt documentation from websites or local directories |
-| `langconnect-rag-expert` | Retrieve and synthesize information from document collections |
 
 ## Skills
 
@@ -107,6 +104,15 @@ python scripts/search_github.py "object detection" --limit 10
 python scripts/search_huggingface.py "qwen vl" --type models
 ```
 
+### feature-implementer
+
+TDD-based feature planning with quality gates.
+
+- Phase-based plans with 1-4 hour increments
+- Test-First Development (Red-Green-Refactor)
+- Quality gates before each phase transition
+- Risk assessment and rollback strategies
+
 ### notion-md-uploader
 
 Upload Markdown files to Notion pages with full formatting support.
@@ -195,8 +201,8 @@ cp node_modules/@yeongjaeyou/claude-code-config/.mcp.json .
 ## Usage Examples
 
 ```bash
-# Create implementation plan
-/plan implement new authentication system
+# Generate llms.txt from website
+/generate-llmstxt https://docs.example.com
 
 # Commit and push
 /commit-and-push src/auth.ts src/utils.ts
@@ -210,11 +216,10 @@ cp node_modules/@yeongjaeyou/claude-code-config/.mcp.json .
 
 ## Key Features
 
-### `/plan` - Implementation Planning
-- Understand requirements intent (ask questions if unclear)
-- Investigate and understand relevant codebase
-- Create step-by-step execution plan
-- **No immediate coding - plan only**
+### `/generate-llmstxt` - LLM Documentation
+- Generate llms.txt from URL or local directory
+- Use Firecrawl MCP for web scraping
+- Organize content into logical sections
 
 ### `/commit-and-push` - Git Automation
 - Follow Conventional Commits format (feat, fix, refactor, docs, etc.)
@@ -236,6 +241,11 @@ cp node_modules/@yeongjaeyou/claude-code-config/.mcp.json .
 - Official documentation via Context7/DeepWiki
 - Auto-generate research reports
 
+### `feature-implementer` Skill
+- TDD-based feature planning with quality gates
+- Phase-based delivery (1-4 hours per phase)
+- Risk assessment and rollback strategies
+
 ### `code-explorer` Skill
 - GitHub repository/code search via `gh` CLI
 - Hugging Face model/dataset/Spaces search via `huggingface_hub` API

package/bin/cli.js

@@ -8,44 +8,45 @@ const readline = require('readline');
 const pkg = require('../package.json');
 const args = process.argv.slice(2);
 
-// 설치 대상 폴더 (사용자 데이터가 아닌 것들만)
-const INSTALL_FOLDERS = ['commands', 'agents', 'skills'];
+// Installation target folders (non-user data only)
+const INSTALL_FOLDERS = ['commands', 'agents', 'skills', 'guidelines'];
 
-// 옵션 파싱
+// Parse options
 const isGlobal = args.includes('--global') || args.includes('-g');
 const showHelp = args.includes('--help') || args.includes('-h');
 const showVersion = args.includes('--version') || args.includes('-v');
 
-// 버전 출력
+// Version output
 if (showVersion) {
   console.log(pkg.version);
   process.exit(0);
 }
 
-// 도움말 출력
+// Help output
 if (showHelp) {
   console.log(`
 Claude Code Config v${pkg.version}
 
-사용법:
-  npx @yeongjaeyou/claude-code-config [옵션]
+Usage:
+  npx @yeongjaeyou/claude-code-config [options]
 
-옵션:
-  -g, --global   전역 설치 (~/.claude/)
-  -h, --help     도움말 출력
-  -v, --version  버전 출력
+Options:
+  -g, --global   Global install (~/.claude/)
+  -h, --help     Show help
+  -v, --version  Show version
 
-예시:
-  npx @yeongjaeyou/claude-code-config          # 현재 프로젝트에 설치
-  npx @yeongjaeyou/claude-code-config --global # 전역 설치
+Examples:
+  npx @yeongjaeyou/claude-code-config          # Install to current project
+  npx @yeongjaeyou/claude-code-config --global # Global install
 
-설치되는 폴더:
-  - commands/  : 슬래시 커맨드
-  - agents/    : 커스텀 에이전트
-  - skills/    : 스킬 (재사용 가능한 도구 모음)
+Installed folders:
+  - commands/   : Slash commands
+  - agents/     : Custom agents
+  - skills/     : Skills (reusable tool collections)
+  - guidelines/ : Shared guidelines
 
-참고:
-  --global 설치 시 기존 사용자 데이터(settings.json, history.jsonl 등)는 보존됩니다.
+Note:
+  With --global install, existing user data (settings.json, history.jsonl, etc.) is preserved.
 `);
   process.exit(0);
 }
@@ -56,14 +57,14 @@ const dest = isGlobal
   : path.join(process.cwd(), '.claude');
 
 /**
- * 사용자에게 질문하고 답변을 받는다
- * @param {string} question - 질문 내용
- * @returns {Promise<string>} - 사용자 답변
+ * Ask user a question and get answer
+ * @param {string} question - Question content
+ * @returns {Promise<string>} - User answer
  */
 function askQuestion(question) {
-  // 비대화형 환경 감지 (CI/CD, 파이프라인 등)
+  // Detect non-interactive environment (CI/CD, pipelines, etc.)
   if (!process.stdin.isTTY) {
-    console.log('비대화형 환경이 감지되었습니다. 기본값(merge)을 사용합니다.');
+    console.log('Non-interactive environment detected. Using default (merge).');
     return Promise.resolve('merge');
   }
 
@@ -81,8 +82,8 @@ function askQuestion(question) {
 }
 
 /**
- * 기존 설치 폴더 확인
- * @returns {string[]} - 존재하는 폴더 목록
+ * Check existing installation folders
+ * @returns {string[]} - List of existing folders
  */
 function checkExistingFolders() {
   const existing = [];
@@ -96,22 +97,22 @@ function checkExistingFolders() {
 }
 
 /**
- * 폴더 복사 (재귀적)
- * @param {string} src - 소스 경로
- * @param {string} dst - 대상 경로
- * @param {boolean} mergeMode - 병합 모드 여부
+ * Copy folder recursively
+ * @param {string} src - Source path
+ * @param {string} dst - Destination path
+ * @param {boolean} mergeMode - Whether to use merge mode
  */
 function copyFolder(src, dst, mergeMode = false) {
   if (!fs.existsSync(src)) {
     return;
   }
 
-  // 대상 폴더 생성
+  // Create destination folder
   if (!fs.existsSync(dst)) {
     try {
       fs.mkdirSync(dst, { recursive: true });
     } catch (err) {
-      throw new Error(`폴더 생성 실패: ${dst} - ${err.message}`);
+      throw new Error(`Failed to create folder: ${dst} - ${err.message}`);
     }
   }
 
@@ -124,21 +125,21 @@ function copyFolder(src, dst, mergeMode = false) {
     if (entry.isDirectory()) {
       copyFolder(srcPath, dstPath, mergeMode);
     } else {
-      // 병합 모드에서는 기존 파일 유지
+      // In merge mode, keep existing files
       if (mergeMode && fs.existsSync(dstPath)) {
         continue;
       }
       try {
         fs.copyFileSync(srcPath, dstPath);
       } catch (err) {
-        throw new Error(`파일 복사 실패: ${srcPath} -> ${dstPath} - ${err.message}`);
+        throw new Error(`Failed to copy file: ${srcPath} -> ${dstPath} - ${err.message}`);
       }
     }
   }
 }
 
 /**
- * 설치 대상 폴더만 선택적으로 복사
+ * Selectively copy installation target folders
  * @param {string} mode - 'merge' | 'overwrite'
  */
 function installFolders(mode) {
@@ -152,12 +153,12 @@ 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(`폴더 삭제 실패: ${dstFolder} - ${err.message}`);
+        throw new Error(`Failed to delete folder: ${dstFolder} - ${err.message}`);
       }
     }
 
@@ -166,7 +167,7 @@ function installFolders(mode) {
 }
 
 /**
- * 메인 함수
+ * Main function
  */
 async function main() {
   console.log('');
@@ -174,90 +175,91 @@ async function main() {
   console.log('==================');
   console.log('');
 
-  // 소스 폴더 존재 확인
+  // Check source folder exists
   if (!fs.existsSync(source)) {
-    console.error('오류: 소스 .claude/ 폴더를 찾을 수 없습니다.');
+    console.error('Error: Source .claude/ folder not found.');
     process.exit(1);
   }
 
-  // 설치 위치 안내
+  // Display installation location
   if (isGlobal) {
-    console.log('전역 설치 모드: ~/.claude/에 설치합니다.');
+    console.log('Global install mode: Installing to ~/.claude/');
   } else {
-    console.log('로컬 설치 모드: 현재 디렉토리에 설치합니다.');
+    console.log('Local install mode: Installing to current directory.');
   }
-  console.log(`설치 경로: ${dest}`);
+  console.log(`Install path: ${dest}`);
   console.log('');
 
-  // 대상 폴더 생성 (없으면)
+  // Create destination folder if not exists
   if (!fs.existsSync(dest)) {
     try {
       fs.mkdirSync(dest, { recursive: true });
     } catch (err) {
-      console.error(`오류: 대상 폴더를 생성할 수 없습니다: ${dest}`);
-      console.error(`상세: ${err.message}`);
+      console.error(`Error: Cannot create destination folder: ${dest}`);
+      console.error(`Details: ${err.message}`);
       process.exit(1);
     }
   }
 
-  // 기존 설치 폴더 확인
+  // Check existing installation folders
   const existingFolders = checkExistingFolders();
   let installMode = 'overwrite';
 
   if (existingFolders.length > 0) {
-    console.log('기존 설치 폴더가 발견되었습니다:');
+    console.log('Existing installation folders found:');
     existingFolders.forEach(folder => {
       console.log(`  - ${folder}/`);
     });
     console.log('');
 
     if (isGlobal) {
-      console.log('(사용자 데이터는 보존됩니다: settings.json, history.jsonl 등)');
+      console.log('(User data will be preserved: settings.json, history.jsonl, etc.)');
       console.log('');
     }
 
-    console.log('설치 옵션:');
-    console.log('  [m] merge     - 새 파일만 추가 (기존 파일 유지)');
-    console.log('  [o] overwrite - 위 폴더들만 덮어쓰기');
-    console.log('  [c] cancel    - 설치 취소');
+    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('');
 
-    const answer = await askQuestion('선택하세요 (m/o/c) [기본: m]: ');
+    const answer = await askQuestion('Choose (m/o/c) [default: m]: ');
 
     if (answer === 'c' || answer === 'cancel') {
-      console.log('설치가 취소되었습니다.');
+      console.log('Installation cancelled.');
       process.exit(0);
     } else if (answer === 'o' || answer === 'overwrite') {
       installMode = 'overwrite';
       console.log('');
-      console.log('덮어쓰기 모드로 설치합니다...');
+      console.log('Installing in overwrite mode...');
     } else {
-      // 기본값: merge (빈 값, 'm', 'merge' 등)
+      // Default: merge (empty, 'm', 'merge', etc.)
       installMode = 'merge';
       console.log('');
-      console.log('병합 모드로 설치합니다 (기존 파일 유지)...');
+      console.log('Installing in merge mode (keeping existing files)...');
     }
   }
 
-  // 폴더 설치
+  // Install folders
   installFolders(installMode);
 
   console.log('');
-  console.log('.claude/ 폴더가 성공적으로 설치되었습니다!');
+  console.log('.claude/ folder installed successfully!');
   console.log('');
-  console.log('설치된 내용:');
-  console.log('  - commands/  : 슬래시 커맨드');
-  console.log('  - agents/    : 커스텀 에이전트');
-  console.log('  - skills/    : 스킬 (재사용 가능한 도구 모음)');
+  console.log('Installed:');
+  console.log('  - commands/   : Slash commands');
+  console.log('  - agents/     : Custom agents');
+  console.log('  - skills/     : Skills (reusable tool collections)');
+  console.log('  - guidelines/ : Shared guidelines');
   console.log('');
 
   if (isGlobal) {
-    console.log('전역 설치가 완료되었습니다.');
-    console.log('모든 프로젝트에서 Claude Code 커맨드를 사용할 수 있습니다.');
+    console.log('Global installation complete.');
+    console.log('Claude Code commands are now available in all projects.');
   }
 }
 
 main().catch((error) => {
-  console.error('오류:', error.message);
+  console.error('Error:', error.message);
   process.exit(1);
 });

package/package.json

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

package/.claude/agents/generate-llmstxt.md

@@ -1,165 +0,0 @@
----
-name: generate-llmstxt
-description: Expert at generating llms.txt files from websites or local directories. Use when user requests to create llms.txt documentation from URLs or local folders.
-tools: Task, mcp__firecrawl__firecrawl_map, mcp__firecrawl__firecrawl_scrape, Bash, Read, Write, Glob, Grep
-model: sonnet
-color: orange
----
-
-You are an expert at creating llms.txt documentation files following the llms.txt standard specification.
-
-# Your Primary Responsibilities
-
-1. Generate well-structured llms.txt files from websites or local directories
-2. Follow the llms.txt format specification precisely
-3. Use parallel processing for efficient content gathering
-4. Summarize content concisely while preserving key information
-
-# llms.txt Format Specification
-
-The llms.txt file should contain:
-1. An H1 with the project/site name (required)
-2. An optional blockquote with a short project summary
-3. Optional detailed markdown sections
-4. Optional markdown sections with H2 headers listing URLs
-
-Example Format:
-```markdown
-# Title
-
-> Optional description goes here
-
-Optional details go here
-
-## Section name
-
-- [Link title](https://link_url): Optional link details
-
-## Optional
-
-- [Link title](https://link_url)
-```
-
-Key Guidelines:
-- Use concise, clear language
-- Provide brief, informative descriptions for linked resources (10-15 words max)
-- Avoid ambiguous terms or unexplained jargon
-- Group related links under appropriate section headings
-- Each description should be SPECIFIC to the content, not generic
-
-## URL Format Best Practices
-
-When documenting projects with official documentation:
-1. **Always prefer official web documentation URLs** over GitHub/repository URLs
-   - ✅ Good: `https://docs.example.com/guide.html`
-   - ❌ Avoid: `https://github.com/example/repo/blob/main/docs/guide.md`
-2. **Check for published documentation sites** even if source is on GitHub
-   - Many projects publish to readthedocs.io, GitHub Pages, or custom domains
-   - Example: TorchServe uses `https://pytorch.org/serve/` not GitHub URLs
-3. **Use HTML versions** when both .md and .html exist
-   - Published docs usually have .html extension
-   - Some sites append .html.md for markdown versions
-4. **Verify URL accessibility** before including in llms.txt
-
-# Workflow for URL Input
-
-When given a URL to generate llms.txt from:
-
-1. Use firecrawl_map to discover all URLs on the website
-2. Create multiple parallel Task agents to scrape each URL concurrently
-   - Each task should use firecrawl_scrape to fetch page content
-   - Each task should extract key information: page title, main concepts, important links
-3. Collect and synthesize all results
-4. Organize content into logical sections
-5. Generate the final llms.txt file following the specification
-
-Important: DO NOT use firecrawl_generate_llmstxt - build the llms.txt manually from scraped content.
-
-# Workflow for Local Directory Input
-
-When given a local directory path:
-
-1. **Comprehensive Discovery**: Use Bash (ls/find) or Glob to list ALL files
-   - Check main directory (e.g., `docs/`)
-   - IMPORTANT: Also check subdirectories (e.g., `docs/hardware_support/`)
-   - Use recursive listing to avoid missing files
-   - Example: `ls -1 /path/to/docs/*.md` AND `ls -1 /path/to/docs/*/*.md`
-
-2. **Verify Completeness**: Count total files and cross-reference
-   - Use `wc -l` to count total markdown files
-   - Compare against what's included in llms.txt
-   - Example: If docs/ has 36 files, ensure all 36 are considered
-
-3. Filter for documentation-relevant files (README, docs, markdown files, code files)
-
-4. Create parallel Task agents to read and analyze relevant files
-   - Each task should use Read to get file contents
-   - Each task should extract: file purpose, key functions/classes, important concepts
-
-5. Collect and synthesize all results
-
-6. Organize content into logical sections (e.g., "Core Modules", "Documentation", "Examples")
-
-7. Generate the final llms.txt file following the specification
-
-# Content Summarization Strategy
-
-For each page or file, extract:
-- Main purpose or topic
-- Key APIs, functions, or classes (for code)
-- Important concepts or features
-- Usage examples or patterns
-- Related resources
-
-**CRITICAL: Read actual content, don't assume!**
-- ✅ Good: "Configure batch size and delay for optimized throughput with dynamic batching"
-- ❌ Bad: "Information about batch inference configuration"
-- Each description MUST be based on actually reading the page/file content
-- Descriptions should be 10-15 words and SPECIFIC to that document
-- Avoid generic phrases like "documentation about X" or "guide for Y"
-- Include concrete details: specific features, APIs, tools, or concepts mentioned
-
-Keep descriptions brief (1-2 sentences per item) but informative and specific.
-
-# Section Organization
-
-Organize content into logical sections such as:
-- Documentation (for docs, guides, tutorials)
-- API Reference (for API documentation)
-- Examples (for code examples, tutorials)
-- Resources (for additional materials)
-- Tools (for utilities, helpers)
-
-Adapt section names to fit the content being documented.
-
-# Parallel Processing
-
-When processing multiple URLs or files:
-1. Create one Task agent per item (up to reasonable limits)
-2. Launch all tasks in a single message for parallel execution
-3. Wait for all tasks to complete before synthesis
-4. If there are too many items (>50), process in batches
-
-# Error Handling
-
-- If a URL cannot be scraped, note it and continue with others
-- If a file cannot be read, note it and continue with others
-- Always generate a llms.txt file even if some sources fail
-- Include a note in the output about any failures
-
-# Output
-
-Always write the generated llms.txt to a file named `llms.txt` in the current directory or a location specified by the user.
-
-Provide a summary of:
-- Number of sources processed
-- Number of sections created
-- Any errors or warnings
-- Location of the generated file
-
-# Important Constraints
-
-- Never use emojis in the generated llms.txt file
-- Keep descriptions concise and technical
-- Prioritize clarity and usefulness for LLMs
-- Follow the user's specific requirements if they provide any customization requests