How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

codemap-optimization - Prompt

Name: codemap-optimization
Author: HeadySystems

codemap-optimization

by HeadySystems(0) 0 installs

Prompt file imported from HeadySystems/Heady-Testing (.windsurf/workflows/codemap-optimization.md). Copyright stays with the author.

description: Codemap Optimization - AI Node Integration for Enhanced Performance

Codemap Optimization Workflow

Overview

Integrates Heady Academy's AI nodes (JULES, OBSERVER, BUILDER, ATLAS) into the HCAutoBuild system for enhanced performance optimization and intelligent automation.

Node Registry

🧠 JULES - The Hyper-Surgeon

Role: Code optimization and analysis
Tool: goose (Python-based optimizer)
Trigger: optimization
Capabilities:
- Unused import detection
- Code quality analysis
- Performance optimization suggestions
- Security vulnerability scanning

👁️ OBSERVER - The Natural Observer

Role: Enhanced monitoring and performance analysis
Tool: observer_daemon
Trigger: monitor
Capabilities:
- Real-time workspace analysis
- File system monitoring
- Performance metrics collection
- Optimization opportunity detection

🔨 BUILDER - The Constructor

Role: Project optimization and cleanup
Tool: hydrator
Trigger: new_project
Capabilities:
- Build optimization
- Dependency management
- Resource cleanup
- Project structure optimization

📚 ATLAS - The Auto-Archivist

Role: Documentation generation and maintenance
Tool: auto_doc
Trigger: documentation
Capabilities:
- Automatic documentation generation
- API documentation extraction
- Code analysis and documentation
- Knowledge base creation

Workflow Phases

Phase 1: Node Activation

# Activate specific nodes
.\hcautobuild_optimizer.ps1 -jules
.\hcautobuild_optimizer.ps1 -observer
.\hcautobuild_optimizer.ps1 -builder
.\hcautobuild_optimizer.ps1 -atlas

# Activate all nodes
.\hcautobuild_optimizer.ps1 -optimize

Phase 2: Analysis & Optimization

JULES Analysis: Code quality and optimization
OBSERVER Monitoring: Performance and resource analysis
BUILDER Optimization: Project structure and dependencies
ATLAS Documentation: Automatic documentation generation

Phase 3: Enhanced Scoring

Base functionality score: 100 points
Codemap enhancements: up to 40 points
- Code quality: up to 10 points
- Documentation: up to 10 points
- Performance: up to 10 points
- Security: up to 10 points

Phase 4: Intelligent Checkpointing

Enhanced checkpoints include codemap analysis
Automatic optimization suggestions
Performance metrics tracking
Documentation status reporting

Integration with HCAutoBuild

Enhanced Commands

# Run enhanced HCAutoBuild with codemap optimization
.\hcautobuild_enhanced.ps1 -optimize

# Run codemap optimization only
.\hcautobuild_optimizer.ps1 -optimize

# Enhanced monitoring with codemap integration
.\hcautobuild_enhanced.ps1 -monitor

Configuration

{
  "codemap_nodes": ["JULES", "OBSERVER", "BUILDER", "ATLAS"],
  "optimization_interval": 3600,
  "auto_optimize": true,
  "node_timeout": 300,
  "parallel_execution": true
}

Optimization Reports

JULES Reports

Location: .heady/logs/optimization_reports/
Format: Markdown with code suggestions
Content: Unused imports, long lines, TODOs, magic numbers

OBSERVER Reports

Location: .heady/observer_reports/
Format: JSON with detailed metrics
Content: File counts, sizes, language distribution, activity

BUILDER Reports

Location: .heady/builder_reports/
Format: JSON with optimization suggestions
Content: Build optimizations, cleanup opportunities

ATLAS Reports

Location: .heady/atlas_reports/
Format: JSON with documentation analysis
Content: API docs, dependencies, existing documentation

Performance Benefits

Code Quality Improvements

Automatic detection of code issues
Performance optimization suggestions
Security vulnerability identification
Best practices enforcement

Enhanced Monitoring

Real-time performance metrics
Resource usage optimization
File system efficiency analysis
Automated cleanup suggestions

