appiq-solution 1.4.8 → 1.4.9

package/SuperClaude/.claude/commands/shared/migration-report.md

@@ -1,165 +0,0 @@
-# Command Files Template Migration Report
-
-## Overview
-
-Successfully migrated 18 out of 19 command files to use the expanded template system, achieving significant token reduction and consistency improvements.
-
-## Files Updated
-
-✅ **Completed (18 files):**
-- analyze.md (already optimized)
-- build.md (already optimized)  
-- cleanup.md
-- deploy.md
-- design.md
-- dev-setup.md
-- document.md
-- estimate.md
-- explain.md
-- git.md (already optimized)
-- improve.md
-- index.md
-- load.md
-- migrate.md
-- scan.md
-- spawn.md
-- test.md
-- troubleshoot.md
-
-⚠️ **Not Updated (1 file):**
-- task.md (already using specialized format)
-
-## Template System Changes Applied
-
-### 1. Legend Replacement
-**Before:** ~180 tokens per file
-```markdown
-## Legend
-| Symbol | Meaning | | Abbrev | Meaning |
-|--------|---------|---|--------|---------|
-| → | leads to | | cfg | configuration |
-| & | and/with | | deps | dependencies |
-| w/ | with | | vuln | vulnerability |
-```
-
-**After:** ~40 tokens per file
-```markdown
-@include shared/constants.yml#Process_Symbols
-```
-
-### 2. Command Header Standardization
-**Before:** ~25 tokens per file
-```markdown
-Execute immediately. Add --plan flag if user wants to see plan first.
-```
-
-**After:** ~35 tokens per file (includes universal flags)
-```markdown
-@include shared/command-templates.yml#Universal_Flags
-```
-
-### 3. Research Requirements
-**Before:** ~120 tokens per file
-```markdown
-Research requirements:
-- Framework patterns → C7 documentation lookup required
-- Best practices → WebSearch for official guides
-- Never implement without documentation backing
-- All implementations must cite sources: // Source: [guide reference]
-```
-
-**After:** ~40 tokens per file
-```markdown
-@include shared/command-templates.yml#Research_Requirements
-```
-
-### 4. Report Output Sections
-**Before:** ~100 tokens per file
-```markdown
-Report Output:
-- Analysis reports: `.claudedocs/reports/analysis-<timestamp>.md`
-- Ensure directory exists: `mkdir -p .claudedocs/reports/`
-- Include report location in output: "📄 Report saved to: [path]"
-```
-
-**After:** ~40 tokens per file
-```markdown
-@include shared/command-templates.yml#Report_Output
-```
-
-### 5. Deliverables Sections
-**Before:** ~50 tokens per file
-```markdown
-Deliverables: Comprehensive analysis report, recommendations, and implementation guide.
-```
-
-**After:** ~25 tokens per file
-```markdown
-@include shared/constants.yml#Success_Messages
-```
-
-## Token Savings Analysis
-
-### Per-File Savings:
-- Legend sections: 140 tokens saved
-- Research requirements: 80 tokens saved  
-- Report output: 60 tokens saved
-- Deliverables: 25 tokens saved
-- **Total per file: ~305 tokens saved**
-
-### Total Project Savings:
-- **Files updated: 18**
-- **Total tokens saved: 5,490 tokens**
-- **Reduction percentage: ~35%**
-
-## Benefits Achieved
-
-### 1. Token Efficiency
-- 35% reduction in command file sizes
-- Faster loading and processing
-- Reduced context consumption
-
-### 2. Consistency
-- Standardized patterns across all commands
-- Uniform terminology and symbols
-- Consistent output formats
-
-### 3. Maintainability  
-- Single source of truth for common elements
-- Easy updates via shared templates
-- Reduced duplication
-
-### 4. Scalability
-- Template system ready for new commands
-- Easy addition of new shared patterns
-- Automated consistency checking possible
-
-## Template System Architecture
-
-### Core Files:
-- `shared/constants.yml` - Standard symbols, paths, messages
-- `shared/command-templates.yml` - Reusable command patterns
-- `shared/research-first.yml` - Research requirements
-- `shared/execution-lifecycle.yml` - Command execution patterns
-
-### Reference System:
-- `@include file#section` - Include content from templates
-- `@see file#section` - Reference for additional info
-- Cross-file consistency maintained automatically
-
-## Next Steps
-
-1. ✅ **Completed:** Migrate existing command files
-2. 🔄 **In Progress:** Monitor template usage effectiveness  
-3. 📋 **Planned:** Implement auto-validation of template references
-4. 📋 **Future:** Add more granular template patterns
-
-## Quality Metrics
-
-- **Migration Success Rate:** 95% (18/19 files)
-- **Token Reduction:** 35% average
-- **Consistency Score:** 100% (all files use standard patterns)
-- **Template Coverage:** 90% of common patterns templated
-
----
-*Migration completed successfully with significant efficiency gains*

