musubix 3.6.1 → 3.7.3

package/.github/skills/musubix-domain-inference/SKILL.md

@@ -1,196 +1,82 @@
 ---
 name: musubix-domain-inference
-description: Guide for automatic domain detection and component inference. Use this when asked to identify the domain of a project and get recommended components for that domain.
+description: 自動ドメイン検出・コンポーネント推論ガイド。プロジェクトドメイン特定に使用。
 license: MIT
 ---
 
-# MUSUBIX Domain Inference Skill
+# Domain Inference Skill
 
-This skill guides you through automatic domain detection and component recommendations.
+**62ドメイン**・**224コンポーネント**を自動検出・推奨。
 
-## Overview
+## Domain Categories
 
-MUSUBIX supports **62 domains** with **224 predefined components**. The domain inference system automatically:
+| カテゴリ | ドメイン数 | 例 |
+|---------|-----------|-----|
+| **Business** | 8 | ecommerce, finance, crm, hr |
+| **Healthcare** | 3 | healthcare, pharmacy, veterinary |
+| **Service** | 20+ | booking, hotel, restaurant, gym |
+| **Technology** | 8 | iot, security, ai, analytics |
 
-1. Detects project domain from requirements/descriptions
-2. Recommends optimal components for that domain
-3. Suggests architecture patterns
+## Key Domains
 
-## Supported Domains (62)
-
-### Business (8)
-| Domain | Description | Key Components |
-|--------|-------------|----------------|
+| Domain | 名称 | Key Components |
+|--------|------|----------------|
 | ecommerce | EC・通販 | CartService, ProductCatalog, OrderProcessor |
-| finance | 金融 | AccountService, TransactionManager, LedgerService |
-| crm | 顧客管理 | CustomerService, LeadManager, OpportunityTracker |
-| hr | 人事 | EmployeeService, PayrollCalculator, AttendanceTracker |
-| marketing | マーケティング | CampaignManager, AudienceSegmenter, AnalyticsService |
-| inventory | 在庫管理 | StockManager, ReorderService, WarehouseController |
-| payment | 決済 | PaymentGateway, RefundProcessor, InvoiceGenerator |
-| subscription | サブスク | PlanManager, BillingService, RenewalProcessor |
-
-### Healthcare (3)
-| Domain | Description | Key Components |
-|--------|-------------|----------------|
-| healthcare | ヘルスケア | PatientService, DiagnosticService, AppointmentManager |
-| pharmacy | 薬局 | PrescriptionManager, MedicineInventory, DosageCalculator |
-| veterinary | 動物病院 | PetService, VetScheduleService, VaccinationTracker |
-
-### Service (20+)
-| Domain | Description | Key Components |
-|--------|-------------|----------------|
-| booking | 予約 | ReservationService, SlotManager, AvailabilityChecker |
-| hotel | ホテル | RoomService, CheckInManager, HousekeepingScheduler |
-| restaurant | 飲食店 | MenuManager, TableService, KitchenOrderSystem |
-| gym | フィットネス | MembershipService, ClassScheduler, TrainerAssignment |
-| delivery | 配送 | DeliveryService, RouteOptimizer, TrackingManager |
-| parking | 駐車場 | SpaceManager, EntryExitController, FeeCalculator |
-
-### Technology (8)
-| Domain | Description | Key Components |
-|--------|-------------|----------------|
-| iot | IoT | DeviceManager, TelemetryProcessor, AlertService |
-| security | セキュリティ | AuthService, PermissionManager, AuditLogger |
-| ai | AI | ModelService, InferenceEngine, TrainingPipeline |
-| analytics | 分析 | ReportGenerator, MetricsCollector, DashboardService |
-
-## Domain Detection
-
-### Automatic Detection
-
-MUSUBIX analyzes text for domain keywords:
-
-```typescript
-import { domainDetector } from '@nahisaho/musubix-core';
-
-const result = domainDetector.detect(`
-  ペットの予約管理システムを作りたい。
-  獣医師のスケジュール管理と、ワクチン接種記録も必要。
-`);
-
-// Result:
-// {
-//   primaryDomain: { id: 'veterinary', name: 'Veterinary', nameJa: '動物病院' },
-//   confidence: 0.92,
-//   matchedKeywords: ['ペット', '獣医', 'ワクチン', '予約'],
-//   suggestedComponents: ['PetService', 'ReservationService', 'VetScheduleService']
-// }
-```
-
-### CLI Usage
-
-```bash
-# Analyze requirements file
-npx musubix design patterns --detect-domain storage/specs/REQ-001.md
-
-# Get component recommendations
-npx musubix design generate storage/specs/REQ-001.md --infer-components
-```
+| finance | 金融 | AccountService, TransactionManager |
+| veterinary | 動物病院 | PetService, VetScheduleService |
+| booking | 予約 | ReservationService, SlotManager |
+| iot | IoT | DeviceManager, TelemetryProcessor |
 
