RobertoBorges

Generate an executive-ready Migration Strategy Report (HTML deck) from a customer portfolio — CMDB exports, RVTools/Azure Migrate inventories, DMA outputs, vendor proposals, architecture diagrams. **Use when:** producing a CIO-ready migration plan for a customer portfolio (apps, databases, infra, or any mix). Starts the Portfolio Planning flow for multi-app engagements. **Triggers:** "generate migration report", "analyze CMDB", "portfolio analysis", "migration strategy report for X", "RVTools export analysis", "Azure Migrate analysis", "portfolio assessment", "build a deck from these artifacts". **Covers:** auto-detected workload pillars (Apps/DB/Infra), CAF-aligned 6 Rs classification, deterministic Factory / ISD-Partner / Unknown ownership, phased roadmap, dependency mapping, move groups, risks, executive HTML output.

Shifts model selection to cost-optimized alternatives when economy mode is active

Determines which LLM model to use for each agent spawn

Find and resume interrupted Copilot CLI sessions using session_store queries

Docker containerization patterns for .NET and Java applications targeting Azure. **Use when:** Creating Dockerfiles or deploying to Container Apps, App Service containers, or AKS. **Triggers on:** Container Apps or AKS selected as hosting platform, Docker-related requests. **Covers:** Multi-stage Dockerfiles, docker-compose, Container Apps configuration, health checks, resource limits.

Azure Infrastructure as Code patterns using Bicep and Terraform. **Use when:** Generating IaC for App Service, Container Apps, or AKS deployments. **Triggers on:** Phase 3 infrastructure generation, azd init, Bicep/Terraform file creation. **Covers:** Azure Verified Modules, managed identities, Key Vault with RBAC, Application Insights, networking.

Business logic discovery, mapping, and preservation during application migration. **Use when:** Migrating .NET or Java applications and need to ensure all business logic is preserved. **Triggers on:** Phase 2 code migration, business rule identification, logic preservation verification. **Covers:** Business rule extraction, logic mapping between source/target, validation tracking, media asset preservation. **Critical:** Ensures no business logic is lost during migration by creating traceable mappings.

Configuration file transformation patterns for .NET and Java modernization. **Use when:** Converting legacy config files to modern cloud-native formats. **Triggers on:** web.config, app.config, applicationContext.xml, persistence.xml files. **Covers:** web.config to appsettings.json, XML to YAML/properties, connection string externalization.

Docker containerization patterns for .NET and Java applications targeting Azure. **Use when:** Creating Dockerfiles or deploying to Container Apps, App Service containers, or AKS. **Triggers on:** Container Apps or AKS selected as hosting platform, Docker-related requests. **Covers:** Multi-stage Dockerfiles, docker-compose, Container Apps configuration, health checks, resource limits.

Azure Infrastructure as Code patterns using Bicep and Terraform. **Use when:** Generating IaC for App Service, Container Apps, or AKS deployments. **Triggers on:** Phase 3 infrastructure generation, azd init, Bicep/Terraform file creation. **Covers:** Azure Verified Modules, managed identities, Key Vault with RBAC, Application Insights, networking.

Business logic discovery, mapping, and preservation during application migration. **Use when:** Migrating .NET or Java applications and need to ensure all business logic is preserved. **Triggers on:** Phase 2 code migration, business rule identification, logic preservation verification. **Covers:** Business rule extraction, logic mapping between source/target, validation tracking, media asset preservation. **Critical:** Ensures no business logic is lost during migration by creating traceable mappings.

Configuration file transformation patterns for .NET and Java modernization. **Use when:** Converting legacy config files to modern cloud-native formats. **Triggers on:** web.config, app.config, applicationContext.xml, persistence.xml files. **Covers:** web.config to appsettings.json, XML to YAML/properties, connection string externalization.

.NET Framework to .NET 8+ modernization patterns. **Use when:** User has a .NET Framework 4.x application and needs to upgrade to .NET 8 LTS. **Triggers on:** .csproj files with TargetFrameworkVersion, web.config files, System.Web references, Entity Framework 6. **Covers:** Project file transformation, web.config to appsettings.json, EF6 to EF Core, Windows/Forms auth to Entra ID.

