home-lab/packages/.roo/rules/roo_rules.md
Geir Okkenhaug Jerstad cc735b3497 feat: Complete migration to GNU Guile Scheme with MCP integration
Major project milestone: Successfully migrated home lab management tool from Bash to GNU Guile Scheme

## Completed Components 
- **Project Foundation**: Complete directory structure (lab/, mcp/, utils/)
- **Working CLI Tool**: Functional home-lab-tool.scm with command parsing
- **Development Environment**: NixOS flake.nix with Guile, JSON, SSH, WebSocket libraries
- **Core Utilities**: Logging, configuration, SSH utilities with error handling
- **Module Architecture**: Comprehensive lab modules and MCP server foundation
- **TaskMaster Integration**: 25-task roadmap with project management
- **Testing & Validation**: Successfully tested in nix develop environment

## Implementation Highlights
- Functional programming patterns with immutable data structures
- Proper error handling and recovery mechanisms
- Clean module separation with well-defined interfaces
- Working CLI commands: help, status, deploy (with parsing)
- Modular Guile architecture ready for expansion

## Project Structure
- home-lab-tool.scm: Main CLI entry point (working)
- utils/: logging.scm, config.scm, ssh.scm (ssh needs syntax fixes)
- lab/: core.scm, machines.scm, deployment.scm, monitoring.scm
- mcp/: server.scm foundation for VS Code integration
- flake.nix: Working development environment

## Next Steps
1. Fix SSH utilities syntax errors for real connectivity
2. Implement actual infrastructure status checking
3. Complete MCP server JSON-RPC protocol
4. Develop VS Code extension with MCP client

This represents a complete rewrite maintaining compatibility while adding:
- Better error handling and maintainability
- MCP server for AI/VS Code integration
- Modular architecture for extensibility
- Comprehensive project management with TaskMaster

The Bash-to-Guile migration provides a solid foundation for advanced
home lab management with modern tooling and AI integration.
2025-06-15 22:17:47 +02:00

1.5 KiB

description globs alwaysApply
Guidelines for creating and maintaining Roo Code rules to ensure consistency and effectiveness. .roo/rules/*.md true
  • Required Rule Structure:

    ---
    description: Clear, one-line description of what the rule enforces
    globs: path/to/files/*.ext, other/path/**/*
    alwaysApply: boolean
    ---
    
    - **Main Points in Bold**
      - Sub-points with details
      - Examples and explanations
    
  • File References:

  • Code Examples:

    • Use language-specific code blocks
    // ✅ DO: Show good examples
    const goodExample = true;
    
    // ❌ DON'T: Show anti-patterns
    const badExample = false;
    
  • Rule Content Guidelines:

    • Start with high-level overview
    • Include specific, actionable requirements
    • Show examples of correct implementation
    • Reference existing code when possible
    • Keep rules DRY by referencing other rules
  • Rule Maintenance:

    • Update rules when new patterns emerge
    • Add examples from actual codebase
    • Remove outdated patterns
    • Cross-reference related rules
  • Best Practices:

    • Use bullet points for clarity
    • Keep descriptions concise
    • Include both DO and DON'T examples
    • Reference actual code over theoretical examples
    • Use consistent formatting across rules