moai-adk 0.8.0__py3-none-any.whl → 1.1.0__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-workflow-project/README.md

@@ -0,0 +1,190 @@
+# MoAI Menu Project Configuration Management
+
+Unified configuration management system for MoAI menu project operations, integrating 5 specialized modules into a single cohesive system.
+
+## Overview
+
+This skill replaces 5 separate configuration management skills with a unified system that provides:
+
+- Centralized Configuration: Single source of truth for all menu project settings
+- Legacy Migration: Automatic detection and migration from existing configurations
+- Module Specialization: Dedicated managers for each functional area
+- Validation Framework: JSON Schema validation and business rule checking
+- Performance Optimization: Caching and efficient file handling
+
+## Quick Start
+
+```python
+from moai_menu_project import create_config_manager, ConfigurationMigrator
+
+# Initialize configuration manager
+config_manager = create_config_manager("/path/to/config")
+
+# Migrate legacy configurations
+migrator = ConfigurationMigrator(config_manager)
+result = migrator.detect_and_migrate(backup=True)
+
+# Access module-specific configuration
+from moai_menu_project import BatchQuestionsConfigManager
+batch_manager = BatchQuestionsConfigManager(config_manager)
+settings = batch_manager.get_config()
+```
+
+## Architecture
+
+### Core Components
+
+1. UnifiedConfigManager: Centralized configuration with JSON Schema validation
+2. ConfigurationMigrator: Legacy configuration detection and migration
+3. Module Managers: Specialized access for each functional area
+4. Validation Framework: Schema and business rule validation
+5. Backup/Recovery: Automatic backup creation and rollback
+
+### Supported Modules
+
+- Batch Questions: Batch processing configuration
+- Documentation: Documentation generation settings 
+- Language Config: Internationalization and localization
+- Template Optimizer: Template processing optimization
+- Project Initializer: Project setup and initialization
+
+## Migration Guide
+
+### From Legacy Configurations
+
+The system automatically detects and migrates legacy configuration files:
+
+1. Detection: Scans for legacy configuration patterns
+2. Transformation: Converts to unified format with version-specific rules
+3. Validation: Ensures migrated data meets schema requirements
+4. Backup: Creates backup before applying changes
+5. History: Records migration for audit and rollback
+
+### Example Migration
+
+```python
+# Preview migration changes
+preview = migrator.preview_migration()
+print(f"Will migrate {preview['migrated']} files")
+
+# Execute migration
+result = migrator.detect_and_migrate(backup=True)
+print(f"Successfully migrated {result['migrated']} configurations")
+```
+
+## Configuration Schema
+
+The unified configuration follows this structure:
+
+```json
+{
+ "version": "1.0.0",
+ "metadata": {
+ "created_at": "timestamp",
+ "updated_at": "timestamp",
+ "migration_history": [...]
+ },
+ "project_settings": {...},
+ "batch_questions": {...},
+ "documentation": {...},
+ "language_config": {...},
+ "template_optimizer": {...},
+ "project_initializer": {...}
+}
+```
+
+See `schemas/config-schema.json` for complete schema definition.
+
+## File Structure
+
+```
+moai-menu-project/
+ SKILL.md # Main skill documentation
+ README.md # This file
+ __init__.py # Package initialization
+ modules/
+ config_manager.py # Core configuration management
+ migration_manager.py # Legacy migration system
+ schemas/
+ config-schema.json # JSON Schema for validation
+ examples/
+ config-migration-example.json # Migration example
+```
+
+## Integration
+
+### With MoAI Ecosystem
+
+- moai-cc-configuration: Claude Code configuration patterns
+- moai-core-workflow: Workflow-based configuration management
+- moai-quality-security: Security validation and compliance
+
+### External Systems
+
+- Environment variable overrides
+- CLI argument integration
+- API endpoint for dynamic updates
+- Monitoring and observability integration
+
+## Validation
+
+The system provides comprehensive validation:
+
+- JSON Schema: Structural validation with type checking
+- Business Rules: Custom validation logic for consistency
+- Security: Compliance checking and constraint enforcement
+- Performance: Resource limit and efficiency validation
+
+## Performance
+
+Optimizations include:
+
+- Caching: In-memory caching with file modification monitoring
+- Lazy Loading: Load only required configuration sections
+- Concurrent Access: Thread-safe operations with locking
+- Resource Management: Efficient file handling and memory usage
+
+## Security
+
+Features for secure configuration management:
+
+- Access Control: Role-based permissions for configuration access
+- Encryption: Sensitive field encryption and secure key management
+- Audit Logging: Comprehensive change tracking and audit trails
+- Data Protection: Secure backup storage and transmission
+
+## Troubleshooting
+
+Common issues and solutions:
+
+### Schema Validation Errors
+- Check JSON structure against schema
+- Verify required fields are present
+- Ensure data types match schema definitions
+
+### Migration Issues
+- Review legacy file detection patterns
+- Check transformation rules for specific versions
+- Verify file permissions and access rights
+
+### Performance Problems
+- Enable caching for frequently accessed configurations
+- Use lazy loading for large configuration files
+- Monitor resource usage and optimize file access patterns
+
+## Support
+
+For issues and questions:
+
+1. Check the troubleshooting section above
+2. Review migration examples and schema documentation
+3. Examine error messages for specific guidance
+4. Validate configuration against schema
+
+## Version History
+
+- 1.0.0: Initial release with unified configuration management
+- Automatic migration from 5 legacy skill configurations
+- JSON Schema validation and business rule checking
+- Performance optimization with caching and lazy loading
+- Security features with access control and audit logging

