musubix 1.1.9 → 1.1.13

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

@@ -0,0 +1,196 @@
+---
+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.
+license: MIT
+---
+
+# MUSUBIX Domain Inference Skill
+
+This skill guides you through automatic domain detection and component recommendations.
+
+## Overview
+
+MUSUBIX supports **62 domains** with **224 predefined components**. The domain inference system automatically:
+
+1. Detects project domain from requirements/descriptions
+2. Recommends optimal components for that domain
+3. Suggests architecture patterns
+
+## Supported Domains (62)
+
+### Business (8)
+| Domain | Description | 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
+```
+
+## Component Inference
+
+### Domain-Specific Components
+
+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:
+
+```typescript
+const result = domainDetector.detect(`
+  ECサイトで商品を販売し、配送追跡も行いたい。
+  在庫管理とサブスクリプション機能も必要。
+`);
+
+// Result:
+// {
+//   primaryDomain: { id: 'ecommerce' },
+//   secondaryDomains: [
+//     { id: 'delivery' },
+//     { id: 'inventory' },
+//     { id: 'subscription' }
+//   ]
+// }
+```
+
+## Using in Design Documents
+
+```markdown
+# DES-SHOP-001: ECサイト設計
+
+## ドメイン分析
+- **主ドメイン**: ecommerce
+- **副ドメイン**: inventory, payment, delivery
+
+## 推奨コンポーネント
+
+### ecommerce ドメイン
+| コンポーネント | 種別 | 責務 |
+|---------------|------|------|
+| CartService | Service | カート管理 |
+| ProductCatalog | Service | 商品カタログ |
+| OrderProcessor | Service | 注文処理 |
+
+### inventory ドメイン
+| コンポーネント | 種別 | 責務 |
+|---------------|------|------|
+| StockManager | Service | 在庫管理 |
+| ReorderService | Service | 発注管理 |
+```
+
+## 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

package/.github/skills/musubix-test-generation/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: musubix-test-generation
+description: Guide for generating test code from designs and requirements. Use this when asked to create unit tests, integration tests, or test coverage analysis following TDD/BDD practices.
+license: MIT
+---
+
+# MUSUBIX Test Generation Skill
+
+This skill guides you through generating comprehensive test suites that maintain traceability.
+
+## Overview
+
+MUSUBIX follows **Article III - Test-First**: Red-Green-Blue TDD cycle.
+
+```mermaid
+flowchart LR
+    RED[🔴 Red<br/>Failing Test] --> GREEN[🟢 Green<br/>Minimal Code]
+    GREEN --> BLUE[🔵 Blue<br/>Refactor]
+    BLUE --> RED
+```
+
+## Test Structure
+
+### Unit Test Template
+
+```typescript
+/**
+ * @requirement REQ-XXX-NNN
+ * @design DES-XXX-NNN
+ */
+import { describe, it, expect, beforeEach } from 'vitest';
+import { XxxService } from './xxx-service.js';
+import { resetXxxCounter } from './xxx-entity.js';
+
+describe('XxxService', () => {
+  let service: XxxService;
+  let repository: MockXxxRepository;
+
+  beforeEach(() => {
+    // BP-TEST-001: Reset counters before each test
+    resetXxxCounter();
+    repository = new MockXxxRepository();
+    service = new XxxService(repository);
+  });
+
+  describe('create', () => {
+    it('should create entity with valid input', async () => {
+      // Arrange
+      const input = { name: 'Test', value: 100 };
+      
+      // Act
+      const result = await service.create(input);
+      
+      // Assert
+      expect(result.isOk()).toBe(true);
+      if (result.isOk()) {
+        expect(result.value.name).toBe('Test');
+      }
+    });
+
+    it('should return error for invalid input', async () => {
+      // Arrange
+      const input = { name: '', value: -1 };
+      
+      // Act
+      const result = await service.create(input);
+      
+      // Assert
+      expect(result.isErr()).toBe(true);
+    });
+  });
+});
+```
+
+### Integration Test Template
+
+```typescript
+/**
+ * @requirement REQ-XXX-NNN
+ * @design DES-XXX-NNN
+ */
+import { describe, it, expect, beforeAll, afterAll } from 'vitest';
+
+describe('XxxService Integration', () => {
+  beforeAll(async () => {
+    // Setup test environment
+  });
+
+  afterAll(async () => {
+    // Cleanup
+  });
+
+  it('should complete full workflow', async () => {
+    // Test full user journey
+  });
+});
+```
+
+## Best Practices for Testing
+
+### BP-TEST-001: Test Counter Reset
+
+```typescript
+beforeEach(() => {
+  resetPetCounter();  // Reset ID counters
+  resetReservationCounter();
+});
+```
+
+### BP-TEST-002: Verify API Before Test
+
+```typescript
+// ✅ Check actual API signature first
+const service = new PetService(repository);
+// Verify method exists and parameters match
+```
+
+### BP-TEST-004: Result Type Test Pattern
+
+```typescript
+// ✅ Test both success and failure cases
+it('should handle success', async () => {
+  const result = await service.create(validInput);
+  expect(result.isOk()).toBe(true);
+  if (result.isOk()) {
+    expect(result.value.id).toBeDefined();
+  }
+});
+
+it('should handle failure', async () => {
+  const result = await service.create(invalidInput);
+  expect(result.isErr()).toBe(true);
+  if (result.isErr()) {
+    expect(result.error.message).toContain('validation');
+  }
+});
+```
+
+### BP-TEST-005: Status Transition Testing
+
+```typescript
+describe('status transitions', () => {
+  // Valid transitions
+  it('should allow draft -> active', () => {
+    const result = workflow.transition('draft', 'activate');
+    expect(result).toBe('active');
+  });
+
+  // Invalid transitions
+  it('should reject completed -> draft', () => {
+    expect(() => workflow.transition('completed', 'revert'))
+      .toThrow('Invalid transition');
+  });
+});
+```
+
+## Test Categories
+
+| Category | Purpose | Location |
+|----------|---------|----------|
+| Unit | Single component | `__tests__/unit/` |
+| Integration | Multiple components | `__tests__/integration/` |
+| E2E | Full user flows | `__tests__/e2e/` |
+
+## CLI Commands
+
+```bash
+# Generate tests from design
+npx musubix test generate storage/design/DES-XXX.md
+
+# Run all tests
+npm test
+
+# Coverage report
+npx musubix test coverage src/
+
+# Run specific test file
+npm test -- xxx.test.ts
+```
+
+## Vitest Configuration
+
+```typescript
+// vitest.config.ts
+import { defineConfig } from 'vitest/config';
+
+export default defineConfig({
+  test: {
+    globals: true,
+    environment: 'node',
+    include: ['**/*.test.ts'],
+    coverage: {
+      provider: 'v8',
+      reporter: ['text', 'json', 'html'],
+    },
+  },
+});
+```
+
+## Coverage Targets
+
+| Metric | Target |
+|--------|--------|
+| Line Coverage | ≥80% |
+| Branch Coverage | ≥75% |
+| Function Coverage | ≥90% |
+
+## Related Skills
+
+- `musubix-sdd-workflow` - Full SDD workflow with TDD
+- `musubix-code-generation` - Generate code to test
+- `musubix-traceability` - Link tests to requirements

package/.github/skills/musubix-traceability/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: musubix-traceability
+description: Guide for managing traceability between requirements, designs, code, and tests. Use this when asked to verify traceability, create traceability matrices, or perform impact analysis.
+license: MIT
+---
+
+# MUSUBIX Traceability Skill
+
+This skill guides you through maintaining full traceability across the development lifecycle.
+
+## Overview
+
+MUSUBIX enforces **Article V - Traceability**: Complete bidirectional tracing between:
+
+```
+Requirements (REQ-*) ↔ Design (DES-*) ↔ Tasks (TSK-*) ↔ Code ↔ Tests
+```
+
+## Traceability Matrix
+
+### Creating a Traceability Matrix
+
+```markdown
+# Traceability Matrix
+
+| 要件ID | 設計ID | タスクID | コード | テスト |
+|--------|--------|---------|--------|--------|
+| REQ-AUTH-001 | DES-AUTH-001 | TSK-001 | src/auth/auth-service.ts | auth.test.ts |
+| REQ-AUTH-002 | DES-AUTH-001 | TSK-002 | src/auth/token-manager.ts | token.test.ts |
+```
+
+### CLI Commands
+
+```bash
+# Generate traceability matrix
+npx musubix trace matrix
+
+# Impact analysis for a specific requirement
+npx musubix trace impact REQ-AUTH-001
+
+# Validate all traceability links
+npx musubix trace validate
+```
+
+## Traceability in Code
+
+### Adding Traceability Comments
+
+```typescript
+/**
+ * AuthService - 認証サービス
+ * @requirement REQ-AUTH-001
+ * @design DES-AUTH-001
+ * @task TSK-001
+ */
+export class AuthService {
+  /**
+   * ユーザー認証
+   * @requirement REQ-AUTH-001
+   */
+  async authenticate(credentials: Credentials): Promise<Result<Token, AuthError>> {
+    // Implementation
+  }
+}
+```
+
+### Test Traceability
+
+```typescript
+/**
+ * @requirement REQ-AUTH-001
+ * @design DES-AUTH-001
+ */
+describe('AuthService', () => {
+  describe('authenticate', () => {
+    it('should return token for valid credentials', async () => {
+      // Test implementation
+    });
+  });
+});
+```
+
+## Impact Analysis
+
+When a requirement changes, identify all affected artifacts:
+
+```mermaid
+flowchart LR
+    REQ[REQ-AUTH-001<br/>変更] --> DES[DES-AUTH-001<br/>設計]
+    DES --> TSK1[TSK-001<br/>タスク]
+    DES --> TSK2[TSK-002<br/>タスク]
+    TSK1 --> CODE1[auth-service.ts]
+    TSK2 --> CODE2[token-manager.ts]
+    CODE1 --> TEST1[auth.test.ts]
+    CODE2 --> TEST2[token.test.ts]
+```
+
+### Impact Analysis Steps
+
+1. Identify changed requirement (REQ-*)
+2. Find linked designs (DES-*)
+3. Find linked tasks (TSK-*)
+4. Locate affected code files
+5. Identify tests to update
+6. Update all artifacts
+
+## Traceability Storage
+
+```
+storage/traceability/
+├── matrix.json           # Full traceability matrix
+├── requirements-map.json # REQ -> DES mappings
+├── design-map.json       # DES -> TSK mappings
+└── code-map.json         # TSK -> Code mappings
+```
+
+## Verification Checklist
+
+Before completing any feature:
+
+- [ ] All requirements have linked designs
+- [ ] All designs have linked tasks
+- [ ] All tasks have linked code
+- [ ] All code has linked tests
+- [ ] Traceability comments in code
+- [ ] Matrix updated
+
+## MCP Tool
+
+Use MCP tool for automated validation:
+
+```
+Tool: sdd_validate_traceability
+Description: Validates bidirectional traceability across all artifacts
+```
+
+## Related Skills
+
+- `musubix-sdd-workflow` - Full SDD workflow
+- `musubix-ears-validation` - Requirements validation
+- `musubix-test-generation` - Generate tests with traceability

package/AGENTS.md

@@ -8,14 +8,15 @@
 
 | 項目 | 詳細 |
 |------|------|
-| **バージョン** | 1.1.4 |
+| **バージョン** | 1.1.11 |
 | **言語** | TypeScript |
 | **ランタイム** | Node.js >= 20.0.0 |
 | **パッケージマネージャ** | npm >= 10.0.0 |
 | **ビルドシステム** | モノレポ（npm workspaces） |
 | **テストフレームワーク** | Vitest |
-| **テスト数** | 439 (全合格) |
-| **コンポーネント数** | ~430 (62ドメイン対応) |
+| **テスト数** | 459 (全合格) |
+| **コンポーネント数** | 224 (62ドメイン対応) |
+| **Agent Skills** | 9 (Claude Code対応) |
 
 ---
 
@@ -276,9 +277,9 @@ npx musubix codegen generate <design.md> --output src/
 
 ---
 
-## � 学習済みベストプラクティス（v1.1.7 NEW!）
+## � 学習済みベストプラクティス（v1.1.10 Updated!）
 
-Project-07 Medical Clinic、Project-08 Property Rentalの実装から学習したパターンです。
+Project-07〜14の実装から学習したパターンです。
 
 ### コードパターン
 
@@ -287,19 +288,29 @@ Project-07 Medical Clinic、Project-08 Property Rentalの実装から学習し
 | BP-CODE-001 | Entity Input DTO | エンティティ作成にInput DTOオブジェクトを使用 | 95% |
 | BP-CODE-002 | Date-based ID Format | PREFIX-YYYYMMDD-NNN形式でIDを生成 | 90% |
 | BP-CODE-003 | Value Objects | ドメイン概念にValue Objectを使用 | 90% |
+| BP-CODE-004 | Function-based Value Objects | クラスではなくinterface+factory関数でVO実装 | 95% |
+| BP-CODE-005 | Result Type | 失敗可能な操作にResult<T, E>を使用 | 95% |
 
-**Entity Input DTO例**:
+**Function-based Value Object例**:
 ```typescript