Documentation Automation

Automatic API documentation
Code structure analysis
Knowledge base generation
Documentation maintenance

Intelligent Checkpointing

Enhanced functionality scoring
Optimization-aware checkpoints
Performance tracking
Automated improvement suggestions

Usage Examples

Basic Optimization

# Run full codemap optimization
.\hcautobuild_optimizer.ps1 -optimize

# Run specific node
.\hcautobuild_optimizer.ps1 -jules -workspace "C:\Project"

Enhanced HCAutoBuild

# Run HCAutoBuild with optimization
.\hcautobuild_enhanced.ps1 -optimize

# Enhanced monitoring
.\hcautobuild_enhanced.ps1 -monitor

# Force enhanced checkpoint
.\hcautobuild_enhanced.ps1 -checkpoint -optimize

Analysis Mode

# Run analysis nodes only
.\hcautobuild_optimizer.ps1 -analyze

# Specific analysis
.\hcautobuild_optimizer.ps1 -observer -atlas

Troubleshooting

Common Issues

Python not available: JULES requires Python for optimization
Missing scripts: Ensure HeadyAcademy/Tools/ directory exists
Permission issues: Check write permissions for .heady directory
Node timeout: Increase NodeTimeout in configuration

Debug Mode

# Run with debug output
.\hcautobuild_optimizer.ps1 -optimize -verbose
.\hcautobuild_enhanced.ps1 -optimize -debug

Log Files

Main log: .heady/logs/hcautobuild_optimizer.log
Enhanced log: .heady/logs/enhanced/hcautobuild_enhanced.log
Node logs: .heady/logs/[node_name].log

Best Practices

Optimization Frequency

Run JULES optimization after code changes
Use OBSERVER monitoring for long-running projects
Run BUILDER optimization before deployments
Use ATLAS documentation for API changes

Integration Strategy

Start with basic HCAutoBuild functionality
Gradually integrate codemap nodes
Monitor performance improvements
Adjust configuration based on results

Performance Considerations

Codemap optimization increases analysis time
Parallel execution improves performance
Caching results reduces redundant work
Monitor resource usage during optimization

Future Enhancements

Additional Nodes

MURPHY: Security auditing integration
SOPHIA: Machine learning optimization
CIPHER: Code obfuscation and protection
SCOUT: GitHub integration and analysis

Advanced Features

Predictive optimization
Machine learning integration
Advanced performance profiling
Automated code refactoring

Integration Opportunities

CI/CD pipeline integration
IDE plugin development
Real-time code analysis
Cloud-based optimization services

Configuration Reference

Node Configuration

nodes:
  JULES:
    enabled: true
    timeout: 300
    parallel: true
    priority: high
  OBSERVER:
    enabled: true
    interval: 300
    metrics: ["performance", "size", "activity"]
  BUILDER:
    enabled: true
    cleanup: true
    optimize_dependencies: true
  ATLAS:
    enabled: true
    auto_generate: true
    format: ["markdown", "json"]

Optimization Rules

optimization_rules:
  code_quality:
    max_line_length: 120
    check_unused_imports: true
    detect_magic_numbers: true
  performance:
    max_file_size: 10MB
    check_memory_usage: true
    analyze_dependencies: true
  documentation:
    require_api_docs: true
    generate_readme: true
    update_changelog: true

Codemap Optimization transforms HCAutoBuild into an intelligent, AI-powered system that continuously improves code quality, performance, and maintainability.

Install codemap-optimization and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

