Skip to content

QUICK_REFERENCE.md

Latest commit

 

History

History
251 lines (195 loc) · 7.5 KB

QUICK_REFERENCE.md

File metadata and controls

251 lines (195 loc) · 7.5 KB

Quick Reference - RooCode Network Engineering & AWS Cloud System

Version: 1.0 | Date: October 2025

📥 Import Files

Use Case File Size Modes
Network Engineering only network-engineering-complete.yaml 300KB 3 orch + 11 specialists
AWS Cloud only aws-complete.yaml 290KB 1 orch + 9 specialists
Both (Full-stack) Import both files 590KB 4 orch + 20 specialists

How to import: RooCode → Settings → Custom Modes → Import → Select file

🌐 Network Engineering System (Phases 1-4)

3 Orchestrators

  • Network Orchestrator - Routing, switching, connectivity
  • VoIP Orchestrator - AWS Connect, CUCM, SIP, call quality
  • Security Orchestrator - ISE, firewalls, NAC

11 Specialists

Troubleshooting (5):

  • Network Troubleshooter - OSPF, BGP, EIGRP, VLAN, STP
  • VoIP Troubleshooter - Call quality, registration, routing
  • ISE Troubleshooter - 802.1X, MAB, policy evaluation
  • Packet Analyzer - Wireshark/tshark command generation
  • Authentication Analyzer - RADIUS flow reconstruction

Architects (3):

  • Network Architect - Routing/switching design, HA, capacity planning
  • VoIP Architect - CUCM clusters, dial plans, QoS design
  • Security Architect - ISE NAC, 802.1X, segmentation design

Implementation (3):

  • Network Engineer - Router/switch CLI configs
  • VoIP Engineer - CUCM/gateway configurations
  • Security Engineer - ISE policies, 802.1X switch configs

☁️ AWS Cloud System (Phase 5)

1 Orchestrator

  • AWS Cloud Orchestrator - Lambda, DynamoDB, AI services, DevOps

9 Specialists

Troubleshooting (4):

  • Lambda Troubleshooter - Timeouts, memory, VPC, permissions, cold starts
  • Database Troubleshooter - DynamoDB throttling, slow queries, capacity
  • Integration Troubleshooter - API Gateway, Step Functions, EventBridge, SNS/SQS
  • AI Services Troubleshooter - Bedrock, Lex, prompts, quotas

Architects (3):

  • Serverless Architect - REST APIs, event-driven, workflows
  • Contact Center Architect - AWS Connect backends, omnichannel
  • AI Solutions Architect - RAG, conversational AI, document processing

DevOps (2):

  • Cloud Engineer - IaC (CloudFormation/CDK), CI/CD, monitoring
  • Cost Optimizer - Cost analysis, right-sizing, optimization

🚀 Common Workflows

Network Engineering

Troubleshooting:

User: "OSPF neighbors not forming between R1 and R2"
→ Network Orchestrator
  → Network Troubleshooter (diagnose)
  → Network Engineer (config fix)
  → Result: Complete solution with validation

Architecture:

User: "Design HA network for 3-site campus"
→ Network Orchestrator
  → Network Architect (design OSPF/HSRP architecture)
  → Network Engineer (provide configs)
  → Result: Complete design + configs + validation

AWS Cloud

Troubleshooting:

User: "Lambda timing out when calling DynamoDB"
→ AWS Cloud Orchestrator
  → Lambda Troubleshooter (VPC connectivity issue)
  → Cloud Engineer (VPC endpoint setup)
  → Result: CloudFormation template + validation

Architecture:

User: "Design serverless API for user management"
→ AWS Cloud Orchestrator
  → Serverless Architect (API Gateway + Lambda + DynamoDB)
  → Cloud Engineer (CloudFormation + CI/CD)
  → Result: Complete architecture + deployment pipeline

AI Solutions:

User: "Build RAG system for knowledge base"
→ AWS Cloud Orchestrator
  → AI Solutions Architect (RAG design)
  → Cloud Engineer (implementation)
  → Result: Complete RAG pipeline with cost optimization