-// ✅ 推奨: Input DTOを使用
-interface CreatePatientInput {
-  name: PersonName;
-  dateOfBirth: Date;
-  contact: ContactInfo;
+// ✅ 推奨: Interface + Factory Function
+interface Price {
+  readonly amount: number;
+  readonly currency: 'JPY';
 }
-function createPatient(input: CreatePatientInput): Patient { ... }
 
-// ❌ 非推奨: 複数パラメータ
-function createPatient(name: PersonName, dob: Date, contact: ContactInfo): Patient
+function createPrice(amount: number): Result<Price, ValidationError> {
+  if (amount < 100 || amount > 1_000_000) {
+    return err(new ValidationError('Price must be between 100 and 1,000,000 JPY'));
+  }
+  return ok({ amount, currency: 'JPY' });
+}
+
+// ❌ 非推奨: クラスベース（構造的型付けと相性が悪い）
+class Price {
+  private constructor(readonly amount: number) {}
+  static create(amount: number): Price { ... }
+}
 ```
 
 ### 設計パターン
@@ -309,15 +320,18 @@ function createPatient(name: PersonName, dob: Date, contact: ContactInfo): Patie
 | BP-DESIGN-001 | Status Transition Map | 有効なステータス遷移をMapで定義 | 95% |
 | BP-DESIGN-002 | Repository Async Pattern | 将来のDB移行に備えてasync化 | 85% |
 | BP-DESIGN-003 | Service Layer with DI | リポジトリをDIしたService層 | 90% |
+| BP-DESIGN-004 | Optimistic Locking | 同時編集検出のためのversion管理 | 90% |
+| BP-DESIGN-005 | AuditService | データ変更の監査ログ記録 | 85% |
+| BP-DESIGN-006 | Entity Counter Reset | テスト用のresetXxxCounter()関数を提供 | 95% |
+| BP-DESIGN-007 | Expiry Time Logic | 有効期限をexpiresAtフィールドで明示管理 | 90% |
 
 **Status Transition Map例**:
 ```typescript
 const validStatusTransitions: Record<Status, Status[]> = {
-  draft: ['active'],
-  active: ['renewed', 'terminated', 'expired'],
-  renewed: [],
-  terminated: [],
-  expired: ['renewed'],
+  draft: ['active', 'cancelled'],
+  active: ['completed', 'cancelled'],
+  completed: [],
+  cancelled: [],
 };
 ```
 
@@ -328,16 +342,27 @@ const validStatusTransitions: Record<Status, Status[]> = {
 | BP-TEST-001 | Test Counter Reset | beforeEachでIDカウンターをリセット | 95% |
 | BP-TEST-002 | Verify API Before Test | テスト前にAPIシグネチャを確認 | 80% |
 | BP-TEST-003 | Vitest ESM Configuration | Vitest + TypeScript ESM構成 | 85% |
+| BP-TEST-004 | Result Type Test Pattern | isOk()/isErr()で両方のケースをテスト | 95% |
+| BP-TEST-005 | Status Transition Testing | 有効・無効な遷移を網羅的にテスト | 90% |
 
-**Test Counter Reset例**:
+**Result Type Test例**:
 ```typescript
-// Entity側でresetXxxCounter()を提供
-export function resetPatientCounter(): void { patientCounter = 0; }
-
-// テスト側でbeforeEachでリセット
-beforeEach(() => {
-  resetPatientCounter();
-  resetAppointmentCounter();
+describe('createPrice', () => {
+  it('should create valid price', () => {
+    const result = createPrice(1000);
+    expect(result.isOk()).toBe(true);
+    if (result.isOk()) {
+      expect(result.value.amount).toBe(1000);
+    }
+  });
+
+  it('should reject price below minimum', () => {
+    const result = createPrice(50);
+    expect(result.isErr()).toBe(true);
+    if (result.isErr()) {
+      expect(result.error.message).toContain('100');
+    }
+  });
 });
 ```
 
@@ -399,6 +424,6 @@ npx musubix learn best-practices --format markdown
 ---
 
 **Agent**: GitHub Copilot / Claude
-**Last Updated**: 2026-01-05
-**Version**: 1.1.7
+**Last Updated**: 2026-01-04
+**Version**: 1.1.10
 **Repository**: https://github.com/nahisaho/MUSUBIX

package/README.ja.md

@@ -10,7 +10,7 @@
 
 > MUSUBI × YATA 統合による次世代AIコーディングシステム
 >
-> **v1.1.4** - 自己学習改善: MockGenerator, BaseRepository, AdapterNaming + gym/bookingドメイン
+> **v1.1.9** - EARSパーサーMarkdown対応、ベストプラクティスCLI強化
 
 ## 概要