moai_adk/templates/.claude/skills/moai-workflow-project/SKILL.md

@@ -0,0 +1,287 @@
+---
+name: "moai-workflow-project"
+description: "Integrated project management system with documentation, language initialization, and template optimization modules. Use when setting up projects, generating documentation, configuring multilingual support, or optimizing templates."
+version: 2.0.0
+category: "workflow"
+modularized: true
+user-invocable: false
+tags: ["workflow", "project", "documentation", "initialization", "templates"]
+updated: 2026-01-08
+status: "active"
+aliases: ["moai-workflow-project"]
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Grep
+  - Glob
+  - mcp__context7__resolve-library-id
+  - mcp__context7__get-library-docs
+---
+
+# MoAI Workflow Project - Integrated Project Management System
+
+Purpose: Comprehensive project management system that integrates documentation generation, multilingual support, and template optimization into unified architecture with intelligent automation and Claude Code integration.
+
+Scope: Consolidates documentation management, language initialization, and template optimization into single cohesive system supporting complete project lifecycle from initialization to maintenance.
+
+Target: Claude Code agents for project setup, documentation generation, multilingual support, and performance optimization.
+
+---
+
+## Quick Reference
+
+Core Capabilities:
+
+- Documentation Management: Template-based documentation generation with multilingual support
+- Language Initialization: Language detection, configuration, and localization management
+- Template Optimization: Advanced template analysis and performance optimization
+- Unified Interface: Single entry point integrating all capabilities
+
+Key Features:
+
+- Automatic project type detection and template selection
+- Multilingual documentation generation supporting English, Korean, Japanese, and Chinese
+- Intelligent template optimization with performance benchmarking
+- SPEC-driven documentation updates
+- Multi-format export including Markdown, HTML, and PDF
+
+Supported Project Types:
+
+- Web applications
+- Mobile applications
+- Command-line interface tools
+- Libraries and packages
+- Machine learning projects
+
+---
+
+## Implementation Guide
+
+### Module Architecture
+
+Documentation Management Capabilities:
+
+- Template-based documentation generation
+- Project type detection for web, mobile, CLI, library, and ML projects
+- Multilingual support with localized content
+- SPEC data integration for automatic updates
+- Multi-format export capabilities
+
+Language Initialization Capabilities:
+
+- Automatic language detection from project content
+- Comprehensive language configuration management
+- Agent prompt localization with cost optimization
+- Domain-specific language support
+- Locale management and cultural adaptation
+
+Template Optimization Capabilities:
+
+- Advanced template analysis with complexity metrics
+- Performance optimization with size reduction
+- Intelligent backup and recovery system
+- Benchmarking and performance tracking
+- Automated optimization recommendations
+
+### Core Workflows
+
+Complete Project Initialization Workflow:
+
+Step 1: Initialize the project management system by specifying the project directory path
+
+Step 2: Execute complete setup with the following configuration parameters:
+
+- Language setting: Specify the primary language code such as "en" for English or "ko" for Korean
+- User name: Provide the developer or team name for personalization
+- Domains: List the project domains such as backend, frontend, and mobile
+- Project type: Specify the project type such as web_application
+- Optimization enabled: Set to true to enable template optimization during initialization
+
+Step 3: Review initialization results which include:
+
+- Language configuration with token cost analysis
+- Documentation structure creation status
+- Template analysis and optimization report
+- Multilingual documentation setup confirmation
+
+Documentation Generation from SPEC Workflow:
+
+Step 1: Prepare SPEC data with the following structure:
+
+- Identifier: Unique SPEC ID such as SPEC-001
+- Title: Feature or component title
+- Description: Brief description of the implementation
+- Requirements: List of specific requirements
+- Status: Current status such as Planned, In Progress, or Complete
+- Priority: Priority level such as High, Medium, or Low
+- API Endpoints: List of endpoint definitions including path, method, and description
+
+Step 2: Generate comprehensive documentation from the SPEC data
+
+Step 3: Review generated documentation which includes:
+
+- Feature documentation with requirements
+- API documentation with endpoint details
+- Updated project documentation files
+- Multilingual versions if configured
+
+Template Performance Optimization Workflow:
+
+Step 1: Analyze current templates to gather metrics
+
+Step 2: Configure optimization options:
+
+- Backup first: Set to true to create backup before optimization
+- Apply size optimizations: Enable to reduce file sizes
+- Apply performance optimizations: Enable to improve loading times
+- Apply complexity optimizations: Enable to simplify template structures
+- Preserve functionality: Ensure all features remain intact
+
+Step 3: Execute optimization and review results:
+
+- Size reduction percentage achieved
+- Performance improvement metrics
+- Backup creation confirmation
+- Detailed optimization report
+
+### Language and Localization
+
+Automatic Language Detection Process:
+
+The system analyzes the project for language indicators using the following methods:
+
+- File content analysis examining comments and strings
+- Configuration file examination for locale settings
+- System locale detection
+- Directory structure patterns
+
+Multilingual Documentation Structure:
+
+When creating documentation for multiple languages, the system generates:
+
+- Language-specific documentation directories such as docs/ko for Korean and docs/en for English
+- Language negotiation configuration
+- Automatic redirection setup between language versions
+
+Agent Prompt Localization:
+
+The localization system provides:
+
+- Language-specific instructions for agents
+- Cultural context adaptations
+- Token cost optimization recommendations for multilingual prompts
+
+### Template Optimization
+
+Performance Analysis Process:
+
+Template analysis provides the following metrics:
+
+- File size and complexity measurements
+- Performance bottleneck identification
+- Optimization opportunity scoring
+- Resource usage patterns
+- Backup recommendations
+
+Intelligent Optimization Process:
+
+The optimization system applies the following techniques:
+
+- Whitespace and redundancy reduction
+- Template structure optimization
+- Complexity reduction techniques
+- Performance caching improvements
+
+### Configuration Management
+
+Integrated Configuration Status:
+
+The project status includes:
+
+- Project metadata and type classification
+- Language configuration and associated costs
+- Documentation completion status
+- Template optimization results
+- Module initialization states
+
+Language Settings Update Process:
+
+When updating language settings, configure the following parameters:
+
+- Conversation language: The language for user-facing responses
+- Agent prompt language: The language for internal agent instructions, often kept as English for cost optimization
+- Documentation language: The language for generated documentation
+
+Updates trigger the following automatic changes:
+
+- Configuration file modifications
+- Documentation structure updates
+- Template localization adjustments
+
+---
+
+## Advanced Implementation
+
+For advanced patterns including custom template development, performance optimization strategies, and integration workflows, see reference.md which covers:
+
+- Custom Templates: Creating project-type-specific documentation templates
+- Performance Caching: Implementing template caching for improved performance
+- Batch Processing: Efficiently processing multiple templates simultaneously
+- Integration Workflows: Complete project lifecycle and multilingual management
+
+---
+
+## Resources
+
+### Configuration Structure
+
+Project Configuration Fields:
+
+- Project name: The display name for the project
+- Project type: Classification such as web_application, mobile_application, or cli_tool
+- Initialization timestamp: When the project was initialized
+- Language configuration: Conversation, agent prompt, and documentation language settings
+- System version: The project management system version
+- Initialization status: Whether all modules are fully initialized
+
+Language Configuration Fields for Each Supported Language:
+
+- Name: Display name in English
+- Native name: Display name in the native language
+- Code: Language code such as en, ko, ja, or zh
+- Locale: System locale string
+- Agent prompt language: Whether to use English or localized prompts
+- Token cost impact: Percentage increase in token usage for non-English prompts
+
+### Performance Metrics
+
+Documentation Generation Performance:
+
+- Complete documentation generation typically completes within 2 to 5 seconds
+- Language detection analysis completes within approximately 500 milliseconds
+- Template optimization duration varies from 10 to 30 seconds depending on project size
+- Configuration updates complete within approximately 100 milliseconds
+
+Memory Usage Characteristics:
+
+- Base system requires approximately 50MB RAM
+- Large projects may require an additional 10 to 50MB depending on template count
+- Optimization cache uses approximately 5 to 20MB for performance improvements
+
+File Size Impact:
+
+- Documentation files range from 50 to 200KB per project
+- Optimization backups match the size of original templates
+- Configuration files range from 5 to 10KB for complete project setup
+
+---
+
+## Works Well With
+
+- moai-foundation-core: Core execution patterns and SPEC-driven development workflows
+- moai-foundation-claude: Claude Code integration and configuration
+- moai-workflow-docs: Unified documentation management
+- moai-workflow-templates: Template optimization strategies
+- moai-library-nextra: Advanced documentation architecture