-## Component Inference
+## WHEN → DO
 
-### Domain-Specific Components
+| WHEN | DO |
+|------|-----|
+| 新規プロジェクト開始 | 要件テキストからドメイン検出 |
+| 複数ドメインの場合 | primaryとsecondaryを特定 |
+| コンポーネント設計 | 推奨コンポーネントを適用 |
 
-Each domain has predefined components with:
-- **Type**: Service, Repository, Controller, Factory, etc.
-- **Layer**: Presentation, Application, Domain, Infrastructure
-- **Dependencies**: Required collaborators
-- **Patterns**: Recommended design patterns
-- **Methods**: Domain-specific operations
-
-### Example: Veterinary Domain
-
-```typescript
-const veterinaryComponents = [
-  {
-    name: 'PetService',
-    type: 'service',
-    layer: 'application',
-    description: 'ペット管理のビジネスロジック',
-    dependencies: ['PetRepository', 'PetHistoryRepository'],
-    patterns: ['Service'],
-    methods: [
-      { name: 'register', returnType: 'Promise<Pet>' },
-      { name: 'update', returnType: 'Promise<Pet>' },
-      { name: 'getByOwner', returnType: 'Promise<Pet[]>' },
-      { name: 'getHistory', returnType: 'Promise<PetHistory[]>' },
-    ]
-  },
-  {
-    name: 'ReservationService',
-    type: 'service',
-    layer: 'application',
-    methods: [
-      { name: 'create', returnType: 'Promise<Reservation>' },
-      { name: 'confirm', returnType: 'Promise<Reservation>' },
-      { name: 'cancel', returnType: 'Promise<Reservation>' },
-      { name: 'getAvailableSlots', returnType: 'Promise<TimeSlot[]>' },
-    ]
-  },
-  // ...more components
-];
-```
-
-## Architecture Recommendations
-
-Based on domain, MUSUBIX recommends:
-
-| Domain Category | Architecture Style | Scaling Strategy |
-|-----------------|-------------------|------------------|
-| Business | Layered + DDD | Vertical with caching |
-| Technology | Microservices | Horizontal scaling |
-| Healthcare | Layered + Audit | Vertical with compliance |
-| Service | Layered | Vertical with caching |
-
-## Multi-Domain Projects
-
-For projects spanning multiple domains:
+## Detection Example
 
 ```typescript
 const result = domainDetector.detect(`
-  ECサイトで商品を販売し、配送追跡も行いたい。
-  在庫管理とサブスクリプション機能も必要。
+  ペットの予約管理システム。
+  獣医師のスケジュール管理とワクチン接種記録。
 `);
-
-// Result:
 // {
-//   primaryDomain: { id: 'ecommerce' },
-//   secondaryDomains: [
-//     { id: 'delivery' },
-//     { id: 'inventory' },
-//     { id: 'subscription' }
-//   ]
+//   primaryDomain: { id: 'veterinary' },
+//   confidence: 0.92,
+//   matchedKeywords: ['ペット', '獣医', 'ワクチン'],
+//   suggestedComponents: ['PetService', 'ReservationService']
 // }
 ```
 