Unit testing patterns for validating migrated applications. **Use when:** Creating tests to verify migration correctness and prevent regressions. **Triggers on:** Test creation requests, validation phase, post-migration verification. **Covers:** xUnit/NUnit for .NET, JUnit 5 for Java, mocking strategies, test organization patterns.

WCF to REST API migration patterns for .NET modernization. **Use when:** Converting WCF services to ASP.NET Core REST APIs. **Triggers on:** .svc files, ServiceContract attributes, OperationContract, DataContract, WCF bindings. **Covers:** ServiceContract to controllers, DataContract to DTOs, FaultContract to Problem Details, OpenAPI generation. **Important:** This is a rewrite, not a compatibility layer. Existing WCF clients will need updates.

Docker containerization patterns for .NET and Java applications targeting Azure. **Use when:** Creating Dockerfiles or deploying to Container Apps, App Service containers, or AKS. **Triggers on:** Container Apps or AKS selected as hosting platform, Docker-related requests. **Covers:** Multi-stage Dockerfiles, docker-compose, Container Apps configuration, health checks, resource limits.

Business logic discovery, mapping, and preservation during application migration. **Use when:** Migrating any legacy application (any stack — .NET, Java, Python, Node.js, PHP, Ruby, Go, COBOL, Oracle Forms, etc.) and need to ensure all business logic is preserved. **Triggers on:** Phase 2 code migration, business rule identification, logic preservation verification. **Covers:** Business rule extraction, logic mapping between source/target, validation tracking, media asset preservation. **Critical:** Ensures no business logic is lost during migration by creating traceable mappings.

Generate an executive-ready Migration Strategy Report (HTML deck) from a customer portfolio — CMDB exports, RVTools/Azure Migrate inventories, DMA outputs, vendor proposals, architecture diagrams. **Use when:** producing a CIO-ready migration plan for a customer portfolio (apps, databases, infra, or any mix). Starts the Portfolio Planning flow for multi-app engagements. **Triggers:** "generate migration report", "analyze CMDB", "portfolio analysis", "migration strategy report for X", "RVTools export analysis", "Azure Migrate analysis", "portfolio assessment", "build a deck from these artifacts". **Covers:** auto-detected workload pillars (Apps/DB/Infra), CAF-aligned 6 Rs classification, deterministic Factory / ISD-Partner / Unknown ownership, phased roadmap, dependency mapping, move groups, risks, executive HTML output.

Unit testing patterns for validating migrated applications. **Use when:** Creating tests to verify migration correctness and prevent regressions. **Triggers on:** Test creation requests, validation phase, post-migration verification. **Covers:** xUnit/NUnit for .NET, JUnit 5 for Java, mocking strategies, test organization patterns.

Angular to React 18+ code mapping reference. Use when converting Angular code patterns to React equivalents including framework mapping, components, services, RxJS, routing, forms, and lifecycle methods.

Azure deployment best practices for React applications (Vite SPAs on Azure Static Web Apps, Next.js on App Service or Container Apps). Use when creating deployment configs, Dockerfiles, staticwebapp.config.json, or GitHub Actions workflows for a React app on Azure.

React 18+ project structure and scaffolding templates for migrated Angular applications. Use when creating new React projects (Vite or Next.js), setting up folder structure, or generating boilerplate for a TypeScript React SPA.

State management and data fetching patterns for React apps migrated from Angular. Use when converting Angular services with RxJS Observables to React hooks (TanStack Query, Context, Redux Toolkit) and axios-based API clients.

Docker containerization and Azure deployment best practices for .NET 10 applications. Use when creating Dockerfiles, docker-compose files, or configuring container deployments to Azure Container Apps, App Service, or AKS.

.NET 10 project structure and scaffolding templates for migrated PHP applications. Use when creating new .NET projects, setting up folder structure, or generating boilerplate code for ASP.NET Core MVC or Minimal APIs.

Entity Framework Core migration patterns for PHP Eloquent/Doctrine to EF Core. Use when converting Eloquent models to EF Core entities, migrating relationships, creating DbContext, or setting up EF Core migrations.

PHP to .NET 10 code mapping reference. Use when converting PHP code patterns to .NET equivalents including framework mapping, authentication, templates (Blade to Razor), packages (Composer to NuGet), and validation rules.