Merge pull request #10 from bulgogi-whopper/feat/deploy-kiro

feat: Deploy to Kiro

Author: mixxeo

.kiro/specs/kiro-deploy-support/design.md

@@ -0,0 +1,170 @@
+# Implementation Plan
+
+## Overview
+
+This document outlines the implementation plan for adding Kiro IDE deployment support to the existing Taptik CLI. The current codebase already has significant infrastructure in place, including platform type definitions, build system support for Kiro, and deployment architecture. This plan focuses on the remaining tasks needed to enable Kiro deployment functionality.
+
+## Current State Analysis
+
+✅ **Already Implemented:**
+
+- Platform type definitions include 'kiro' support (`SupportedPlatform`)
+- Complete build system with Kiro as primary platform
+- Deployment infrastructure (services, interfaces, error handling)
+- Deploy command structure with Claude Code support
+
+🔄 **Needs Implementation:**
+
+- Kiro-specific deployment logic and transformations
+- Kiro component handlers and file writers
+- Platform routing to support multiple targets
+- Kiro-specific validation and conflict resolution
+
+## Implementation Priority
+
+1. **Core Kiro Deployment**: Platform routing and basic Kiro deployment service
+2. **Component Handlers**: Kiro-specific component deployment logic
+3. **Data Transformation**: Taptik format to Kiro format conversion
+4. **Validation & Conflict Resolution**: Kiro-specific validation and file conflict handling
+5. **Testing & Documentation**: Comprehensive test coverage and documentation
+
+- [x] 1.1 Platform type definitions for Kiro support
+  - ✅ `SupportedPlatform` already includes 'kiro' in `src/modules/deploy/interfaces/component-types.interface.ts`
+  - ✅ Build system already supports Kiro as primary platform
+  - _Requirements: 1.2_
+
+- [x] 1.2 Add Kiro platform support to deploy command
+  - Update `src/modules/deploy/commands/deploy.command.ts` to accept and handle `--platform kiro`
+  - Remove hardcoded Claude Code restriction
+  - Add Kiro platform validation in `parsePlatform` method
+  - Update command description and help text
+  - _Requirements: 1.1, 1.3, 4.1_
+  - _Estimated: 0.5 days_
+
+- [x] 1.3 Implement platform routing in deployment service
+  - Add `deployToKiro` method to `DeploymentService`
+  - Update deploy command to route to appropriate deployment method based on platform
+  - Create platform-specific deployment options handling
+  - Add basic error handling for unsupported platform combinations
+  - _Dependencies: 1.2_
+  - _Requirements: 1.2, 1.3_
+  - _Estimated: 1 day_
+
+- [x] 2.1 Create Kiro-specific interfaces and types
+  - Create `src/modules/deploy/interfaces/kiro-deployment.interface.ts` for Kiro deployment types
+  - Define `KiroDeploymentOptions`, `KiroComponentType`, `KiroConflictStrategy` interfaces
+  - Add Kiro-specific configuration models (settings, steering, specs, hooks, agents)
+  - Update existing interfaces to support Kiro platform
+  - _Dependencies: 1.3_
+  - _Requirements: 2.1, 10.1_
+  - _Estimated: 1 day_
+
+- [x] 2.2 Implement Kiro data transformation service
+  - Create `src/modules/deploy/services/kiro-transformer.service.ts`
+  - Implement `transformPersonalContext()` - TaptikPersonalContext to Kiro global settings
+  - Implement `transformProjectContext()` - TaptikProjectContext to Kiro project settings and steering
+  - Implement `transformPromptTemplates()` - TaptikPromptTemplates to Kiro templates
+  - Add transformation validation and error handling
+  - _Dependencies: 2.1_
+  - _Requirements: 9.1, 9.2, 9.3, 17.1, 17.2, 17.3_
+  - _Estimated: 3 days_
+
+- [x] 2.3 Create Kiro component deployment handlers
+  - Create `src/modules/deploy/services/kiro-component-handler.service.ts`
+  - Implement `deploySettings()` - deploy to `~/.kiro/settings.json` and `.kiro/settings.json`
+  - Implement `deploySteering()` - deploy steering documents to `.kiro/steering/`
+  - Implement `deploySpecs()` - deploy specs to `.kiro/specs/` with proper structure
+  - Implement `deployHooks()` - deploy hooks to `.kiro/hooks/`
+  - Implement `deployAgents()` - deploy agents to `~/.kiro/agents/`
+  - _Dependencies: 2.2_
+  - _Requirements: 2.2, 2.3, 2.4, 2.5, 2.6, 10.1, 10.2, 10.3, 10.4_
+  - _Estimated: 4 days_
+
+- [x] 3.1 Implement Kiro validation service
+  - Create `src/modules/deploy/services/kiro-validator.service.ts`
+  - Implement `validateForKiro()` method similar to existing `validateForPlatform()`
+  - Add Kiro-specific schema validation for components
+  - Implement business rule validation (required fields, file size limits, etc.)
+  - Add validation reporting with actionable error messages
+  - _Dependencies: 2.3_
+  - _Requirements: 3.1, 3.2, 3.3, 11.1, 11.2_
+  - _Estimated: 2 days_
+
+- [x] 3.2 Create Kiro file conflict resolution service
+  - Create `src/modules/deploy/services/kiro-conflict-resolver.service.ts`
+  - Implement conflict detection for Kiro configuration files
+  - Add intelligent merging for JSON settings files
+  - Implement content-aware merging for markdown steering documents
+  - Add conflict resolution strategies (prompt, merge, backup, skip, overwrite)
+  - Handle task completion status preservation in specs
+  - _Dependencies: 2.3_
+  - _Requirements: 5.1, 5.2, 5.3, 5.4, 5.5, 12.3, 12.4_
+  - _Estimated: 3 days_
+
+- [x] 3.3 Implement Kiro security scanning
+  - Extend existing `SecurityScannerService` to support Kiro components
+  - Add Kiro-specific security rules for hooks, agents, and templates
+  - Implement malicious pattern detection for Kiro hook configurations
+  - Add agent capability validation and security scanning
+  - Create security violation reporting and quarantine system
+  - _Dependencies: 2.3_
+  - _Requirements: 7.1, 7.2, 17.3_
+  - _Estimated: 2 days_
+
+- [x] 4.1 Integrate Kiro deployment into main deployment service
+  - Add `deployToKiro()` method to existing `DeploymentService`
+  - Implement Kiro deployment orchestration using existing infrastructure
+  - Integrate with existing backup, security, and performance monitoring services
+  - Add Kiro-specific error handling and recovery
+  - Update deployment result reporting for Kiro components
+  - _Dependencies: 3.3_
+  - _Requirements: 2.1, 6.1, 6.2, 13.1, 13.2_
+  - _Estimated: 2 days_
+
+- [x] 4.2 Implement Kiro installation detection and compatibility
+  - Create `src/modules/deploy/services/kiro-installation-detector.service.ts`
+  - Implement Kiro installation detection and version checking
+  - Add existing configuration analysis and compatibility validation
+  - Create migration support for different Kiro versions
+  - Add installation health checks and recommendations
+  - _Dependencies: 4.1_
+  - _Requirements: 12.1, 12.6, 14.1, 14.2_
+  - _Estimated: 2 days_
+
+- [x] 5.1 Add comprehensive unit tests for Kiro services
+  - Create unit tests for `KiroTransformerService` with all transformation scenarios
+  - Add unit tests for `KiroComponentHandlerService` with mock file system
+  - Create unit tests for `KiroValidatorService` with validation edge cases
+  - Add unit tests for `KiroConflictResolverService` with different conflict types
+  - Test error handling and edge cases for all Kiro services
+  - _Dependencies: 4.2_
+  - _Requirements: All requirements - testing coverage_
+  - _Estimated: 3 days_
+
+- [ ] 5.2 Create integration tests for Kiro deployment workflows
+  - Add end-to-end integration tests for complete Kiro deployment
+  - Test integration between transformation, validation, and deployment services
+  - Create tests for conflict resolution and backup/rollback scenarios
+  - Add performance tests for large Kiro configurations
+  - Test compatibility with different Kiro installation states
+  - _Dependencies: 5.1_
+  - _Requirements: All requirements - integration testing_
+  - _Estimated: 3 days_
+
+- [ ] 6.1 Update CLI help and documentation
+  - Update deploy command help text to include Kiro platform option
+  - Add Kiro-specific CLI option documentation
+  - Create usage examples for Kiro deployment scenarios
+  - Update error messages to include Kiro-specific guidance
+  - _Dependencies: 5.2_
+  - _Requirements: 8.1, 8.2, 8.3, 8.4, 8.5_
+  - _Estimated: 1 day_
+
+- [ ] 6.2 Create user documentation and guides
+  - Write comprehensive user guide for Kiro deployment
+  - Create step-by-step deployment examples
+  - Add troubleshooting guide for common Kiro deployment issues
+  - Document Kiro-specific component mapping and transformation rules
+  - _Dependencies: 6.1_
+  - _Requirements: 8.1, 8.2_
+  - _Estimated: 2 days_