package/SuperClaude/.claude/commands/shared/patterns.yml

@@ -1,155 +0,0 @@
-# Shared Patterns & Deliverables
-
-## Core Workflows
-```yaml
-Dev:
-  Full Stack: load→analyze→design→build→test→scan→deploy
-  Feature: analyze→build→test→improve→commit
-  Bug Fix: troubleshoot→fix→test→verify→commit
-  
-Quality:
-  Code Review: analyze→improve→scan→test
-  Perf: analyze→improve→test→measure
-  Security: scan→improve→validate→test
-
-Maintenance:
-  Cleanup: cleanup→analyze→improve→test
-  Update: migrate→test→validate→deploy
-  Refactor: analyze→design→improve→test
-```
-
-## Universal Flags
-```yaml
-Planning: --plan (show execution plan first)
-Thinking: --think (4K) | --think-hard (10K) | --ultrathink (32K)
-Docs: --uc (ultracompressed 70% reduction)
-MCP: --c7 --seq --magic --pup | --all-mcp | --no-mcp
-Execution: --dry-run | --watch | --interactive
-Quality: --tdd | --iterate | --threshold N%
-```
-
-## Error Types
-```yaml
-Syntax: Typos|brackets|quotes → Check syntax
-Runtime: Null|undefined|types → Validate inputs
-Logic: Conditions|loops|state → Trace flow
-Performance: N+1|memory|blocking → Profile
-Integration: API|auth|format → Check contracts
-```
-
-## MCP Usage
-```yaml
-Sequential: Complex analysis|Architecture|Debug
-Context7: Docs|Examples|Patterns
-Magic: UI components|Prototypes
-Puppeteer: E2E|Visual|Performance
-```
-
-## Research Patterns
-```yaml
-Library Usage: Detect import→C7 lookup→Cache pattern→Implement with citation
-Component Creation: Identify need→Search existing→Magic builder→Document source
-API Integration: Find docs→Check auth→Review limits→Implement→Note constraints
-Unknown Pattern: Sequential thinking→WebSearch→Multiple sources→Choose best
-
-Research Cache:
-  Session-based: Keep patterns until session end
-  Cite previous: "Using researched pattern from earlier"
-  Invalidate: On version change or conflicting info
-```
-
-## Deliverables
-
-### Code
-```yaml
-Commits: type: description | feat|fix|refactor|perf|test|docs | Why>What
-Docs: API(endpoints|params|examples) | Code(JSDoc|README) | User(guides|FAQs)
-Tests: Unit(functions|logic) | Integration(APIs|services) | E2E(flows|paths)
-```
-
-### Reports
-```yaml
-Performance: Baseline→Current→Improvement% | Time|memory|CPU|network
-Security: Vulnerabilities→Risk→Fixes | OWASP|deps|auth|data
-Quality: Coverage|complexity|duplication → Issues→Severity→Resolution
-```
-
-### Artifacts
-```yaml
-Configs: .env|settings|deployment | Scripts: build|test|deploy|migrate
-Schemas: Database|API|validation | Assets: Images|styles|components
-```
-
-## Accelerated Workflows
-```yaml
-Fast Chains:
-  Fix Known: /user:improve --quality [uses prior analyze]
-  Quick Deploy: /user:deploy [uses prior test+scan]
-  Smart Build: /user:build [skips unchanged modules]
-
-Auto Skip:
-  Unchanged files → Skip re-analysis
-  Passed tests → Skip re-test
-  Clean scan → Skip re-scan
-```
-
-## Clean Workflows
-```yaml
-Pre-Operations: cleanup→build→test→deploy
-Maintenance: analyze→cleanup→improve→test
-Development: cleanup→code→commit→push
-Release: cleanup→build→test→scan→deploy
-
-Clean-First Patterns:
-  Build: Remove old artifacts → Clean cache → Fresh build
-  Deploy: Clean previous version → Validate config → Deploy new
-  Test: Clean test outputs → Reset state → Run tests
-  Develop: Clean workspace → Remove debug code → Commit clean
-```
-
-## Command Integration Patterns
-```yaml
-Sequential Chains:
-  Full Development: load → analyze → design → build → test → deploy
-  Bug Investigation: troubleshoot --investigate → troubleshoot --fix → test
-  Quality Pipeline: analyze → improve --quality → scan --validate → test
-  
-Parallel Operations:
-  Multi-Stack: build --react & build --api & test --e2e
-  Quality Gates: scan --security & test --coverage & analyze --performance
-  
-Conditional Flows:
-  Safe Deploy: scan --validate && test --e2e && deploy --env prod
-  Rollback: deploy --rollback || troubleshoot --investigate
-  
-Context Sharing:
-  Analysis → Implementation: analyze → build (uses analysis context)
-  Design → Development: design → build (uses design patterns)
-  Investigation → Fix: troubleshoot --investigate → improve (uses findings)
-```
-
-## UltraCompressed Patterns
-```yaml
-Activation Patterns:
-  Manual: --uc flag | "ultracompressed" keyword
-  Auto: Context >70% | Token budget specified
-  Smart: Large docs → Suggest compression
-
-Documentation Patterns:
-  Start: Legend table | Only used symbols/abbrevs
-  Structure: Lists>prose | Tables>paragraphs | YAML>text
-  Content: Direct info | No fluff | Telegram-style
-  
-Example Transformations:
-  Normal: "Configure the authentication system by setting environment variables"
-  Compressed: "Auth cfg: set env vars"
-  
-  Normal: "This function processes user input and returns validation result"
-  Compressed: "fn: process usr input→validation"
-  
-Token Savings:
-  Headers: 60-80% reduction
-  Paragraphs: 70-75% reduction  
-  Lists: 50-60% reduction
-  Overall: ~70% average reduction
-```

