aiwf 0.1.0 → 0.3.1

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_language_status.md

@@ -0,0 +1,246 @@
+# AIWF 언어 상태 확인
+
+AIWF 프레임워크의 현재 언어 설정 상태를 자세히 확인하는 명령어입니다.
+
+## 사용법
+
+이 명령어는 다음과 같은 정보를 제공합니다:
+- 현재 감지된 시스템 언어
+- 사용자가 설정한 언어 (있는 경우)
+- 실제로 사용되는 언어
+- 언어 설정 파일 상태
+- 명령어 경로 해결 상태
+
+## 실행 과정
+
+### 1. 언어 상태 종합 분석
+
+```bash
+node -e "
+import('./language-utils.js').then(async (utils) => {
+  const { getLanguageStatus, resolveCommandPath, getLocalizedMessage } = utils;
+  
+  console.log('=== AIWF 언어 시스템 상태 분석 ===\n');
+  
+  // 기본 상태 정보
+  const status = await getLanguageStatus();
+  
+  console.log('📍 기본 정보:');
+  console.log('  감지된 언어:', status.detectedLanguage);
+  console.log('  설정된 언어:', status.configuredLanguage || '없음');
+  console.log('  현재 사용 언어:', status.effectiveLanguage);
+  console.log('  자동 감지:', status.autoDetect ? '활성화' : '비활성화');
+  console.log('  폴백 언어:', status.fallbackLanguage);
+  console.log('  지원 언어:', status.supportedLanguages.join(', '));
+  console.log('  설정 파일:', status.configPath);
+  
+  if (status.error) {
+    console.log('  ⚠️ 오류:', status.error);
+  }
+  
+  console.log('\n📂 설정 파일 상태:');
+  try {
+    const fs = await import('fs/promises');
+    const configExists = await fs.access(status.configPath).then(() => true).catch(() => false);
+    
+    if (configExists) {
+      const configContent = await fs.readFile(status.configPath, 'utf8');
+      const config = JSON.parse(configContent);
+      console.log('  ✅ 설정 파일 존재');
+      console.log('  📄 내용:', JSON.stringify(config, null, 4));
+    } else {
+      console.log('  ❌ 설정 파일 없음');
+    }
+  } catch (error) {
+    console.log('  ⚠️ 설정 파일 읽기 오류:', error.message);
+  }
+});
+"
+```
+
+### 2. 환경 변수 분석
+
+```bash
+node -e "
+console.log('\n🌍 시스템 환경 변수:');
+console.log('  LANG:', process.env.LANG || '설정되지 않음');
+console.log('  LC_ALL:', process.env.LC_ALL || '설정되지 않음');
+console.log('  LANGUAGE:', process.env.LANGUAGE || '설정되지 않음');
+console.log('  NODE_ENV:', process.env.NODE_ENV || '설정되지 않음');
+"
+```
+
+### 3. 명령어 경로 테스트
+
+```bash
+node -e "
+import('./language-utils.js').then(async ({ resolveCommandPath, detectLanguage }) => {
+  console.log('\n🔍 명령어 경로 해결 테스트:');
+  
+  const currentLang = await detectLanguage();
+  console.log('  현재 언어:', currentLang);
+  
+  const testCommands = [
+    'aiwf_do_task',
+    'aiwf_commit', 
+    'aiwf_initialize',
+    'aiwf_switch_language',
+    'aiwf_test',
+    'aiwf_code_review',
+    'aiwf_project_review'
+  ];
+  
+  for (const cmd of testCommands) {
+    const result = await resolveCommandPath(cmd);
+    if (result.path) {
+      const status = result.fallback ? '🔄 폴백' : '✅ 직접';
+      console.log('  ' + status, cmd + ':', result.language);
+    } else {
+      console.log('  ❌ 없음', cmd + ':', result.error);
+    }
+  }
+});
+"
+```
+
+### 4. 메시지 시스템 테스트
+
+```bash
+node -e "
+import('./language-utils.js').then(async ({ getLocalizedMessage, detectLanguage }) => {
+  console.log('\n💬 다국어 메시지 시스템 테스트:');
+  
+  const currentLang = await detectLanguage();
+  console.log('  현재 언어:', currentLang);
+  
+  const testMessages = [
+    'LANGUAGE_NOT_SUPPORTED',
+    'CONFIG_LOAD_FAILED', 
+    'CONFIG_SAVE_FAILED',
+    'COMMAND_NOT_FOUND',
+    'LANGUAGE_SWITCH_SUCCESS'
+  ];
+  
+  for (const msgKey of testMessages) {
+    const koMsg = getLocalizedMessage(msgKey, 'ko');
+    const enMsg = getLocalizedMessage(msgKey, 'en');
+    console.log('  ' + msgKey + ':');
+    console.log('    한국어: ' + koMsg);
+    console.log('    English: ' + enMsg);
+  }
+});
+"
+```
+
+### 5. 디렉토리 구조 확인
+
+```bash
+node -e "
+const fs = await import('fs/promises');
+const path = await import('path');
+
+console.log('\n📁 AIWF 디렉토리 구조:');
+
+const checkDirs = [
+  '.aiwf',
+  '.aiwf/config',
+  '.claude',
+  '.claude/commands',
+  '.claude/commands/aiwf',
+  'claude-code/aiwf/ko/.claude/commands/aiwf',
+  'claude-code/aiwf/en/.claude/commands/aiwf'
+];
+
+for (const dir of checkDirs) {
+  try {
+    const exists = await fs.access(dir).then(() => true).catch(() => false);
+    if (exists) {
+      const files = await fs.readdir(dir);
+      console.log('  ✅', dir + ':', files.length + '개 파일');
+    } else {
+      console.log('  ❌', dir + ':', '디렉토리 없음');
+    }
+  } catch (error) {
+    console.log('  ⚠️', dir + ':', '접근 오류');
+  }
+}
+"
+```
+
+## 진단 및 권장사항
+
+### 언어 감지 문제 해결
+
+명령어가 다음과 같은 권장사항을 제공합니다:
+
+1. **설정 파일이 없는 경우**:
+   ```
+   💡 권장사항: 언어를 명시적으로 설정하세요
+   /project:aiwf:switch_language ko
+   ```
+
+2. **환경 변수 문제**:
+   ```
+   💡 권장사항: 환경 변수를 확인하세요
+   export LANG=ko_KR.UTF-8
+   ```
+
+3. **명령어 파일 누락**:
+   ```
+   💡 권장사항: AIWF를 다시 설치하세요
+   npx aiwf --force
+   ```
+
+## 출력 예시
+
+```
+=== AIWF 언어 시스템 상태 분석 ===
+
+📍 기본 정보:
+  감지된 언어: ko
+  설정된 언어: ko
+  현재 사용 언어: ko
+  자동 감지: 활성화
+  폴백 언어: en
+  지원 언어: ko, en
+  설정 파일: .aiwf/config/language.json
+
+📂 설정 파일 상태:
+  ✅ 설정 파일 존재
+  📄 내용: {
+      "language": "ko",
+      "auto_detect": true,
+      "last_updated": "2025-07-03T06:25:00.000Z",
+      "fallback": "en"
+  }
+
+🌍 시스템 환경 변수:
+  LANG: ko_KR.UTF-8
+  LC_ALL: 설정되지 않음
+  LANGUAGE: 설정되지 않음
+  NODE_ENV: 설정되지 않음
+
+🔍 명령어 경로 해결 테스트:
+  현재 언어: ko
+  ✅ 직접 aiwf_do_task: ko
+  ✅ 직접 aiwf_commit: ko
+  ✅ 직접 aiwf_initialize: ko
+  ✅ 직접 aiwf_switch_language: ko
+  🔄 폴백 aiwf_test: en
+  ❌ 없음 aiwf_unknown: 명령어 파일을 찾을 수 없습니다
+
+💬 다국어 메시지 시스템 테스트:
+  현재 언어: ko
+  LANGUAGE_NOT_SUPPORTED:
+    한국어: 지원되지 않는 언어입니다
+    English: Language not supported
+  
+📁 AIWF 디렉토리 구조:
+  ✅ .aiwf: 8개 파일
+  ✅ .aiwf/config: 1개 파일
+  ✅ .claude: 2개 파일
+  ✅ .claude/commands: 1개 파일
+  ❌ .claude/commands/aiwf: 디렉토리 없음
+  ✅ claude-code/aiwf/ko/.claude/commands/aiwf: 15개 파일
+  ✅ claude-code/aiwf/en/.claude/commands/aiwf: 14개 파일
+```

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_mermaid.md