-## Using in Design Documents
-
-```markdown
-# DES-SHOP-001: ECサイト設計
+## Architecture by Category
 
-## ドメイン分析
-- **主ドメイン**: ecommerce
-- **副ドメイン**: inventory, payment, delivery
+| カテゴリ | アーキテクチャ | スケーリング |
+|---------|---------------|-------------|
+| Business | Layered + DDD | Vertical + Cache |
+| Technology | Microservices | Horizontal |
+| Healthcare | Layered + Audit | Vertical + Compliance |
 
-## 推奨コンポーネント
+## CLI
 
-### ecommerce ドメイン
-| コンポーネント | 種別 | 責務 |
-|---------------|------|------|
-| CartService | Service | カート管理 |
-| ProductCatalog | Service | 商品カタログ |
-| OrderProcessor | Service | 注文処理 |
-
-### inventory ドメイン
-| コンポーネント | 種別 | 責務 |
-|---------------|------|------|
-| StockManager | Service | 在庫管理 |
-| ReorderService | Service | 発注管理 |
+```bash
+npx musubix design patterns --detect-domain <file>  # ドメイン検出
+npx musubix design generate <file> --infer-components  # コンポーネント推論
 ```
 
-## Related Skills
+## 出力例
 
-- `musubix-c4-design` - Create architecture with inferred components
-- `musubix-code-generation` - Generate code for components
-- `musubix-sdd-workflow` - Full workflow with domain awareness
+```
+┌─────────────────────────────────────────┐
+│ Domain Detected                         │
+├─────────────────────────────────────────┤
+│ Primary:    veterinary (動物病院)       │
+│ Confidence: 92%                         │
+│ Keywords:   ペット, 獣医, ワクチン      │
+│ Components: 5 recommended               │
+│ - PetService                            │
+│ - ReservationService                    │
+│ - VetScheduleService                    │
+└─────────────────────────────────────────┘
+```

package/.github/skills/musubix-ears-validation/SKILL.md

@@ -1,161 +1,74 @@
 ---
 name: musubix-ears-validation
-description: Guide for validating and creating EARS-format requirements. Use this when asked to write requirements, validate requirement syntax, or convert natural language to EARS format.
+description: EARS形式要件の検証・作成ガイド。要件記述・構文検証に使用。
 license: MIT
 ---
 
-# MUSUBIX EARS Validation Skill
+# EARS Validation Skill
 
-This skill helps you create and validate requirements using EARS (Easy Approach to Requirements Syntax) format.
+EARS (Easy Approach to Requirements Syntax) で要件を形式化・検証。
 
-## EARS Pattern Reference
+## EARS Patterns
 
-### 1. Ubiquitous Pattern
-**Use for**: Requirements that must always be satisfied.
+| パターン | 構文 | 用途 |
+|---------|------|------|
+| **Ubiquitous** | `THE [system] SHALL [requirement]` | 常に満たす要件 |
+| **Event-driven** | `WHEN [event], THE [system] SHALL [response]` | イベント発生時 |
+| **State-driven** | `WHILE [state], THE [system] SHALL [behavior]` | 特定状態中 |
+| **Unwanted** | `THE [system] SHALL NOT [behavior]` | 禁止事項 |
+| **Optional** | `IF [cond], THEN THE [system] SHALL [response]` | 条件付き |
 
-**Syntax**:
-```
-THE [system name] SHALL [requirement]
-```
-
-**Example**:
-```markdown
-THE AuthService SHALL authenticate users with valid credentials.
-```
-
-### 2. Event-Driven Pattern
-**Use for**: Requirements triggered by specific events.
-
-**Syntax**:
-```
-WHEN [trigger event], THE [system name] SHALL [response]
-```
-
-**Example**:
-```markdown
-WHEN a user submits login credentials, THE AuthService SHALL validate the credentials within 2 seconds.
-```
-
-### 3. State-Driven Pattern
-**Use for**: Requirements that apply while in a specific state.
-
-**Syntax**:
-```
-WHILE [system state], THE [system name] SHALL [behavior]
-```
-
-**Example**:
-```markdown
-WHILE the system is in maintenance mode, THE API SHALL return 503 Service Unavailable.
-```
-
-### 4. Unwanted Behavior Pattern
-**Use for**: Behaviors that must be prevented.
-
-**Syntax**:
-```
-THE [system name] SHALL NOT [unwanted behavior]
-```
-
-**Example**:
-```markdown
-THE AuthService SHALL NOT store passwords in plain text.
-```
-
-### 5. Optional Pattern
-**Use for**: Conditional requirements.
-
-**Syntax**:
-```
-IF [condition], THEN THE [system name] SHALL [response]
-```
+## WHEN → DO
 
-**Example**:
-```markdown
-IF two-factor authentication is enabled, THEN THE AuthService SHALL require a verification code.
-```
+| WHEN | DO |
+|------|-----|
+| 自然言語の要件 | EARS形式に変換 |
+| 要件レビュー | 6項目チェックリスト実施 |
+| 要件文書作成 | テンプレートに従って記述 |
 
 ## Validation Checklist
 
-When validating EARS requirements, check:
-
-- [ ] **Pattern Compliance**: Does it follow one of the 5 EARS patterns?
-- [ ] **System Name**: Is the system/component clearly identified?
-- [ ] **SHALL Keyword**: Is "SHALL" used for mandatory requirements?
-- [ ] **Measurable**: Is the requirement testable and measurable?
-- [ ] **Atomic**: Does it describe a single requirement?
-- [ ] **No Ambiguity**: Is the language clear and unambiguous?
-
-## CLI Commands
-
-```bash
-# Validate EARS syntax
-npx musubix requirements validate <file>
-
-# Convert natural language to EARS
-npx musubix requirements analyze <file>
-
-# Map to ontology
-npx musubix requirements map <file>
-```
+- [ ] **Pattern Compliance**: 5パターンのいずれかに準拠
+- [ ] **System Name**: システム名が明確
+- [ ] **SHALL Keyword**: 必須要件に「SHALL」使用
+- [ ] **Measurable**: テスト可能・測定可能
+- [ ] **Atomic**: 単一の要件を記述
+- [ ] **No Ambiguity**: 曖昧な表現がない
 
 ## Conversion Examples
 
-### Natural Language → EARS
+| 自然言語 | EARS形式 |
+|---------|---------|
+| ユーザーがログインできる | `THE AuthModule SHALL authenticate users with valid credentials.` |
+| パスワードが間違っている時エラー表示 | `WHEN invalid credentials are provided, THE AuthModule SHALL display an error.` |
+| SQLインジェクションを許可しない | `THE InputValidator SHALL NOT accept SQL injection patterns.` |
 
-**Input**: "Users should be able to login"
+## Priority Levels
 
-**Output**:
-```markdown
-THE AuthenticationModule SHALL authenticate users with valid credentials.
-```
+| 優先度 | 説明 | 用途 |
+|--------|------|------|
+| **P0** | 必須 | リリースブロッカー |
+| **P1** | 重要 | 可能な限り実装 |
+| **P2** | 任意 | 時間があれば |
 
-**Input**: "Show error when password is wrong"
+## CLI
 
-**Output**:
-```markdown
-WHEN invalid credentials are provided, THE AuthenticationModule SHALL display an error message.
+```bash
+npx musubix requirements validate <file>  # EARS検証
+npx musubix requirements analyze <file>   # 自然言語→EARS変換
+npx musubix requirements map <file>       # オントロジーマッピング
 ```
 