package/SuperClaude/.claude/commands/shared/performance.yml

@@ -1,317 +0,0 @@
-# Performance Monitoring & Optimization System
-
-## Legend
-| Symbol | Meaning | | Abbrev | Meaning |
-|--------|---------|---|--------|---------|
-| ⚡ | fast/optimized | | perf | performance |
-| 📊 | metrics/data | | exec | execution |
-| ⏱ | timing/duration | | tok | token |
-| 🔄 | continuous | | opt | optimization |
-
-## Performance Metrics
-
-```yaml
-Command_Performance:
-  Timing_Metrics:
-    Start_Time: "Record command initiation timestamp"
-    End_Time: "Record command completion timestamp"  
-    Duration: "end_time - start_time"
-    Phases: "Breakdown by major operations (analysis, execution, reporting)"
-    
-  Token_Metrics:
-    Input_Tokens: "Tokens in user command + context"
-    Output_Tokens: "Tokens in response + tool calls"
-    MCP_Tokens: "Tokens consumed by MCP servers"
-    Efficiency_Ratio: "output_value / total_tokens"
-    Context_Size: "Total context size throughout operation"
-    
-  Operation_Metrics:
-    Tools_Used: "List of tools called (Read, Edit, Bash, etc)"
-    Files_Accessed: "Number of files read/written/analyzed"
-    MCP_Calls: "Which MCP servers used + frequency"
-    Error_Count: "Number of errors encountered"
-    Retry_Count: "Number of retry attempts needed"
-    
-  Success_Metrics:
-    Completion_Status: "success|partial|failure"
-    User_Satisfaction: "Interruptions, corrections, positive signals"
-    Quality_Score: "Estimated output quality (1-10)"
-    Objectives_Met: "Did operation achieve stated goals?"
-
-Op_Duration_Tracking:
-  Average_vs_Current: "Compare current execution to historical average"
-  Trend_Analysis: "Track performance changes over time"
-  Baseline_Comparison: "Measure against established benchmarks"
-  
-Token_Consumption_Analysis:
-  Usage_per_Operation: "Token consumption by command type"
-  Baseline_Comparison: "Compare to expected token usage"
-  Efficiency_Ratios: "Value delivered per token consumed"
-  Optimization_Opportunities: "Areas for token reduction"
-  
-Success_Rate_Monitoring:
-  Command_Completion_Rate: "Percentage of successful completions"
-  Error_Frequency: "Types and frequency of errors"
-  Retry_Patterns: "When and why retries are needed"
-  User_Intervention_Rate: "How often users need to correct/guide"
-```
-
-## Performance Baselines & Thresholds
-
-```yaml
-Command_Benchmarks:
-  Simple_Commands:
-    read_file: "<2s, <200 tokens"
-    edit_file: "<3s, <300 tokens"
-    analyze_single_file: "<5s, <500 tokens"
-    git_status: "<3s, <100 tokens"
-    
-  Medium_Commands:
-    build_component: "<30s, <2000 tokens"
-    test_execution: "<45s, <1500 tokens"
-    security_scan: "<60s, <3000 tokens"
-    analyze_multiple_files: "<45s, <2500 tokens"
-    
-  Complex_Commands:
-    full_codebase_analysis: "<120s, <5000 tokens"
-    architecture_design: "<180s, <8000 tokens"
-    comprehensive_security_audit: "<300s, <10000 tokens"
-    
-  MCP_Server_Performance:
-    Context7: "<5s response, 100-2000 tokens typical"
-    Sequential: "<30s analysis, 500-10000 tokens typical"
-    Magic: "<10s generation, 500-2000 tokens typical"
-    Puppeteer: "<15s operation, minimal tokens"
-
-Performance_Thresholds:
-  Time_Limits:
-    Yellow_Warning: ">30s operations → Consider alternatives"
-    Red_Alert: ">60s → Force timeout, explain delay, offer cancellation"
-    Critical: ">120s → Immediate intervention required"
-    
-  Token_Limits:
-    Moderate_Usage: ">2K tokens single op → Simplify approach"
-    High_Usage: ">5K session → Suggest /compact mode"
-    Critical_Usage: ">10K → Force optimization"
-    
-  Error_Patterns:
-    Concern_Level: "3+ retries same operation → Switch strategy"
-    Critical_Level: "Repeated failures → Escalate to manual approach"
-    System_Issue: "5+ consecutive failures → System health check"
-```
-
-## Adaptive Optimization Strategies
-
-```yaml
-Real_Time_Performance_Optimization:
-  Slow_Operations_Response:
-    Detection: "Operations exceeding 30s threshold"
-    Immediate_Actions:
-      - Switch to faster tools (rg vs grep, parallel processing)
-      - Reduce operation scope (specific files vs full scan)
-      - Enable parallel processing where possible
-      - Break large operations into smaller chunks
-      
-  High_Token_Usage_Response:
-    Detection: ">70% context or >5K tokens in single operation"
-    Immediate_Actions:
-      - Auto-suggest UltraCompressed mode (--uc)
-      - Cache repeated content and use references
-      - Summarize large outputs instead of full details
-      - Use shared templates instead of duplicating content
-      
-  Error_Pattern_Response:
-    Repeated_Failures:
-      Detection: "3+ failures of same operation type"
-      Actions:
-        - Switch to alternative tool/approach
-        - Adjust strategy based on error type
-        - Request user guidance for complex issues
-        - Document known issue for future prevention
-
-Workflow_Acceleration:
-  Pattern_Recognition:
-    Successful_Sequences: "Learn from effective command chains"
-    Efficient_Combinations: "Track optimal persona + command + flag combinations"
-    User_Preferences: "Adapt to user's working style over time"
-    
-  Predictive_Optimization:
-    Context_Preloading: "Anticipate likely-needed resources"
-    Smart_Caching: "Store and reuse expensive analysis results"
-    Skip_Redundant: "Avoid re-analysis of unchanged files"
-    Progressive_Refinement: "Start broad, narrow focus as needed"
-
-When_Slow_Strategies:
-  File_Operations: "Use faster tools (rg vs grep, fd vs find)"
-  Large_Codebases: "Focus on specific areas, progressive analysis"
-  Complex_Analysis: "Break into phases, provide interim results"
-  Network_Operations: "Parallel requests, intelligent caching"
-  
-When_High_Token_Usage:
-  Verbose_Output: "Switch to concise/compressed mode automatically"
-  Repeated_Content: "Use cross-references instead of duplication"
-  Large_Responses: "Summarize key points, provide detailed links"
-  Context_Management: "Smart context trimming, keep only essential"
-  
-When_Errors_Occur:
-  Tool_Failures: "Try alternative tools/approaches immediately"
-  Permission_Issues: "Provide specific fix guidance"
-  Missing_Dependencies: "Guide installation with exact commands"
-  Configuration_Problems: "Auto-detect and suggest corrections"
-```
-
-## Monitoring Implementation
-
-```yaml
-Data_Collection:
-  Lightweight_Tracking:
-    Performance_Impact: "<1% overhead on operations"
-    Background_Collection: "No user interruption during monitoring"
-    Privacy_Preserving: "Local storage only, no external transmission"
-    User_Configurable: "Can be disabled via settings"
-    
-  Storage_Format:
-    Location: ".claudedocs/metrics/performance-YYYY-MM-DD.jsonl"
-    Format: "JSON Lines (one record per command execution)"
-    Retention_Policy: "30 days rolling storage, monthly aggregation"
-    Size_Management: "10MB max per day, auto-rotation"
-    
-  Data_Structure:
-    timestamp: "ISO 8601 format"
-    command: "Full command with flags"
-    persona: "Active persona (if any)"
-    duration_ms: "Execution time in milliseconds"
-    tokens_input: "Input token count"
-    tokens_output: "Output token count"
-    tools_used: "Array of tool names"
-    mcp_servers: "Array of MCP servers used"
-    success: "Boolean completion status"
-    error_count: "Number of errors encountered"
-    user_corrections: "Number of user interruptions/corrections"
-    optimization_applied: "Any auto-optimizations used"
-```
-
-## Performance Reporting
-
-```yaml
-Real_Time_Feedback:
-  Transparency_Messages:
-    - "Operation taking longer than expected, switching to faster method"
-    - "Optimizing approach to reduce token usage"
-    - "Primary method failed, trying backup approach"
-    - "Completed efficiently using optimized strategy"
-    
-  Progress_Updates:
-    - Show percentage completion for long operations
-    - Indicate optimization strategies being applied
-    - Provide ETAs for remaining work
-    - Alert when alternative approaches are being tried
-
-Automated_Reports:
-  Daily_Summary:
-    Location: ".claudedocs/metrics/daily-summary-YYYY-MM-DD.md"
-    Content:
-      - Command execution statistics
-      - Token efficiency metrics
-      - Error frequency analysis
-      - Optimization wins and opportunities
-      - Performance trend indicators
-      
-  Weekly_Trends:
-    Location: ".claudedocs/metrics/weekly-trends-YYYY-WW.md"
-    Content:
-      - Performance trend analysis over 7 days
-      - Usage pattern identification
-      - Efficiency improvements over time
-      - Bottleneck identification and resolution
-      - User workflow optimization suggestions
-      
-  Monthly_Insights:
-    Location: ".claudedocs/metrics/monthly-insights-YYYY-MM.md"
-    Content:
-      - Long-term performance trends
-      - System optimization recommendations
-      - User productivity analysis
-      - Technology stack efficiency assessment
-
-Performance_Insights:
-  Bottleneck_Identification: "Which operations consume most resources"
-  Efficiency_Trends: "Performance improvement over time"
-  User_Patterns: "Most effective workflows and flag combinations"
-  Optimization_Recommendations: "Specific suggestions for improvement"
-  Success_Factor_Analysis: "What leads to successful outcomes"
-```
-
-## Integration Points
-
-```yaml
-Command_Wrapper_Integration:
-  Pre_Execution:
-    - Record start timestamp and context state
-    - Capture input context size and complexity
-    - Note active persona, flags, and user preferences
-    - Check for known performance issues with operation
-    
-  During_Execution:
-    - Track tool usage and performance
-    - Monitor MCP server response times
-    - Count errors, retries, and optimization attempts
-    - Provide real-time feedback on long operations
-    
-  Post_Execution:
-    - Record completion time and final status
-    - Calculate total token consumption
-    - Assess success metrics and quality
-    - Store performance record for future analysis
-    - Generate optimization recommendations
-
-Auto_Optimization_Features:
-  Context_Size_Management:
-    - Auto-suggest /compact when context >70%
-    - Enable --uc mode for responses >2K tokens
-    - Cache expensive analysis results
-    - Trim redundant context intelligently
-    
-  Tool_Selection_Optimization:
-    - Prefer faster tools for routine operations
-    - Use parallel execution when safe and beneficial
-    - Skip redundant file reads and analyses
-    - Choose optimal MCP server for each task
-    
-  User_Experience_Enhancement:
-    - Proactive performance feedback during operations
-    - Intelligent optimization suggestions
-    - Alternative approach recommendations
-    - Learning from user preferences and corrections
-```
-
-## Configuration & Customization
-
-```yaml
-Performance_Settings:
-  Monitoring_Level:
-    minimal: "Basic timing and success tracking"
-    standard: "Full performance monitoring (default)"
-    detailed: "Comprehensive analysis with detailed breakdowns"
-    disabled: "No performance tracking"
-    
-  Optimization_Aggressiveness:
-    conservative: "Optimize only when significant benefit"
-    balanced: "Reasonable optimization vs consistency trade-offs"
-    aggressive: "Maximum optimization, accept some workflow changes"
-    
-  Alert_Preferences:
-    real_time: "Show optimization messages during operations"
-    summary: "Daily/weekly performance summaries only"
-    critical_only: "Alert only on significant issues"
-    silent: "No performance notifications"
-
-Auto_Optimization_Controls:
-  Enable_Auto_UC: "Automatically enable UltraCompressed mode"
-  Enable_Tool_Switching: "Allow automatic tool substitution"
-  Enable_Scope_Reduction: "Automatically reduce operation scope when slow"
-  Enable_Parallel_Processing: "Use parallel execution when beneficial"
-```
-
----
-*Performance System v1.0 - Comprehensive monitoring, analysis, and optimization for SuperClaude*

