musubi-sdd 5.1.0 → 5.6.1

package/src/templates/agents/claude-code/skills/software-developer/test-first-workflow.md

@@ -43,23 +43,23 @@ describe('AuthService', () => {
       const authService = new AuthService(mockUserRepo);
       const email = 'test@example.com';
       const password = 'validPassword123';
-      
+
       // Act
       const result = await authService.login(email, password);
-      
+
       // Assert
       expect(result.success).toBe(true);
       expect(result.user.email).toBe(email);
     });
-    
+
     it('should throw error when credentials are invalid', async () => {
       // Arrange
       const authService = new AuthService(mockUserRepo);
-      
+
       // Act & Assert
-      await expect(
-        authService.login('test@example.com', 'wrongPassword')
-      ).rejects.toThrow('Invalid credentials');
+      await expect(authService.login('test@example.com', 'wrongPassword')).rejects.toThrow(
+        'Invalid credentials'
+      );
     });
   });
 });
@@ -78,17 +78,17 @@ describe('AuthService', () => {
 
 export class AuthService {
   constructor(private userRepository: UserRepository) {}
-  
+
   async login(email: string, password: string): Promise<AuthResult> {
     const user = await this.userRepository.findByEmail(email);
-    
+
     if (!user || !this.verifyPassword(password, user.passwordHash)) {
       throw new Error('Invalid credentials');
     }
-    
+
     return { success: true, user };
   }
-  
+
   private verifyPassword(password: string, hash: string): boolean {
     // Minimal implementation - just enough to pass test
     return bcrypt.compareSync(password, hash);
@@ -113,16 +113,16 @@ export class AuthService {
     private passwordService: PasswordService, // Extract dependency
     private logger: Logger // Add observability
   ) {}
-  
+
   async login(email: string, password: string): Promise<AuthResult> {
     const user = await this.findUserOrFail(email);
     await this.validatePasswordOrFail(password, user);
-    
+
     this.logger.info('User logged in', { userId: user.id });
-    
+
     return { success: true, user };
   }
-  
+
   private async findUserOrFail(email: string): Promise<User> {
     const user = await this.userRepository.findByEmail(email);
     if (!user) {
@@ -130,7 +130,7 @@ export class AuthService {
     }
     return user;
   }
-  
+
   private async validatePasswordOrFail(password: string, user: User): Promise<void> {
     const isValid = await this.passwordService.verify(password, user.passwordHash);
     if (!isValid) {
@@ -199,7 +199,7 @@ describe('POST /api/auth/login', () => {
     const response = await request(app)
       .post('/api/auth/login')
       .send({ email: 'user@test.com', password: 'password123' });
-    
+
     expect(response.status).toBe(200);
     expect(response.body.token).toBeDefined();
   });
@@ -211,7 +211,7 @@ describe('POST /api/auth/login', () => {
     const response = await request(app)
       .post('/api/auth/login')
       .send({ email: 'user@test.com', password: 'wrong' });
-    
+
     expect(response.status).toBe(401);
   });
 });
@@ -244,32 +244,32 @@ describe('[ClassName]', () => {
   // Setup
   let sut: ClassName; // System Under Test
   let mockDependency: jest.Mocked<Dependency>;
-  
+
   beforeEach(() => {
     mockDependency = {
       method: jest.fn(),
     };
     sut = new ClassName(mockDependency);
   });
-  
+
   describe('[methodName]', () => {
     it('should [expected behavior] when [condition]', () => {
       // Arrange
       const input = 'test input';
       mockDependency.method.mockReturnValue('mocked result');
-      
+
       // Act
       const result = sut.methodName(input);
-      
+
       // Assert
       expect(result).toBe('expected result');
       expect(mockDependency.method).toHaveBeenCalledWith(input);
     });
-    
+
     it('should throw [ErrorType] when [error condition]', () => {
       // Arrange
       const invalidInput = null;
-      
+
       // Act & Assert
       expect(() => sut.methodName(invalidInput)).toThrow(ErrorType);
     });
@@ -284,36 +284,36 @@ describe('[API Endpoint]', () => {
   // Setup
   let app: Express;
   let db: TestDatabase;
-  
+
   beforeAll(async () => {
     db = await TestDatabase.create();
     app = createApp({ database: db });
   });
-  
+
   afterAll(async () => {
     await db.close();
   });
-  
+
   beforeEach(async () => {
     await db.clear();
     await db.seed();
   });
-  
+
   describe('[HTTP Method] [Path]', () => {
     it('should return [status] when [condition]', async () => {
       // Arrange
       const payload = { key: 'value' };
-      
+
       // Act
       const response = await request(app)
         .post('/api/resource')
         .set('Authorization', `Bearer ${token}`)
         .send(payload);
-      
+
       // Assert
       expect(response.status).toBe(201);
       expect(response.body.id).toBeDefined();
-      
+
       // Verify side effects
       const record = await db.find('resources', response.body.id);
       expect(record).toBeDefined();
@@ -327,24 +327,28 @@ describe('[API Endpoint]', () => {
 ## Common Test-First Mistakes
 
 ### Mistake 1: Writing Test and Code Together
+
 ```
 ❌ Creating test and implementation in same commit
 ✅ Always commit test first, then implementation
 ```
 
 ### Mistake 2: Testing Implementation Details
+
 ```
 ❌ expect(service.internalCache.size).toBe(1);
 ✅ expect(service.getData()).toEqual(expectedData);
 ```
 
 ### Mistake 3: Skipping Integration Tests
+
 ```
 ❌ Only unit tests with mocks
 ✅ Integration tests first, then unit tests for gaps
 ```
 
 ### Mistake 4: Writing Too Many Tests at Once
+
 ```
 ❌ Writing 10 tests before any implementation
 ✅ One test at a time: RED → GREEN → REFACTOR
@@ -355,16 +359,19 @@ describe('[API Endpoint]', () => {
 ## Test-First Checklist
 
 Before implementation:
+
 - [ ] Test file created before source file
 - [ ] Test describes expected behavior
 - [ ] Test is failing (RED)
 
 During implementation:
+
 - [ ] Minimal code written to pass test
 - [ ] Test is passing (GREEN)
 - [ ] No code without corresponding test
 
 After implementation:
+
 - [ ] Code refactored for quality
 - [ ] Tests still passing
 - [ ] Test committed before source in git history

package/src/templates/agents/claude-code/skills/steering/SKILL.md

@@ -63,6 +63,7 @@ musubi-remember clear
 ```
 
 **ユースケース**:
+
 - セッション終了時の学習抽出・保存
 - チームメンバー間のナレッジ共有
 - プロジェクト間のベストプラクティス移植

package/src/templates/agents/claude-code/skills/steering/auto-update-rules.md

@@ -11,6 +11,7 @@ This document defines the rules for automatically detecting when steering files
 ### 1. New Dependencies Added
 
 **Detection**:
+
 ```bash
 # package.json changes (Node.js)
 git diff --name-only | grep -E "(package\.json|package-lock\.json)"
@@ -25,8 +26,10 @@ git diff --name-only | grep -E "go\.(mod|sum)"
 **Action**: Update `steering/tech.md` with new dependencies
 
 **Example**:
+
 ```markdown
 # Add to tech.md Dependencies section
+
 - **New**: express@4.18.0 (Web framework)
 - **New**: jest@29.0.0 (Testing framework)
 ```
@@ -36,6 +39,7 @@ git diff --name-only | grep -E "go\.(mod|sum)"
 ### 2. New Directory Structure Created
 
 **Detection**:
+
 ```bash
 # New directories created
 git diff --name-only --diff-filter=A | grep "/" | cut -d'/' -f1 | sort -u
@@ -44,6 +48,7 @@ git diff --name-only --diff-filter=A | grep "/" | cut -d'/' -f1 | sort -u
 **Action**: Update `steering/structure.md` with new directories
 
 **Patterns to Watch**:
+
 - `src/` - Source code organization
 - `lib/` - Library modules (Constitutional Article I)
 - `tests/` - Test organization
@@ -55,6 +60,7 @@ git diff --name-only --diff-filter=A | grep "/" | cut -d'/' -f1 | sort -u
 ### 3. Architecture Pattern Changes
 
 **Detection**:
+
 ```bash
 # Major architectural changes
 git diff --name-only | grep -E "(src/.*index\.(ts|js|py)|main\.(ts|js|py))"
@@ -66,9 +72,12 @@ find src -type d -maxdepth 2 -newer .git/COMMIT_EDITMSG
 **Action**: Update `steering/structure.md` with pattern changes
 
 **Example**:
+
 ```markdown
 # Update Architecture Patterns section
+
 ## Detected Pattern: Microservices
+
 - services/auth/
 - services/user/
 - services/order/
@@ -79,6 +88,7 @@ find src -type d -maxdepth 2 -newer .git/COMMIT_EDITMSG
 ### 4. Technology Stack Updates
 
 **Detection**:
+
 ```bash
 # Framework version updates
 git diff package.json | grep -E '"(react|vue|angular|express|fastapi)"'
@@ -94,6 +104,7 @@ git diff --name-only | grep -E "(webpack|vite|rollup|esbuild)\.config\."
 ### 5. New Feature Implementation
 
 **Detection**:
+
 ```bash
 # New feature directories
 git diff --name-only --diff-filter=A | grep "storage/features/"
@@ -146,9 +157,12 @@ git diff --name-only --diff-filter=A | grep "requirements\.md"
 **Trigger**: New ADR created in `storage/features/*/design.md`
 
 **Action**:
+
 ```markdown
 # Append to architecture_decisions.md
+
 ## ADR-XXX: [Decision Title]
+
 - **Date**: YYYY-MM-DD
 - **Status**: Accepted
 - **Context**: [Extracted from ADR]
@@ -160,9 +174,12 @@ git diff --name-only --diff-filter=A | grep "requirements\.md"
 **Trigger**: New CI/CD config or build scripts added
 
 **Action**:
+
 ```markdown
 # Update development_workflow.md
+
 ## Build Process
+
 - npm run build (detected from package.json)
 - npm test (detected from package.json)
 ```
@@ -172,9 +189,12 @@ git diff --name-only --diff-filter=A | grep "requirements\.md"
 **Trigger**: New business logic files or domain models
 
 **Action**:
+
 ```markdown
 # Update domain_knowledge.md
+
 ## Core Concepts
+
 - User: Represents system users (src/models/user.ts)
 - Order: Purchase transaction (src/models/order.ts)
 ```
@@ -184,9 +204,12 @@ git diff --name-only --diff-filter=A | grep "requirements\.md"
 **Trigger**: New CLI commands or scripts added
 
 **Action**:
+
 ```markdown
 # Update suggested_commands.md
+
 ## Development Commands
+
 - `npm run dev` - Start development server
 - `npm run test:watch` - Run tests in watch mode
 ```
@@ -196,9 +219,12 @@ git diff --name-only --diff-filter=A | grep "requirements\.md"
 **Trigger**: Post-mortem or retrospective files created
 
 **Action**:
+
 ```markdown
 # Append to lessons_learned.md
+
 ## [Date]: [Lesson Title]
+
 - **Context**: [What happened]
 - **Insight**: [What we learned]
 - **Action**: [What we changed]
@@ -231,17 +257,21 @@ diff <(grep "Feature" steering/product.md) <(ls storage/features/)
 ## Detected Issues
 
 ### tech.md
+
 - ⚠️ Missing: express@4.18.0 (added in package.json)
 - ⚠️ Outdated: react@17.0.0 → react@18.2.0
 
 ### structure.md
+
 - ⚠️ Missing directory: src/services/payment/
 - ⚠️ Removed directory: src/legacy/ (no longer exists)
 
 ### product.md
+
 - ⚠️ Missing feature: payment-integration (in storage/features/)
 
 ## Recommendations
+
 1. Run steering skill to update all files
 2. Review changes before committing
 ```
@@ -253,6 +283,7 @@ diff <(grep "Feature" steering/product.md) <(ls storage/features/)
 ### Git Hooks Integration
 
 **pre-commit hook**:
+
 ```bash
 #!/bin/bash
 # Check if steering files need update

package/src/templates/agents/claude-code/skills/system-architect/adr-template.md

@@ -34,24 +34,29 @@ We will...
 ## Consequences
 
 ### Positive
+
 - [Benefit 1]
 - [Benefit 2]
 
 ### Negative
+
 - [Tradeoff 1]
 - [Tradeoff 2]
 
 ### Neutral
+
 - [Neither positive nor negative consequence]
 
 ## Alternatives Considered
 
 ### Alternative 1: [Name]
+
 - **Pros**: [Benefits]
 - **Cons**: [Drawbacks]
 - **Reason for rejection**: [Why not chosen]
 
 ### Alternative 2: [Name]
+
 - **Pros**: [Benefits]
 - **Cons**: [Drawbacks]
 - **Reason for rejection**: [Why not chosen]
@@ -81,6 +86,7 @@ Accepted
 ## Context
 
 We need to choose a primary database for our e-commerce platform. The system needs to:
+
 - Handle complex relational data (users, orders, products)
 - Support ACID transactions for payment processing
 - Scale to 10,000+ concurrent users
@@ -93,6 +99,7 @@ Our team has experience with both PostgreSQL and MySQL. The project has 12 month
 We will use **PostgreSQL 16** as our primary database.
 
 Specific configuration:
+
 - Managed PostgreSQL on AWS RDS
 - Primary-replica setup for read scaling
 - pg_trgm extension for full-text search
@@ -101,6 +108,7 @@ Specific configuration:
 ## Consequences
 
 ### Positive
+
 - Rich feature set (JSON, full-text search, extensions)
 - Strong ACID compliance for financial transactions
 - Excellent open-source community support
@@ -108,27 +116,32 @@ Specific configuration:
 - Cost-effective (open source)
 
 ### Negative
+
 - More complex configuration than MySQL
 - Requires dedicated DBA knowledge for optimization
 - Memory-intensive for complex queries
 
 ### Neutral
+
 - Similar performance to MySQL for our use case
 - Learning curve for advanced features (CTEs, window functions)
 
 ## Alternatives Considered
 
 ### Alternative 1: MySQL 8.0
+
 - **Pros**: Simpler setup, lower memory footprint, wide hosting support
 - **Cons**: Weaker JSON support, limited extensions
 - **Reason for rejection**: PostgreSQL's richer feature set better suits complex e-commerce queries
 
 ### Alternative 2: MongoDB
+
 - **Pros**: Flexible schema, horizontal scaling, JSON-native
 - **Cons**: Weak transactions, eventual consistency concerns for payments
 - **Reason for rejection**: ACID transactions required for financial operations
 
 ### Alternative 3: CockroachDB
+
 - **Pros**: Distributed, PostgreSQL-compatible, auto-scaling
 - **Cons**: Higher cost, newer technology, fewer DBAs available
 - **Reason for rejection**: Overkill for initial scale, can migrate later if needed
@@ -145,30 +158,35 @@ Specific configuration:
 ## ADR Categories
 
 ### Technology Selection
+
 - Database choice
 - Framework selection
 - Cloud provider
 - Third-party services
 
 ### Architecture Patterns
+
 - Microservices vs. Monolith
 - Event-driven architecture
 - API design (REST vs. GraphQL)
 - Caching strategy
 
 ### Development Practices
+
 - Testing strategy
 - CI/CD approach
 - Code organization
 - Dependency management
 
 ### Security
+
 - Authentication method
 - Authorization model
 - Data encryption
 - Secret management
 
 ### Performance
+
 - Scaling strategy
 - Caching layers
 - Database optimization
@@ -274,17 +292,17 @@ docs/
 
 ## Active ADRs
 
-| ADR | Title | Date | Status |
-|-----|-------|------|--------|
+| ADR                            | Title                              | Date       | Status   |
+| ------------------------------ | ---------------------------------- | ---------- | -------- |
 | [ADR-001](ADR-001-database.md) | Use PostgreSQL as Primary Database | 2025-01-15 | Accepted |
-| [ADR-002](ADR-002-caching.md) | Use Redis for Caching | 2025-01-16 | Accepted |
-| [ADR-003](ADR-003-auth.md) | Use JWT for Authentication | 2025-01-17 | Accepted |
+| [ADR-002](ADR-002-caching.md)  | Use Redis for Caching              | 2025-01-16 | Accepted |
+| [ADR-003](ADR-003-auth.md)     | Use JWT for Authentication         | 2025-01-17 | Accepted |
 
 ## Superseded ADRs
 
-| ADR | Title | Superseded By |
-|-----|-------|---------------|
-| [ADR-004](ADR-004-old-api.md) | REST API v1 Design | ADR-010 |
+| ADR                           | Title              | Superseded By |
+| ----------------------------- | ------------------ | ------------- |
+| [ADR-004](ADR-004-old-api.md) | REST API v1 Design | ADR-010       |
 
 ## How to Propose a New ADR