-**Input**: "Don't allow SQL injection"
+## 出力例
 
-**Output**:
-```markdown
-THE InputValidator SHALL NOT accept input containing SQL injection patterns.
 ```
-
-## Priority Levels
-
-| Priority | Description | Usage |
-|----------|-------------|-------|
-| **P0** | 必須 (Must Have) | Release blocker |
-| **P1** | 重要 (Should Have) | Implement if possible |
-| **P2** | 任意 (Nice to Have) | Time permitting |
-
-## Requirement Document Template
-
-```markdown
-### REQ-[CATEGORY]-[NUMBER]: [Title]
-
-**種別**: [UBIQUITOUS|EVENT-DRIVEN|STATE-DRIVEN|UNWANTED|OPTIONAL]
-**優先度**: [P0|P1|P2]
-
-**要件**:
-[EARS形式の要件文]
-
-**検証方法**: [Unit Test|Integration Test|E2E Test|Manual]
-**受入基準**:
-- [ ] Criterion 1
-- [ ] Criterion 2
-
-**トレーサビリティ**: DES-XXX, TEST-XXX
-**憲法準拠**: Article IV (EARS Format)
+┌─────────────────────────────────────────┐
+│ EARS Validation Result                  │
+├─────────────────────────────────────────┤
+│ Requirements: 5 validated               │
+│ ✅ Ubiquitous:   2 passed               │
+│ ✅ Event-driven: 2 passed               │
+│ ✅ Unwanted:     1 passed               │
+│ Issues: 0                               │
+└─────────────────────────────────────────┘
 ```
-
-## Common Mistakes to Avoid
-
-1. ❌ Using "should" instead of "SHALL"
-2. ❌ Combining multiple requirements in one statement
-3. ❌ Vague or unmeasurable criteria
-4. ❌ Missing system name
-5. ❌ Using implementation details in requirements