.kiro/specs/kiro-deploy-support/requirements.md

@@ -4,10 +4,10 @@ import { TerminusModule } from '@nestjs/terminus';
 
 import { HealthCommand } from './commands/health.command';
 import { AuthModule } from './modules/auth/auth.module';
-import { InfoModule } from './modules/info/info.module';
 import { BuildModule } from './modules/build/build.module';
 import { ContextModule } from './modules/context/context.module';
 import { DeployModule } from './modules/deploy/deploy.module';
+import { InfoModule } from './modules/info/info.module';
 
 @Module({
   imports: [

.kiro/specs/kiro-deploy-support/tasks.md

@@ -264,7 +264,7 @@ export class ErrorHandlerService {
   handleCriticalErrorAndExit(error: CriticalError): never {
     this.addCriticalError(error);
     this.displayErrorSummary();
-    // eslint-disable-next-line unicorn/no-process-exit
+     
     process.exit(error.exitCode);
   }
 
@@ -277,18 +277,18 @@ export class ErrorHandlerService {
         ...this.errorSummary.criticalErrors.map(error => error.exitCode),
         1
       );
-      // eslint-disable-next-line unicorn/no-process-exit
+       
       process.exit(highestExitCode);
     }
 
     if (this.hasWarnings()) {
       console.log('\n✅ Build completed with warnings');
-      // eslint-disable-next-line unicorn/no-process-exit
+       
       process.exit(0);
     }
 
     console.log('\n✅ Build completed successfully');
-    // eslint-disable-next-line unicorn/no-process-exit
+     
     process.exit(0);
   }
 

src/app.module.ts

@@ -2,11 +2,9 @@ import { Injectable } from '@nestjs/common';
 
 import { Command, CommandRunner, Option } from 'nest-commander';
 
-import {
-  ComponentType,
-  SupportedPlatform,
-} from '../interfaces/component-types.interface';
-import { ConflictStrategy } from '../interfaces/conflict-strategy.interface';
+import { ComponentType } from '../interfaces/component-types.interface';
+import { SupportedPlatform, ConflictStrategy } from '../interfaces/deploy-options.interface';
+import { DeploymentResult } from '../interfaces/deployment-result.interface';
 import { DeploymentService } from '../services/deployment.service';
 import { ImportService } from '../services/import.service';
 
@@ -23,7 +21,7 @@ interface DeployCommandOptions {
 
 @Command({
   name: 'deploy',
-  description: 'Deploy Taptik context to target platform (Claude Code)',
+  description: 'Deploy Taptik context to target platform (Claude Code, Kiro IDE)',
 })
 @Injectable()
 export class DeployCommand extends CommandRunner {
@@ -40,15 +38,17 @@ export class DeployCommand extends CommandRunner {
   ): Promise<void> {
     try {
       // Set default platform
-      const platform = options.platform || 'claudeCode';
+      const platform = options.platform || 'claude-code';
 
-      if (platform !== 'claudeCode') {
+      if (platform !== 'claude-code' && platform !== 'kiro-ide') {
         console.error(
-          `❌ Platform '${platform}' is not supported. Only 'claudeCode' is currently available.`,
+          `❌ Platform '${platform}' is not supported. Supported platforms: 'claude-code', 'kiro-ide'`,
         );
         process.exit(1);
       }
 
+      // Note: Kiro deployment will show feature development status in results
+
       console.log(`🚀 Starting deployment to ${platform}...`);
 
       // Step 1: Import context from Supabase
@@ -68,27 +68,39 @@ export class DeployCommand extends CommandRunner {
 
       // Step 2: Prepare deployment options
       const deployOptions = {
-        platform: 'claude-code' as const,
+        platform: platform as SupportedPlatform,
         dryRun: options.dryRun || false,
         validateOnly: options.validateOnly || false,
         conflictStrategy: options.conflictStrategy || 'prompt',
         components: options.components?.map((c) => c as ComponentType),
         skipComponents: options.skipComponents?.map((c) => c as ComponentType),
       };
 
-      // Step 3: Deploy to Claude Code
+      // Step 3: Deploy to target platform
       if (options.validateOnly) {
         console.log('🔍 Running validation only...');
       } else if (options.dryRun) {
         console.log('🧪 Running in dry-run mode...');
       } else {
-        console.log('🚀 Deploying to Claude Code...');
+        console.log(`🚀 Deploying to ${platform === 'claude-code' ? 'Claude Code' : 'Kiro IDE'}...`);
       }
 
-      const result = await this.deploymentService.deployToClaudeCode(
-        context,
-        deployOptions,
-      );
+      // Step 3: Route to appropriate deployment method based on platform
+      let result: DeploymentResult;
+      if (platform === 'claude-code') {
+        result = await this.deploymentService.deployToClaudeCode(
+          context,
+          deployOptions,
+        );
+      } else if (platform === 'kiro-ide') {
+        result = await this.deploymentService.deployToKiro(
+          context,
+          deployOptions,
+        );
+      } else {
+        console.error(`❌ Platform '${platform}' deployment is not implemented yet.`);
+        process.exit(5); // Platform Error exit code
+      }
 
       // Step 4: Display results
       if (result.success) {
@@ -136,12 +148,13 @@ export class DeployCommand extends CommandRunner {
 
   @Option({
     flags: '-p, --platform <platform>',
-    description: 'Target platform (currently only "claudeCode" is supported)',
-    defaultValue: 'claudeCode',
+    description: 'Target platform ("claude-code" or "kiro-ide")',
+    defaultValue: 'claude-code',
   })
   parsePlatform(value: string): SupportedPlatform {
-    if (value !== 'claudeCode') {
-      throw new Error(`Unsupported platform: ${value}`);
+    const supportedPlatforms: SupportedPlatform[] = ['claude-code', 'kiro-ide'];
+    if (!supportedPlatforms.includes(value as SupportedPlatform)) {
+      throw new Error(`Unsupported platform: ${value}. Supported platforms: ${supportedPlatforms.join(', ')}`);
     }
     return value as SupportedPlatform;
   }

src/modules/build/services/error-handler/error-handler.service.ts

@@ -10,6 +10,11 @@ import { DiffService } from './services/diff.service';
 import { ErrorHandlerService } from './services/error-handler.service';
 import { ErrorRecoveryService } from './services/error-recovery.service';
 import { ImportService } from './services/import.service';
+import { KiroComponentHandlerService } from './services/kiro-component-handler.service';
+import { KiroConflictResolverService } from './services/kiro-conflict-resolver.service';
+import { KiroInstallationDetectorService } from './services/kiro-installation-detector.service';
+import { KiroTransformerService } from './services/kiro-transformer.service';
+import { KiroValidatorService } from './services/kiro-validator.service';
 import { LargeFileStreamerService } from './services/large-file-streamer.service';
 import { LockingService } from './services/locking.service';
 import { PerformanceMonitorService } from './services/performance-monitor.service';
@@ -32,6 +37,11 @@ import { PerformanceOptimizer } from './utils/performance-optimizer.utility';
     ErrorHandlerService,
     ErrorRecoveryService,
     ImportService,
+    KiroComponentHandlerService,
+    KiroConflictResolverService,
+    KiroInstallationDetectorService,
+    KiroTransformerService,
+    KiroValidatorService,
     LargeFileStreamerService,
     LockingService,
     PerformanceMonitorService,

src/modules/deploy/commands/deploy.command.ts

@@ -1,3 +1,15 @@
 export type ComponentType = 'settings' | 'agents' | 'commands' | 'project';
 
-export type SupportedPlatform = 'claudeCode' | 'kiro' | 'cursor' | 'windsurf';
+export type SupportedPlatform = 'claude-code' | 'kiro-ide' | 'cursor-ide';
+
+// Extended component types for different platforms
+export type ClaudeCodeComponentType = ComponentType;
+export type KiroComponentType = 'settings' | 'steering' | 'specs' | 'hooks' | 'agents' | 'templates';
+export type CursorComponentType = ComponentType;
+
+// Platform-specific component mapping
+export type PlatformComponentType<T extends SupportedPlatform> = 
+  T extends 'claude-code' ? ClaudeCodeComponentType :
+  T extends 'kiro-ide' ? KiroComponentType :
+  T extends 'cursor-ide' ? CursorComponentType :
+  never;

src/modules/deploy/deploy.module.ts

@@ -3,3 +3,4 @@ export * from './deployment-result.interface';
 export * from './platform-config.interface';
 export * from './security-config.interface';
 export * from './merge-strategy.interface';
+export * from './kiro-deployment.interface';