infrastructure▌

Guidance and reference material for instrumenting webapps with Azure Application Insights. \n \n Covers SDK setup, telemetry patterns, and configuration for ASP.NET Core, Node.js, and Python applications hosted in Azure \n Distinguishes between this skill (reference and guidance) and azure-prepare (which orchestrates actual instrumentation changes) \n Recommends auto-instrumentation for C# ASP.NET Core apps on Azure App Service; provides manual instrumentation paths for other stacks \n Includes

Find minimal Azure RBAC roles, generate assignment commands, and provide Bicep infrastructure code. \n \n Identifies built-in roles matching desired permissions using Azure documentation, or generates custom role definitions when no built-in role fits \n Produces Azure CLI commands and Bicep code snippets for role assignments to identities, managed identities, and service principals \n Documents prerequisites for granting roles, including required permissions and recommended least-privilege role

Prepare Azure applications for deployment with infrastructure-as-code, configuration, and containerization. \n \n Generates Bicep or Terraform infrastructure code, azure.yaml configuration, and Dockerfiles based on application type and requirements \n Follows mandatory plan-first workflow: analyze workspace, gather requirements, select deployment recipe (AZD, AZCLI, Bicep, or Terraform), design architecture, and get user approval before code generation \n Supports creation, modernization, and up

Encore Go uses declarative infrastructure - you define resources as package-level variables and Encore handles provisioning:

Reduce infrastructure costs through intelligent resource allocation, reserved instances, spot instances, and continuous optimization without sacrificing performance.

Encore.ts uses declarative infrastructure - you define resources in code and Encore handles provisioning:

ln-743-test-infrastructure

Build scalable infrastructure as code with Terraform, managing AWS, Azure, GCP, and on-premise resources through declarative configuration, remote state, and automated provisioning.

Complete API specification for Agentica multi-agent coordination infrastructure.

Design and scale internal platforms by abstracting common capabilities and planning infrastructure before hitting limits. \n \n Focuses on understanding platform purpose, assessing organizational readiness, identifying leverage points, and designing for actual developer adoption rather than theoretical needs \n Emphasizes invisible infrastructure qualities like reliability, performance, and privacy as critical success factors alongside visible features \n Recommends proactive infrastructure scal