npm - @yeongjaeyou/claude-code-config - Versions diffs - 0.5.0 → 0.5.2 - Mend

@yeongjaeyou/claude-code-config 0.5.0 → 0.5.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (9) hide show

package/.claude/commands/generate-llmstxt.md +49 -0
package/.claude/skills/feature-implementer/SKILL.md +317 -0
package/.claude/skills/feature-implementer/plan-template.md +605 -0
package/README.md +169 -129
package/package.json +1 -1
package/.claude/agents/generate-llmstxt.md +0 -165
package/.claude/agents/langconnect-rag-expert.md +0 -98
package/.claude/commands/plan.md +0 -26
package/.claude/commands/tm/review-prd-with-codex.md +0 -442

package/README.md CHANGED Viewed

@@ -1,146 +1,176 @@
 # Claude Code Config
-Claude Code CLI를 위한 커스텀 슬래시 커맨드, 에이전트, 스킬 모음입니다.
+A collection of custom slash commands, agents, and skills for Claude Code CLI.
-## 구조
+## Structure
 ```
 .claude/
-├── commands/                    # 슬래시 커맨드
-│   ├── ask-codex.md             # Codex MCP로 코드 검토 요청
-│   ├── ask-deepwiki.md          # DeepWiki로 GitHub 리포 심층 질의
-│   ├── ask-gemini.md            # Gemini CLI로 코드 검토 요청
-│   ├── code-review.md           # CodeRabbit 등 외부 리뷰 처리
-│   ├── commit-and-push.md       # Git 커밋 및 푸시 자동화
-│   ├── edit-notebook.md         # Jupyter Notebook 안전 편집
-│   ├── plan.md                  # 구현 계획 수립 (코드 작성 전)
+├── commands/                    # Slash commands
+│   ├── ask-codex.md             # Request code review via Codex MCP
+│   ├── ask-deepwiki.md          # Deep query GitHub repos via DeepWiki
+│   ├── ask-gemini.md            # Request code review via Gemini CLI
+│   ├── code-review.md           # Process external code reviews (CodeRabbit, etc.)
+│   ├── commit-and-push.md       # Automate Git commit and push
+│   ├── council.md               # Consult multiple AI models (LLM Council)
+│   ├── edit-notebook.md         # Safely edit Jupyter Notebooks
+│   ├── generate-llmstxt.md      # Generate llms.txt from URL or directory
 │   ├── gh/
-│   │   ├── create-issue-label.md  # GitHub 이슈 라벨 생성
-│   │   ├── decompose-issue.md     # 큰 작업을 이슈로 분해
-│   │   ├── init-project.md        # GitHub Project 보드 초기화
-│   │   ├── post-merge.md          # PR 머지 후 정리 작업
-│   │   └── resolve-issue.md       # GitHub 이슈 해결 워크플로우
+│   │   ├── create-issue-label.md  # Create GitHub issue labels
+│   │   ├── decompose-issue.md     # Decompose large work into issues
+│   │   ├── init-project.md        # Initialize GitHub Project board
+│   │   ├── post-merge.md          # Post-merge cleanup
+│   │   └── resolve-issue.md       # GitHub issue resolution workflow
 │   └── tm/
-│       ├── convert-prd.md         # PRD 초안을 TaskMaster 형식으로 변환
-│       ├── post-merge.md          # TaskMaster 연동 PR 머지 후 정리
-│       ├── resolve-issue.md       # TaskMaster 기반 이슈 해결
-│       ├── review-prd-with-codex.md # PRD를 Codex로 검토
-│       └── sync-to-github.md      # TaskMaster -> GitHub 동기화
-├── agents/                      # 커스텀 에이전트
-│   ├── web-researcher.md        # 다중 플랫폼 웹 리서치
-│   ├── python-pro.md            # Python 전문가
-│   ├── generate-llmstxt.md      # llms.txt 생성
-│   └── langconnect-rag-expert.md # RAG 기반 문서 검색
-└── skills/                      # 스킬 (재사용 가능한 도구 모음)
-    └── code-explorer/           # GitHub/HuggingFace 코드 탐색
+│       ├── convert-prd.md         # Convert PRD draft to TaskMaster format
+│       ├── post-merge.md          # TaskMaster-integrated post-merge cleanup
+│       ├── resolve-issue.md       # TaskMaster-based issue resolution
+│       └── 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
+└── 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/
+    │   └── references/
+    └── skill-creator/           # Guide for creating skills
         ├── SKILL.md
-        ├── scripts/
-        │   ├── search_github.py
-        │   └── search_huggingface.py
-        └── references/
-            ├── github_api.md
-            └── huggingface_api.md
+        └── scripts/
 ```