@@ -0,0 +1,272 @@
+# Mermaid 다이어그램 유지 관리
+
+Instructions for generating, maintaining and updating the mermaid diagrams in the current project's architecture documentation.
+
+## 📋 Overview
+
+The architecture documentation should include comprehensive mermaid diagrams that illustrate:
+
+- System context and component relationships
+- Module dependencies and data flows (150+ modules)
+- Class hierarchies and interactions
+- Service layer patterns and UI architecture
+
+## 📂 Diagram Locations
+
+All architecture diagrams are to be stored in `/docs/architecture/`:
+
+```
+docs/architecture/
+├── README.md                           # Main architecture overview
+├── context_diagram.md                  # System context & data flow
+├── module_overview.md                  # Module relationships (150+ modules)
+└── class_diagrams/
+    ├── core_classes.md                 # Database, DAOs, data processing
+    ├── data_models.md                  # Domain models & database schema
+    └── service_layer.md                # UI architecture & service coordination
+```
+
+## 🛠️ Update Process
+
+### Step 1: Identify Affected Diagrams
+
+Determine which diagrams need updates based on your changes:
+
+| Change Type            | Primary Diagram    | Secondary Diagrams |
+| ---------------------- | ------------------ | ------------------ |
+| New analytics module   | module_overview.md | context_diagram.md |
+| Database schema change | data_models.md     | core_classes.md    |
+| New UI component       | service_layer.md   | module_overview.md |
+| New service/manager    | service_layer.md   | module_overview.md |
+| Architecture refactor  | context_diagram.md | All others         |
+
+### Step 2: Update Mermaid Code
+
+Edit the relevant `.md` files to update mermaid diagram code:
+
+```mermaid
+# Example: Adding a new class to core_classes.md
+class NewAnalyticsService {
+    -CacheManager cache_manager
+    -Logger logger
+    +calculate_advanced_metrics() Dict
+    +generate_insights() List[str]
+}
+
+# Add relationships
+NewAnalyticsService --> CacheManager : uses
+NewAnalyticsService --> DatabaseManager : queries
+```
+
+### Step 3: Validate Diagrams
+
+Test diagram syntax and rendering:
+
+1. **Online validation**: Copy mermaid code to [Mermaid Live Editor](https://mermaid.live/)
+2. **Local preview**: Use VS Code Mermaid extensions
+3. **Check syntax**: Ensure proper mermaid formatting
+
+### Step 4: Update Cross-References
+
+Update any cross-references in documentation:
+
+- Update `docs/architecture/README.md` if adding new diagrams
+- Update navigation links between diagram files
+- Update main project README if architecture changes significantly
+
+## 📝 Mermaid Syntax Guidelines
+
+### Class Diagrams
+
+```mermaid
+classDiagram
+    class ClassName {
+        -private_field: Type
+        +public_method() ReturnType
+        #protected_method(param: Type) void
+    }
+
+    %% Relationships
+    ClassA <|-- ClassB : inherits
+    ClassA *-- ClassC : composition
+    ClassA --> ClassD : uses
+    ClassA ..> ClassE : depends on
+
+    %% Notes
+    note for ClassName "Important implementation details"
+```
+
+### Flowcharts
+
+```mermaid
+flowchart TD
+    A[Start] --> B{Decision}
+    B -->|Yes| C[Action 1]
+    B -->|No| D[Action 2]
+    C --> E[End]
+    D --> E
+
+    %% Styling
+    style A fill:#e1f5fe
+    style E fill:#e8f5e8
+```
+
+### Sequence Diagrams
+
+```mermaid
+sequenceDiagram
+    participant A as Actor
+    participant B as System
+
+    A->>B: Request
+    B->>B: Process
+    B-->>A: Response
+
+    Note over A,B: Important interaction
+```
+
+## 🎨 Styling Guidelines
+
+### Color Scheme
+
+Use consistent colors across all diagrams:
+
+```mermaid
+%% Standard color palette
+style MainComponents fill:#4ecdc4,color:#fff
+style DataLayer fill:#f3e5f5
+style CacheLayer fill:#fff8e1
+style UILayer fill:#e8f5e8
+style ExternalSystems fill:#e1f5fe
+```
+
+### Component Categories
+
+- **🏗️ Core Infrastructure**: `#4ecdc4` (teal)
+- **📊 Analytics/Data**: `#f3e5f5` (light purple)
+- **⚡ Caching/Performance**: `#fff8e1` (light yellow)
+- **🎨 UI Components**: `#e8f5e8` (light green)
+- **🔗 External Systems**: `#e1f5fe` (light blue)
+
+## 📋 Common Update Scenarios
+
+### Adding a New Analytics Module
+
+1. **Update module_overview.md**: Add to Analytics Engine section
+2. **Update class diagrams**: Add detailed class structure if significant
+3. **Update context_diagram.md**: Add if it's a major new capability
+
+```mermaid
+# Example: New trend analysis module
+TREND_ANALYZER[trend_analyzer.py<br/>📈 Advanced Trends]
+TREND_ANALYZER --> DAILY_CALC
+TREND_ANALYZER --> CACHE
+```
+
+### New UI Component or Widget
+
+1. **Update service_layer.md**: Add class definition and relationships
+2. **Update module_overview.md**: Add to UI Layer section
+3. **Consider component factory updates**
+
+```mermaid
+# Example: New dashboard widget
+class NewDashboardWidget {
+    -MetricsCalculator calculator
+    -ComponentFactory factory
+    +setup_ui() void
+    +refresh_data() void
+}
+QWidget <|-- NewDashboardWidget : inherits
+```
+
+### Database Schema Changes
+
+1. **Update data_models.md**: Modify ER diagram and class definitions
+2. **Update core_classes.md**: Update DAO methods if needed
+3. **Document migration requirements**
+
+### New Service or Manager Class
+
+1. **Update service_layer.md**: Add to appropriate service category
+2. **Update relationships**: Show dependencies and usage patterns
+3. **Update module_overview.md**: Add service layer connections
+
+## 🔍 Validation Checklist
+
+Before committing diagram updates:
+
+- [ ] **Syntax Valid**: Diagram renders without errors
+- [ ] **Consistent Styling**: Uses standard color scheme
+- [ ] **Accurate Relationships**: Reflects actual code relationships
+- [ ] **Clear Labels**: All components clearly labeled
+- [ ] **Cross-References Updated**: Navigation links work
+- [ ] **README Updated**: Main architecture README reflects changes
+
+## 🤖 Automation & Maintenance Scripts
+
+### Useful Commands for Analysis
+
+```bash
+# Find all Python classes in the codebase
+find src/ -name "*.py" -exec grep -l "^class " {} \; | sort
+
+# Check module imports to understand dependencies
+grep -r "^from src\." src/ | cut -d: -f2 | sort | uniq
+
+# Find new files since last commit
+git diff --name-only HEAD~1 | grep "\.py$"
+
+# Count modules by package
+find src/ -name "*.py" | cut -d/ -f2 | sort | uniq -c
+```
+
+### Maintenance Tasks
+
+1. **Quarterly Review**: Compare diagrams against actual codebase structure
+2. **Release Preparation**: Ensure all diagrams reflect release state
+3. **Refactoring Support**: Update diagrams during major refactors
+4. **New Developer Onboarding**: Keep diagrams current for documentation
+
+## 🚨 Best Practices
+
+### Do's
+
+- ✅ **Keep diagrams focused**: One primary concept per diagram
+- ✅ **Use consistent naming**: Match actual class/module names
+- ✅ **Add explanatory notes**: Include important design decisions
+- ✅ **Regular updates**: Keep diagrams current with code changes
+- ✅ **Validate syntax**: Always test before committing
+
+### Don'ts
+
+- ❌ **Avoid over-complexity**: Don't include every minor detail
+- ❌ **Don't duplicate**: Each relationship should appear in most appropriate diagram
+- ❌ **Avoid generic names**: Use specific, meaningful component names
+- ❌ **Don't ignore styling**: Consistent colors improve readability
+- ❌ **Don't skip validation**: Always check diagram rendering
+
+## 📞 Support & Resources
+
+### Documentation Resources
+
+- [Mermaid Documentation](https://mermaid-js.github.io/mermaid/)
+- [Mermaid Live Editor](https://mermaid.live/) - For testing diagrams
+- [VS Code Mermaid Extension](https://marketplace.visualstudio.com/items?itemName=bierner.markdown-mermaid)
+
+### Quick Reference
+
+- **Architecture overview**: `/docs/architecture/README.md`
+- **System context**: `/docs/architecture/context_diagram.md`
+- **Module relationships**: `/docs/architecture/module_overview.md`
+- **Class details**: `/docs/architecture/class_diagrams/`
+
+### Getting Help
+
+1. **Reference existing patterns**: Look at similar components in current diagrams
+2. **Check diagram history**: Use git to see how similar changes were handled
+3. **Ask in code review**: Get feedback on architectural accuracy
+
+---
+
+_Keep architecture diagrams accurate, useful, and maintainable as the project evolves. Focus on clarity and consistency to support both current development and future maintenance._

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_pr_create.md

@@ -0,0 +1,76 @@
+# 태스크 완료 후 풀 리퀘스트 생성
+
+태스크 완료 후 GitHub 풀 리퀘스트를 생성하고 관련 이슈와 연결합니다.
+
+## 정확히 다음 6개 항목으로 TODO 생성
+
+1. 현재 브랜치 및 변경사항 확인
+2. PR 본문 템플릿 생성
+3. GitHub PR 생성
+4. 이슈와 PR 연결
+5. 리뷰어 배정
+6. 결과 보고
+
+## 1 · 브랜치 및 변경사항 확인
+
+병렬로 실행:
+- `git branch --show-current`: 현재 브랜치 확인
+- `git log main..HEAD --oneline`: 커밋 히스토리
+- `git diff main...HEAD --stat`: 변경된 파일 통계
+
+Extract GitHub issue number from task file
+
+## 2 · Generate PR Body Template
+
+```markdown
+## 🎯 Overview
+Completed implementation of {task_title}.
+
+## 📝 Changes
+{commit_list}
+
+## 📊 Changed Files
+{file_statistics}
+
+## ✅ Checklist
+- [ ] Tests pass
+- [ ] Code review completed
+- [ ] Documentation updated
+
+## 🔗 Related Information
+- Closes #{issue_number}
+- Task: {task_id}
+```
+
+## 3 · Create GitHub PR
+
+```bash
+gh pr create \
+  --title "{task_id}: {task_title}" \
+  --body "$(cat <<'EOF'
+{pr_body}
+EOF
+)" \
+  --base main \
+  --head {branch_name}
+```
+
+## 4 · Link Issue with PR
+
+Automatically included in PR body:
+- `Closes #{issue_number}`: Auto-close issue
+- `Relates to #{issue_number}`: Show relationship
+
+## 5 · Assign Reviewers
+
+```bash
+gh pr edit {pr_number} \
+  --add-reviewer {reviewer_username}
+```
+
+## 6 · Report Results
+
+✅ **PR Created**: #{pr_number}
+🔗 **Link**: {pr_url}
+🎯 **Linked Issue**: #{issue_number}
+👥 **Reviewers**: {reviewers}

package/claude-code/aiwf/ko/.claude/commands/aiwf/aiwf_prime.md

@@ -0,0 +1,9 @@
+# 지식 프라임
+
+이 프로젝트의 기본 정보로 자신을 준비시키세요.
+환경을 인식하고 있는지 확인하세요.
+
+## **병렬 에이전트**를 사용하여 다음을 수행하세요
+
+- 기본 프로젝트 정보를 위해 .aiwf/01_PROJECT_DOCS/ARCHITECTURE.md 읽기
+- 프로젝트 상태를 위해 .aiwf/00_PROJECT_MANIFEST.md 읽기