--- description: Codemap Optimization - AI Node Integration for Enhanced Performance --- # Codemap Optimization Workflow ## Overview Integrates Heady Academy's AI nodes (JULES, OBSERVER, BUILDER, ATLAS) into the HCAutoBuild system for enhanced performance optimization and intelligent automation. ## Node Registry ### 🧠 JULES - The Hyper-Surgeon - **Role**: Code optimization and analysis - **Tool**: goose (Python-based optimizer) - **Trigger**: optimization - **Capabilities**: - Unused import detection - Code quality analysis - Performance optimization suggestions - Security vulnerability scanning ### 👁️ OBSERVER - The Natural Observer - **Role**: Enhanced monitoring and performance analysis - **Tool**: observer_daemon - **Trigger**: monitor - **Capabilities**: - Real-time workspace analysis - File system monitoring - Performance metrics collection - Optimization opportunity detection ### 🔨 BUILDER - The Constructor - **Role**: Project optimization and cleanup - **Tool**: hydrator - **Trigger**: new_project - **Capabilities**: - Build optimization - Dependency management - Resource cleanup - Project structure optimization ### 📚 ATLAS - The Auto-Archivist - **Role**: Documentation generation and maintenance - **Tool**: auto_doc - **Trigger**: documentation - **Capabilities**: - Automatic documentation generation - API documentation extraction - Code analysis and documentation - Knowledge base creation ## Workflow Phases ### Phase 1: Node Activation ```bash # Activate specific nodes .\hcautobuild_optimizer.ps1 -jules .\hcautobuild_optimizer.ps1 -observer .\hcautobuild_optimizer.ps1 -builder .\hcautobuild_optimizer.ps1 -atlas # Activate all nodes .\hcautobuild_optimizer.ps1 -optimize ``` ### Phase 2: Analysis & Optimization 1. **JULES Analysis**: Code quality and optimization 2. **OBSERVER Monitoring**: Performance and resource analysis 3. **BUILDER Optimization**: Project structure and dependencies 4. **ATLAS Documentation**: Automatic documentation generation ### Phase 3: Enhanced Scoring - Base functionality score: 100 points - Codemap enhancements: up to 40 points - Code quality: up to 10 points - Documentation: up to 10 points - Performance: up to 10 points - Security: up to 10 points ### Phase 4: Intelligent Checkpointing - Enhanced checkpoints include codemap analysis - Automatic optimization suggestions - Performance metrics tracking - Documentation status reporting ## Integration with HCAutoBuild ### Enhanced Commands ```bash # Run enhanced HCAutoBuild with codemap optimization .\hcautobuild_enhanced.ps1 -optimize # Run codemap optimization only .\hcautobuild_optimizer.ps1 -optimize # Enhanced monitoring with codemap integration .\hcautobuild_enhanced.ps1 -monitor ``` ### Configuration ```json { "codemap_nodes": ["JULES", "OBSERVER", "BUILDER", "ATLAS"], "optimization_interval": 3600, "auto_optimize": true, "node_timeout": 300, "parallel_execution": true } ``` ## Optimization Reports ### JULES Reports - Location: `.heady/logs/optimization_reports/` - Format: Markdown with code suggestions - Content: Unused imports, long lines, TODOs, magic numbers ### OBSERVER Reports - Location: `.heady/observer_reports/` - Format: JSON with detailed metrics - Content: File counts, sizes, language distribution, activity ### BUILDER Reports - Location: `.heady/builder_reports/` - Format: JSON with optimization suggestions - Content: Build optimizations, cleanup opportunities ### ATLAS Reports - Location: `.heady/atlas_reports/` - Format: JSON with documentation analysis - Content: API docs, dependencies, existing documentation ## Performance Benefits ### Code Quality Improvements - Automatic detection of code issues - Performance optimization suggestions - Security vulnerability identification - Best practices enforcement ### Enhanced Monitoring - Real-time performance metrics - Resource usage optimization - File system efficiency analysis - Automated cleanup suggestions ### Documentation Automation - Automatic API documentation - Code structure analysis - Knowledge base generation - Documentation maintenance ### Intelligent Checkpointing - Enhanced functionality scoring - Optimization-aware checkpoints - Performance tracking - Automated improvement suggestions ## Usage Examples ### Basic Optimization ```bash # Run full codemap optimization .\hcautobuild_optimizer.ps1 -optimize # Run specific node .\hcautobuild_optimizer.ps1 -jules -workspace "C:\Project" ``` ### Enhanced HCAutoBuild ```bash # Run HCAutoBuild with optimization .\hcautobuild_enhanced.ps1 -optimize # Enhanced monitoring .\hcautobuild_enhanced.ps1 -monitor # Force enhanced checkpoint .\hcautobuild_enhanced.ps1 -checkpoint -optimize ``` ### Analysis Mode ```bash # Run analysis nodes only .\hcautobuild_optimizer.ps1 -analyze # Specific analysis .\hcautobuild_optimizer.ps1 -observer -atlas ``` ## Troubleshooting ### Common Issues 1. **Python not available**: JULES requires Python for optimization 2. **Missing scripts**: Ensure HeadyAcademy/Tools/ directory exists 3. **Permission issues**: Check write permissions for .heady directory 4. **Node timeout**: Increase NodeTimeout in configuration ### Debug Mode ```bash # Run with debug output .\hcautobuild_optimizer.ps1 -optimize -verbose .\hcautobuild_enhanced.ps1 -optimize -debug ``` ### Log Files - Main log: `.heady/logs/hcautobuild_optimizer.log` - Enhanced log: `.heady/logs/enhanced/hcautobuild_enhanced.log` - Node logs: `.heady/logs/[node_name].log` ## Best Practices ### Optimization Frequency - Run JULES optimization after code changes - Use OBSERVER monitoring for long-running projects - Run BUILDER optimization before deployments - Use ATLAS documentation for API changes ### Integration Strategy 1. Start with basic HCAutoBuild functionality 2. Gradually integrate codemap nodes 3. Monitor performance improvements 4. Adjust configuration based on results ### Performance Considerations - Codemap optimization increases analysis time - Parallel execution improves performance - Caching results reduces redundant work - Monitor resource usage during optimization ## Future Enhancements ### Additional Nodes - **MURPHY**: Security auditing integration - **SOPHIA**: Machine learning optimization - **CIPHER**: Code obfuscation and protection - **SCOUT**: GitHub integration and analysis ### Advanced Features - Predictive optimization - Machine learning integration - Advanced performance profiling - Automated code refactoring ### Integration Opportunities - CI/CD pipeline integration - IDE plugin development - Real-time code analysis - Cloud-based optimization services ## Configuration Reference ### Node Configuration ```yaml nodes: JULES: enabled: true timeout: 300 parallel: true priority: high OBSERVER: enabled: true interval: 300 metrics: ["performance", "size", "activity"] BUILDER: enabled: true cleanup: true optimize_dependencies: true ATLAS: enabled: true auto_generate: true format: ["markdown", "json"] ``` ### Optimization Rules ```yaml optimization_rules: code_quality: max_line_length: 120 check_unused_imports: true detect_magic_numbers: true performance: max_file_size: 10MB check_memory_usage: true analyze_dependencies: true documentation: require_api_docs: true generate_readme: true update_changelog: true ``` --- **Codemap Optimization transforms HCAutoBuild into an intelligent, AI-powered system that continuously improves code quality, performance, and maintainability.**