🎯 When to Use Which Orchestrator

Scenario Use This Orchestrator
OSPF/BGP/EIGRP issues Network Orchestrator
VLAN/STP/trunking issues Network Orchestrator
AWS Connect call quality VoIP Orchestrator
CUCM registration issues VoIP Orchestrator
ISE 802.1X authentication Security Orchestrator
Firewall rules/NAC Security Orchestrator
Lambda errors/timeouts AWS Cloud Orchestrator
DynamoDB throttling AWS Cloud Orchestrator
API Gateway errors AWS Cloud Orchestrator
Bedrock/Lex issues AWS Cloud Orchestrator
Serverless architecture design AWS Cloud Orchestrator
CI/CD pipeline setup AWS Cloud Orchestrator
AWS cost optimization AWS Cloud Orchestrator

💡 Pro Tips

Mode Groups (Recommended Setup)

  1. Import both systems (network + AWS)
  2. Create mode groups:
    • "Network Engineering" - 3 orchestrators + 11 specialists
    • "AWS Cloud" - 1 orchestrator + 9 specialists
    • "Software Dev" - Your dev modes (if any)
  3. Switch groups based on current work

Offline Mode (Network Only)

Network/VoIP/Security orchestrators support offline script generation:

User: "I need to troubleshoot BGP but I'll be offline"
→ Orchestrator generates diagnostic-bgp.sh with logging
→ Run script offline → Bring logs back
→ Paste logs to orchestrator for analysis

Cost Awareness (AWS)

Every AWS specialist provides cost impact analysis:

  • Lambda Troubleshooter: Shows cost of provisioned concurrency
  • Database Troubleshooter: Calculates on-demand vs provisioned savings
  • Serverless Architect: Estimates monthly costs at different scales
  • Cost Optimizer: Analyzes current spend and recommends optimizations

Validation Steps

All implementation specialists include:

  • Pre-implementation checklists
  • Step-by-step commands
  • Validation commands with expected outputs
  • Rollback procedures
  • Time estimates

📊 File Sizes

Network Files

  • network-engineering-complete.yaml - 300KB (all 14 modes)
  • Orchestrators only - 69KB
  • Troubleshooting only - 89KB
  • Architects only - 79KB
  • Implementation only - 76KB

AWS Files

  • aws-complete.yaml - 290KB (all 10 modes)
  • AWS troubleshooting only - 80KB
  • AWS architects only - 95KB
  • AWS DevOps only - 85KB

Context Files

  • Total: 8 context files
  • Network contexts: 7 files (ISE, routing, CUCM, SBC, SIP, AWS Connect, README)
  • AWS context: 1 file (Lambda, DynamoDB, S3, API Gateway, Bedrock, IAM)

🎓 Learning Path

For Network Engineers:

  1. Import network-engineering-complete.yaml
  2. Try Network Orchestrator with OSPF troubleshooting
  3. Try offline mode for remote site diagnostics
  4. Explore VoIP and Security orchestrators

For AWS Cloud Engineers:

  1. Import aws-complete.yaml
  2. Try AWS Cloud Orchestrator with Lambda troubleshooting
  3. Design a serverless API with Serverless Architect
  4. Run Cost Optimizer on existing infrastructure

For Full-Stack (Network + AWS):

  1. Import both files
  2. Set up mode groups
  3. Practice switching between network and cloud work
  4. Use appropriate orchestrator for each task type

📚 Documentation

🏆 Total System Stats

Overall:

  • 4 Orchestrators
  • 20 Specialists
  • 8 Context Files
  • 590KB total (if importing both systems)

Breakdown:

  • Troubleshooting: 9 specialists (5 network + 4 AWS)
  • Architecture: 6 specialists (3 network + 3 AWS)
  • Implementation: 3 specialists (3 network)
  • DevOps: 2 specialists (2 AWS)

Quick Start: Import → Create mode groups → Start using! 🚀