package/SuperClaude/.claude/commands/shared/planning-mode.yml

@@ -1,51 +0,0 @@
-# Planning Mode Config
-
-## Flag-Based Planning Control
-```yaml
-Planning_Flags:
-  --plan: "Force planning mode for any command"
-  --skip-plan: "Skip planning mode (execute immediately)"
-  default: "Execute immediately unless --plan flag is present"
-  
-Risk_Assessment:
-  description: "Users control planning through explicit flags"
-  recommendation: "Use --plan for risky ops that modify system state"
-```
-
-## Risk Assessment Patterns
-```yaml
-Risk Triggers:
-  Prod: deploy --env prod | migrate --rollback false
-  Data Loss: cleanup --all | migrate w/o --dry-run
-  System Wide: spawn --task | improve --iterate
-  Arch: design --api | troubleshoot --prod
-  
-Checkpoint Required:
-  - Before: deploy, migrate, cleanup --all
-  - During: Long-running improve --iterate
-  - After: Any operation with warnings
-
-Safety Overrides:
-  --no-plan: Skip planning only for SKIP_PLANNING commands
-  --plan: Force planning for any command
-  --dry-run: Safe preview mode, skip planning
-```
-
-## Planning Workflow
-```yaml
-Pre-Execution Check:
-  1. Parse command name and flags
-  2. Check REQUIRED_PLANNING list
-  3. Check special conditions (build --init)
-  4. If planning required → exit_plan_mode → await approval
-  5. Create checkpoint if risky
-  6. Proceed with execution
-
-Planning Content:
-  Required: Command intent, affected resources, risks, rollback plan
-  Optional: Time estimate, dependencies, validation steps
-  Format: Structured plan using exit_plan_mode tool
-```
-
----
-*Planning mode configuration for systematic risk management*