{ "prompt": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n---\ndescription: Codemap Optimization - AI Node Integration for Enhanced Performance\n---\n\n# Codemap Optimization Workflow\n\n## Overview\nIntegrates Heady Academy's AI nodes (JULES, OBSERVER, BUILDER, ATLAS) into the HCAutoBuild system for enhanced performance optimization and intelligent automation.\n\n## Node Registry\n\n### 🧠 JULES - The Hyper-Surgeon\n- **Role**: Code optimization and analysis\n- **Tool**: goose (Python-based optimizer)\n- **Trigger**: optimization\n- **Capabilities**:\n - Unused import detection\n - Code quality analysis\n - Performance optimization suggestions\n - Security vulnerability scanning\n\n### 👁️ OBSERVER - The Natural Observer\n- **Role**: Enhanced monitoring and performance analysis\n- **Tool**: observer_daemon\n- **Trigger**: monitor\n- **Capabilities**:\n - Real-time workspace analysis\n - File system monitoring\n - Performance metrics collection\n - Optimization opportunity detection\n\n### 🔨 BUILDER - The Constructor\n- **Role**: Project optimization and cleanup\n- **Tool**: hydrator\n- **Trigger**: new_project\n- **Capabilities**:\n - Build optimization\n - Dependency management\n - Resource cleanup\n - Project structure optimization\n\n### 📚 ATLAS - The Auto-Archivist\n- **Role**: Documentation generation and maintenance\n- **Tool**: auto_doc\n- **Trigger**: documentation\n- **Capabilities**:\n - Automatic documentation generation\n - API documentation extraction\n - Code analysis and documentation\n - Knowledge base creation\n\n## Workflow Phases\n\n### Phase 1: Node Activation\n```bash\n# Activate specific nodes\n.\\hcautobuild_optimizer.ps1 -jules\n.\\hcautobuild_optimizer.ps1 -observer\n.\\hcautobuild_optimizer.ps1 -builder\n.\\hcautobuild_optimizer.ps1 -atlas\n\n# Activate all nodes\n.\\hcautobuild_optimizer.ps1 -optimize\n```\n\n### Phase 2: Analysis & Optimization\n1. **JULES Analysis**: Code quality and optimization\n2. **OBSERVER Monitoring**: Performance and resource analysis\n3. **BUILDER Optimization**: Project structure and dependencies\n4. **ATLAS Documentation**: Automatic documentation generation\n\n### Phase 3: Enhanced Scoring\n- Base functionality score: 100 points\n- Codemap enhancements: up to 40 points\n - Code quality: up to 10 points\n - Documentation: up to 10 points\n - Performance: up to 10 points\n - Security: up to 10 points\n\n### Phase 4: Intelligent Checkpointing\n- Enhanced checkpoints include codemap analysis\n- Automatic optimization suggestions\n- Performance metrics tracking\n- Documentation status reporting\n\n## Integration with HCAutoBuild\n\n### Enhanced Commands\n```bash\n# Run enhanced HCAutoBuild with codemap optimization\n.\\hcautobuild_enhanced.ps1 -optimize\n\n# Run codemap optimization only\n.\\hcautobuild_optimizer.ps1 -optimize\n\n# Enhanced monitoring with codemap integration\n.\\hcautobuild_enhanced.ps1 -monitor\n```\n\n### Configuration\n```json\n{\n \"codemap_nodes\": [\"JULES\", \"OBSERVER\", \"BUILDER\", \"ATLAS\"],\n \"optimization_interval\": 3600,\n \"auto_optimize\": true,\n \"node_timeout\": 300,\n \"parallel_execution\": true\n}\n```\n\n## Optimization Reports\n\n### JULES Reports\n- Location: `.heady/logs/optimization_reports/`\n- Format: Markdown with code suggestions\n- Content: Unused imports, long lines, TODOs, magic numbers\n\n### OBSERVER Reports\n- Location: `.heady/observer_reports/`\n- Format: JSON with detailed metrics\n- Content: File counts, sizes, language distribution, activity\n\n### BUILDER Reports\n- Location: `.heady/builder_reports/`\n- Format: JSON with optimization suggestions\n- Content: Build optimizations, cleanup opportunities\n\n### ATLAS Reports\n- Location: `.heady/atlas_reports/`\n- Format: JSON with documentation analysis\n- Content: API docs, dependencies, existing documentation\n\n## Performance Benefits\n\n### Code Quality Improvements\n- Automatic detection of code issues\n- Performance optimization suggestions\n- Security vulnerability identification\n- Best practices enforcement\n\n### Enhanced Monitoring\n- Real-time performance metrics\n- Resource usage optimization\n- File system efficiency analysis\n- Automated cleanup suggestions\n\n### Documentation Automation\n- Automatic API documentation\n- Code structure analysis\n- Knowledge base generation\n- Documentation maintenance\n\n### Intelligent Checkpointing\n- Enhanced functionality scoring\n- Optimization-aware checkpoints\n- Performance tracking\n- Automated improvement suggestions\n\n## Usage Examples\n\n### Basic Optimization\n```bash\n# Run full codemap optimization\n.\\hcautobuild_optimizer.ps1 -optimize\n\n# Run specific node\n.\\hcautobuild_optimizer.ps1 -jules -workspace \"C:\\Project\"\n```\n\n### Enhanced HCAutoBuild\n```bash\n# Run HCAutoBuild with optimization\n.\\hcautobuild_enhanced.ps1 -optimize\n\n# Enhanced monitoring\n.\\hcautobuild_enhanced.ps1 -monitor\n\n# Force enhanced checkpoint\n.\\hcautobuild_enhanced.ps1 -checkpoint -optimize\n```\n\n### Analysis Mode\n```bash\n# Run analysis nodes only\n.\\hcautobuild_optimizer.ps1 -analyze\n\n# Specific analysis\n.\\hcautobuild_optimizer.ps1 -observer -atlas\n```\n\n## Troubleshooting\n\n### Common Issues\n1. **Python not available**: JULES requires Python for optimization\n2. **Missing scripts**: Ensure HeadyAcademy/Tools/ directory exists\n3. **Permission issues**: Check write permissions for .heady directory\n4. **Node timeout**: Increase NodeTimeout in configuration\n\n### Debug Mode\n```bash\n# Run with debug output\n.\\hcautobuild_optimizer.ps1 -optimize -verbose\n.\\hcautobuild_enhanced.ps1 -optimize -debug\n```\n\n### Log Files\n- Main log: `.heady/logs/hcautobuild_optimizer.log`\n- Enhanced log: `.heady/logs/enhanced/hcautobuild_enhanced.log`\n- Node logs: `.heady/logs/[node_name].log`\n\n## Best Practices\n\n### Optimization Frequency\n- Run JULES optimization after code changes\n- Use OBSERVER monitoring for long-running projects\n- Run BUILDER optimization before deployments\n- Use ATLAS documentation for API changes\n\n### Integration Strategy\n1. Start with basic HCAutoBuild functionality\n2. Gradually integrate codemap nodes\n3. Monitor performance improvements\n4. Adjust configuration based on results\n\n### Performance Considerations\n- Codemap optimization increases analysis time\n- Parallel execution improves performance\n- Caching results reduces redundant work\n- Monitor resource usage during optimization\n\n## Future Enhancements\n\n### Additional Nodes\n- **MURPHY**: Security auditing integration\n- **SOPHIA**: Machine learning optimization\n- **CIPHER**: Code obfuscation and protection\n- **SCOUT**: GitHub integration and analysis\n\n### Advanced Features\n- Predictive optimization\n- Machine learning integration\n- Advanced performance profiling\n- Automated code refactoring\n\n### Integration Opportunities\n- CI/CD pipeline integration\n- IDE plugin development\n- Real-time code analysis\n- Cloud-based optimization services\n\n## Configuration Reference\n\n### Node Configuration\n```yaml\nnodes:\n JULES:\n enabled: true\n timeout: 300\n parallel: true\n priority: high\n OBSERVER:\n enabled: true\n interval: 300\n metrics: [\"performance\", \"size\", \"activity\"]\n BUILDER:\n enabled: true\n cleanup: true\n optimize_dependencies: true\n ATLAS:\n enabled: true\n auto_generate: true\n format: [\"markdown\", \"json\"]\n```\n\n### Optimization Rules\n```yaml\noptimization_rules:\n code_quality:\n max_line_length: 120\n check_unused_imports: true\n detect_magic_numbers: true\n performance:\n max_file_size: 10MB\n check_memory_usage: true\n analyze_dependencies: true\n documentation:\n require_api_docs: true\n generate_readme: true\n update_changelog: true\n```\n\n---\n\n**Codemap Optimization transforms HCAutoBuild into an intelligent, AI-powered system that continuously improves code quality, performance, and maintainability.**", "variables": [], "notes": "              ", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/HeadySystems/Heady-Testing", "path": ".windsurf/workflows/codemap-optimization.md", "ref": "688dd9a613128f74bfb8687c36e5349ee1e2d942", "url": "https://github.com/HeadySystems/Heady-Testing/blob/688dd9a613128f74bfb8687c36e5349ee1e2d942/.windsurf/workflows/codemap-optimization.md", "key": "HeadySystems/Heady-Testing/.windsurf/workflows/codemap-optimization.md" } } }