-## 슬래시 커맨드
+## Slash Commands
-### 일반 커맨드
+### General Commands
-| 커맨드 | 설명 |
-|--------|------|
-| `/plan` | 요구사항을 분석하고 코드 작성 전 구현 계획만 수립 |
-| `/commit-and-push` | 변경된 파일 분석 후 Conventional Commits 형식으로 커밋 및 푸시 |
-| `/code-review` | CodeRabbit 등 외부 코드 리뷰 결과를 분석하고 자동 수정 적용 |
-| `/edit-notebook` | Jupyter Notebook 파일을 NotebookEdit 도구로 안전하게 편집 |
-| `/ask-deepwiki` | DeepWiki MCP를 활용하여 GitHub 리포지토리에 심층 질의 |
-| `/ask-codex` | Codex MCP로 현재 작업 코드 검토 요청 (Claude cross-check 포함) |
-| `/ask-gemini` | Gemini CLI로 현재 작업 코드 검토 요청 (Claude cross-check 포함) |
+| Command | Description |
+|---------|-------------|
+| `/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) |
+| `/council` | Consult multiple AI models and synthesize collective wisdom |
-### GitHub 워크플로우 커맨드 (`/gh/`)
+### GitHub Workflow Commands (`/gh/`)
-| 커맨드 | 설명 |
-|--------|------|
-| `/gh/create-issue-label` | 프로젝트 구조 분석 후 적절한 GitHub 이슈 라벨 생성 |
-| `/gh/decompose-issue` | 큰 작업을 관리 가능한 독립적인 이슈들로 분해 |
-| `/gh/init-project` | GitHub Project 보드 초기화 및 설정 |
-| `/gh/post-merge` | PR 머지 후 브랜치 정리 및 CLAUDE.md 업데이트 |
-| `/gh/resolve-issue` | GitHub 이슈 번호를 받아 체계적으로 분석하고 해결 |
+| Command | Description |
+|---------|-------------|
+| `/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/resolve-issue` | Systematically analyze and resolve GitHub issues |
-### TaskMaster 연동 커맨드 (`/tm/`)
+### TaskMaster Integration Commands (`/tm/`)
-| 커맨드 | 설명 |
-|--------|------|
-| `/tm/convert-prd` | PRD 초안을 TaskMaster PRD 형식으로 변환 |
-| `/tm/sync-to-github` | TaskMaster tasks.json을 GitHub Issue/Milestone으로 동기화 |
-| `/tm/resolve-issue` | GitHub Issue를 TaskMaster subtask 단위로 체계적 해결 |
-| `/tm/review-prd-with-codex` | PRD를 Codex MCP로 검토하고 Claude가 cross-check |
-| `/tm/post-merge` | PR 머지 후 TaskMaster 상태 업데이트 및 브랜치 정리 |
+| Command | Description |
+|---------|-------------|
+| `/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 |
-## 에이전트
+## Agents
-| 에이전트 | 설명 |
-|----------|------|
-| `web-researcher` | 다중 플랫폼(Reddit, GitHub, SO, HF, arXiv 등)에서 기술 리서치 수행 |
-| `python-pro` | Python 고급 기능(데코레이터, 제너레이터, async/await) 전문가 |
-| `generate-llmstxt` | 웹사이트나 로컬 디렉토리에서 llms.txt 문서 생성 |
-| `langconnect-rag-expert` | RAG 기반 문서 컬렉션에서 정보 검색 및 종합 |
+| Agent | Description |
+|-------|-------------|
+| `web-researcher` | Multi-platform tech research (Reddit, GitHub, SO, HF, arXiv, etc.) |
+| `python-pro` | Python advanced features expert (decorators, generators, async/await) |
-## 스킬
+## Skills
 ### code-explorer
-GitHub와 Hugging Face에서 코드/모델/데이터셋을 검색하고 분석하는 스킬입니다.
+Search and analyze code/models/datasets on GitHub and Hugging Face.
 ```bash
-# GitHub 리포지토리 검색
+# Search GitHub repositories
 python scripts/search_github.py "object detection" --limit 10
-# Hugging Face 모델/데이터셋/Spaces 검색
+# Search Hugging Face models/datasets/Spaces
 python scripts/search_huggingface.py "qwen vl" --type models
 ```
-## 설치
+### feature-implementer
-### npx로 설치 (권장)
+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.
+- Headings, lists, code blocks, images, tables, callouts, todos
+- Automatic image uploads
+- Preserved formatting
+### skill-creator
+Guide for creating effective Claude Code skills.
+- Skill structure templates
+- Best practices
+- Validation scripts
+## Installation
+### Install with npx (Recommended)
 ```bash
-# 현재 프로젝트에 설치
+# Install to current project
 npx @yeongjaeyou/claude-code-config
-# 전역 설치 (모든 프로젝트에서 사용)
+# Global install (available in all projects)
 npx @yeongjaeyou/claude-code-config --global
 ```
-### 수동 설치
+### Manual Installation
 ```bash
-# 방법 1: 직접 복사
+# Method 1: Direct copy
 git clone https://github.com/YoungjaeDev/claude-code-config.git
 cp -r claude-code-config/.claude /path/to/your/project/
-# 방법 2: 심볼릭 링크
+# Method 2: Symbolic link
 ln -s /path/to/claude-code-config/.claude /path/to/your/project/.claude
 ```
-### CLI 옵션
+### CLI Options
 ```bash
-npx @yeongjaeyou/claude-code-config [옵션]
+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
 ```
-## MCP 서버 설정
+## MCP Server Configuration
-패키지에 포함된 `.mcp.json`을 프로젝트 루트에 복사하여 사용할 수 있습니다.
+The package includes `.mcp.json` that can be copied to your project root.
-### 전제조건
+### Prerequisites
-- **Node.js**: npx 명령어 사용
-- **Python uv**: [uv 설치](https://docs.astral.sh/uv/getting-started/installation/)
+- **Node.js**: For npx command
+- **Python uv**: [Install uv](https://docs.astral.sh/uv/getting-started/installation/)
   ```bash
   # macOS/Linux
   curl -LsSf https://astral.sh/uv/install.sh | sh
@@ -149,68 +179,78 @@ npx @yeongjaeyou/claude-code-config [옵션]
   powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
   ```
-### 포함된 MCP 서버
+### Included MCP Servers
-| 서버 | 설명 | API 키 |
-|------|------|--------|
-| mcpdocs | Claude Code, Cursor 문서 검색 (mcp-cache 래퍼) | 불필요 |
-| deepwiki | GitHub 리포지토리 문서화 질의 | 불필요 |
-| serena | LSP 기반 코드 분석 도구 | 불필요 |
+| Server | Description | API Key |
+|--------|-------------|---------|
+| mcpdocs | Claude Code, Cursor docs search (mcp-cache wrapper) | Not required |
+| deepwiki | GitHub repository documentation query | Not required |
+| serena | LSP-based code analysis tool | Not required |
-### 사용 방법
+### Usage
 ```bash
-# .mcp.json 복사
+# Copy .mcp.json
 cp node_modules/@yeongjaeyou/claude-code-config/.mcp.json .
-# 또는 기존 .mcp.json이 있는 경우 내용 병합
+# Or merge contents if you have existing .mcp.json
 ```
-> **참고**: 자체 `.mcp.json`이 있는 경우 `mcpServers` 객체를 수동으로 병합하세요.
-## 사용법
+> **Note**: If you have your own `.mcp.json`, manually merge the `mcpServers` object.
-### 실행 예시
+## Usage Examples
 ```bash
-# 구현 계획 수립
-/plan 새로운 인증 시스템 구현
+# Generate llms.txt from website
+/generate-llmstxt https://docs.example.com
-# 커밋 및 푸시
+# Commit and push
 /commit-and-push src/auth.ts src/utils.ts
-# GitHub 이슈 해결
+# Resolve GitHub issue
 /gh/resolve-issue 42
+# Consult AI council
+/council "Should we use REST or GraphQL for this API?"
 ```
-## 주요 기능
+## Key Features
+### `/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.)
+- Analyze changes and generate appropriate commit message
+- Selectively commit specified files only
-### `/plan` - 구현 계획 수립
-- 요구사항의 의도를 파악하고 불명확하면 질문
-- 관련 코드베이스를 조사하고 이해
-- 단계별 실행 계획 작성
-- **바로 코드를 작성하지 않고 계획만 수립**
+### `/edit-notebook` - Jupyter Notebook Editing
+- Use only `NotebookEdit` tool (protect JSON structure)
+- Track cell_id for correct insertion order
+- Include source format issue resolution guide
-### `/commit-and-push` - Git 자동화
-- Conventional Commits 형식 준수 (feat, fix, refactor, docs 등)
-- 변경 내용 분석 후 적절한 커밋 메시지 생성
-- 지정된 파일만 선택적으로 커밋
+### `/council` - LLM Council
+- Query multiple AI models (Opus, Sonnet, Codex, Gemini) in parallel
+- Anonymize responses for unbiased evaluation
+- Synthesize collective wisdom into consensus
-### `/edit-notebook` - Jupyter Notebook 편집
-- `NotebookEdit` 도구만 사용 (JSON 구조 보호)
-- 셀 삽입 순서 보장을 위한 cell_id 추적
-- source 형식 문제 해결 가이드 포함
+### `web-researcher` Agent
+- Multi-platform search: GitHub (`gh` CLI), Hugging Face, Reddit, SO, arXiv
+- Official documentation via Context7/DeepWiki
+- Auto-generate research reports
-### `web-researcher` 에이전트
-- GitHub(`gh` CLI), Hugging Face(`huggingface_hub`), Reddit, SO, arXiv 등 다중 플랫폼 검색
-- Context7/DeepWiki를 통한 공식 문서 수집
-- 한글 리서치 리포트 자동 생성
+### `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` 스킬
-- `gh` CLI를 활용한 GitHub 리포지토리/코드 검색
-- `huggingface_hub` API를 활용한 모델/데이터셋/Spaces 검색
-- 임시 디렉토리(`/tmp/`)에 소스 코드 다운로드 및 분석
+### `code-explorer` Skill
+- GitHub repository/code search via `gh` CLI
+- Hugging Face model/dataset/Spaces search via `huggingface_hub` API
+- Download and analyze source code in temp directory (`/tmp/`)
-## 라이선스
+## License
 MIT License

package/package.json CHANGED Viewed

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

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

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