Azure-Samples

Use when starting or refining a project's requirements, before any planning or coding. Supports sub-commands `sync`, `reverse`, and `validate`.

Use when local verification passed and the feature is ready to ship to Azure.

Use when a plan exists and the application source or IaC needs to be created or updated.

Use when a spec exists and an implementation or Azure deployment plan is needed, before writing code.

Use when the user wants to run the full Specify → Plan → Implement → Deploy loop end-to-end in one shot. Accepts a free-form prompt that is passed to specify.

Use when implementation exists and needs to be exercised locally against provisioned Azure dependencies, before deploying.

Create Azure architecture diagrams, flowcharts, data-flow visualizations, or illustrations as Excalidraw documents with embedded official Azure service icons, and export them as SVG and PNG. Use whenever the user wants to draw, sketch, diagram, visualize, or illustrate an Azure workload, solution, reference architecture, network topology, AI/ML topology, or any cloud system involving Azure services — even if they don't say "Excalidraw". Triggers include: "diagram", "architecture diagram", "draw", "sketch", "visualize", "flowchart", "data flow", "topology", "illustrate" combined with any Azure / cloud context. Also use to re-render existing `.excalidraw` files to SVG/PNG.

Execute pending tasks from tasks.md / tasks.json, updating both on completion.

Read-only — assemble the wider runtime picture of a deployed voice app from azd deployment artifacts and Azure Monitor (Application Insights / Log Analytics) via Azure MCP or az CLI, then render it as KQL, call timelines, latency waterfalls, and mermaid diagrams

Service catalog and guided onboarding for the azd deployment. USE WHEN the user wants to discover, install, set up, or be walked through the deployable components (Azure OpenAI/AI Foundry, Speech, ACS/telephony, Cosmos DB, Redis, Container Apps, Key Vault, App Config, CardAPI MCP), asks "what gets deployed", "what services does this use", "help me onboard", "set up the deployment", "guide me through azd up", "which components do I need", or wants to enable optional pieces (phone number, EasyAuth, data seeding). Acts as the entry point an agent hooks into to assess current state, present the catalog, and onboard each component. DO NOT USE FOR: deep azd hook/flow internals or model-availability checks (use deployment-guide); runtime failure diagnosis (use troubleshoot); telemetry/log analysis (use observability-insights).

Agent-first, read-only diagnosis of the voice pipeline (deploy, telephony, STT, LLM, TTS, state) — gather evidence via Azure MCP / azd artifacts / CLI, probe the user for missing details, and recommend fixes without changing anything

Require relevant tests and documentation updates for any code or config change, and report what was run.

Create or update evaluation scenarios for the tests/evaluation framework, including session-based scenarios and A/B comparisons

Guide azd-based deployments, including where azure.yaml and azd hook scripts live, the current deployment flow, troubleshooting docs, and regional/model availability checks for Azure OpenAI

Add a new React component with Material UI

Add a new FastAPI endpoint to the API

Break down Azure Kubernetes Service spend by cluster, namespace, and utilization bucket. Identifies the most expensive clusters and namespaces, and how much spend sits in idle vs active workloads. WHEN: "AKS cost", "Kubernetes cost", "cluster cost", "namespace cost", "container cost", "break down AKS", "AKS utilization", "idle pods", "chargeback AKS". INVOKES: query_aks_costs, generate_query, validate_query, execute_query

Current spend vs limits, end-of-month forecast, and active alerts. WHEN: "budget status", "am I over budget", "budget health", "will I exceed budget", "budget forecast". INVOKES: list_budgets, forecast_costs, query_costs, list_alerts

Create a budget with sensible default thresholds, contact emails, and an optional action group. WHEN: "create budget", "setup budget", "need a budget", "no budgets", "budget recommendations". INVOKES: list_budgets, query_costs, forecast_costs, create_budget

RI/Savings Plan utilization, coverage of compute spend, new purchase recommendations, and an optional investigation when utilization drops. WHEN: "commitment benefits", "RI utilization", "savings plan utilization", "reservation coverage", "utilization dropped", "how much am I saving", "new RI recommendation". INVOKES: list_benefit_utilization, get_benefit_recommendations, query_costs, list_reservation_transactions, generate_query, validate_query, execute_query

Check Azure Policy SKU/region restrictions, tag compliance, and budget coverage via Azure Resource Graph. WHEN: "what SKUs are allowed", "can I deploy this", "check policy", "allowed VMs", "will this be denied", "tag compliance", "budget coverage", "governance health". INVOKES: generate_query, validate_query, execute_query, list_budgets

Explain a cost spike or unexpected charge: when it happened, which service drove it, what changed, and who owns the resources. WHEN: "why did cost go up", "cost spike", "unexpected charge", "explain increase", "bill higher than expected", "surprise cost". INVOKES: query_costs, generate_query, validate_query, execute_query

Surface right-sizing recommendations (Azure Advisor) filtered by SKU policy and flagged against existing commitments, plus quick-win cleanup candidates. WHEN: "optimize costs", "reduce spending", "right-size", "savings opportunities", "save money", "oversized", "wasted resources". INVOKES: query_costs, generate_query, validate_query, execute_query, get_benefit_recommendations, list_benefit_utilization

Look up Azure retail pricing for a service / SKU / region, compare options across regions or commitment types, estimate workload cost, and optionally retrieve negotiated prices via pricesheet download. WHEN: "how much will it cost", "estimate cost", "compare pricing", "cheapest option", "free tier", "price of", "compare regions", "DTU vs vCore", "negotiated prices", "pricesheet". INVOKES: get_retail_prices, list_dimensions, query_costs, start_pricesheet_download, get_pricesheet_status

Reviews Azure SDK .NET code samples for best practices, credential handling, error patterns, Aspire orchestration, and documentation compliance. Trigger: "review .NET Azure SDK sample", "check dotnet sample", "Azure SDK .NET review".

Reviews Azure SDK Go code samples for best practices, credential handling, idiomatic error handling, context propagation, and documentation compliance. Trigger: "review Go Azure SDK sample", "check Go sample", "Azure SDK Go review".

Reviews Azure SDK Java code samples for best practices, credential handling, error patterns, Spring Boot integration, and documentation compliance. Trigger: "review Java Azure SDK sample", "check Java sample", "Azure SDK Java review".

Reviews Azure SDK Python code samples for best practices, credential handling, async patterns, error handling, and documentation compliance. Trigger: "review Python Azure SDK sample", "check Python sample", "Azure SDK Python review".

Reviews Azure SDK Rust code samples for best practices, credential handling, ownership patterns, async runtime usage, error propagation, and documentation compliance. Trigger: "review Rust Azure SDK sample", "check Rust sample", "Azure SDK Rust review".

Reviews Azure SDK samples for best practices, credentials, errors, and docs. Auto-detects language.

Reviews Azure SDK TypeScript code samples for best practices, credential handling, error patterns, and documentation compliance. Trigger: "review TypeScript Azure SDK sample", "check TypeScript sample", "Azure SDK TypeScript review".

Migrate existing Azure Durable Functions apps from existing backend storage providers (Azure Storage, Netherite, MSSQL) to the Durable Task Scheduler. Use when switching backends, converting to azureManaged storage provider, upgrading from Azure Storage default provider, migrating from Netherite Event Hubs-based backend, migrating from Microsoft SQL Server backend, or modernizing Durable Functions infrastructure. Applies to .NET, Python, JavaScript/TypeScript, and Java Durable Functions apps that need to adopt the managed Durable Task Scheduler service.

Build durable, fault-tolerant workflows in Java using the Durable Task SDK with Azure Durable Task Scheduler. Use when creating orchestrations, activities, or implementing patterns like function chaining, fan-out/fan-in, human interaction, or monitoring. Applies to any Java application requiring durable execution, state persistence, or distributed transactions without Azure Functions dependency.

Build durable, fault-tolerant workflows in JavaScript/TypeScript using the Durable Task SDK with Azure Durable Task Scheduler. Use when creating orchestrations, activities, entities, or implementing patterns like function chaining, fan-out/fan-in, human interaction, or durable timers. Applies to any Node.js application requiring durable execution, state persistence, or distributed coordination without Azure Functions dependency.

Build durable, fault-tolerant workflows in Python using the Durable Task SDK with Azure Durable Task Scheduler. Use when creating orchestrations, activities, entities, or implementing patterns like function chaining, fan-out/fan-in, human interaction, or stateful agents. Applies to any Python application requiring durable execution, state persistence, or distributed transactions without Azure Functions dependency.

Build durable, fault-tolerant workflows using Azure Durable Functions with .NET isolated worker and Durable Task Scheduler backend. Use when creating serverless orchestrations, activities, entities, or implementing patterns like function chaining, fan-out/fan-in, async HTTP APIs, human interaction, monitoring, or stateful aggregators. Applies to Azure Functions apps requiring durable execution, state persistence, or distributed coordination with built-in HTTP management APIs and Azure integration.

Build durable, fault-tolerant workflows in .NET using the Durable Task SDK with Azure Durable Task Scheduler. Use when creating orchestrations, activities, entities, or implementing patterns like function chaining, fan-out/fan-in, human interaction, or stateful agents. Applies to any .NET application requiring durable execution, state persistence, or distributed transactions without Azure Functions dependency.

Guide for creating new AI Gateway labs. Use when users want to create a new lab in the labs/ folder. This skill provides the standard lab structure, templates, and patterns used across the AI Gateway repository including Jupyter notebooks, Bicep infrastructure templates, APIM policies, and README documentation.

Guide for creating Azure API Management (APIM) XML policies. Use when users want to create, modify, or understand APIM policies including inbound/outbound processing, authentication, rate limiting, caching, transformations, AI gateway policies, and policy expressions. This skill provides policy syntax, examples, and C# policy expressions for request/response manipulation.

Guide for building Bicep files for Azure API Management (APIM) and related Azure services. Use when users want to create, modify, or understand Bicep templates for APIM instances, APIs, backends, subscriptions, policies, products, loggers, diagnostics, and MCP servers. This skill provides Bicep syntax, patterns from Azure Verified Modules, and examples from this repository.

Guide for creating Kusto Query Language (KQL) queries for Azure API Management tables in Azure Monitor (Log Analytics Workspace). Use when users want to query, analyze, or monitor APIM logs including gateway logs, LLM/AI logs, MCP logs, WebSocket logs, and Application Insights data. This skill provides KQL syntax, table schemas, and query patterns for APIM monitoring scenarios.

Guide for creating Terraform files for Azure API Management (APIM) and related Azure services. Use when users want to create, modify, or understand Terraform configurations for APIM instances, APIs, backends, subscriptions, policies, products, loggers, diagnostics, and supporting infrastructure using the azurerm provider. This skill provides HCL syntax, resource definitions, and patterns from the Terraform Registry and this repository.

Reusable session pattern for modernized .NET apps that add observability, grounded search, reporting, MCP tools, and A2A agents.

Package an Aspire modernization session with docs, demo flow, and architecture notes

Keeps scenario README files and session docs aligned with the repo's documentation conventions.

Clone the closest existing eShopLite scenario baseline before adding a new modernization story.

{what this skill teaches agents}

Guide for building Bicep files for Azure API Management (APIM) and related Azure services. Use when users want to create, modify, or understand Bicep templates for APIM instances, APIs, backends, subscriptions, policies, products, loggers, and diagnostics. This skill provides Bicep syntax and patterns based on the shared modules in this repository.

Guide for creating Azure API Management (APIM) XML policies. Use when users want to create, modify, or understand APIM policies including inbound/outbound processing, authentication, rate limiting, caching, transformations, and policy expressions. This skill provides policy syntax, examples, and C# policy expressions for request/response manipulation.

Guide for creating or scaffolding Azure API Management (APIM) usage samples with the repository's notebook/helper architecture. Use when users want a new sample under `samples/`, a sample-local helper, `samples/_TEMPLATE` scaffolding, or synchronized README, website, slide deck, and compatibility listings.

Review code for best practices, potential bugs, and improvements. Use when asked to review, analyze, or critique code quality.

Analyze datasets and generate statistical summaries and insights. Use when asked to analyze data, compute statistics, or identify trends.

Summarize meeting transcripts into structured notes with action items. Use when asked to process, summarize, or extract action items from meetings.

Add styled banners to MkDocs documentation pages. Use when: adding a banner to a new camp page, adding a banner to a non-camp page like prerequisites or contributing, styling doc page headers with the deep teal gradient, creating consistent page headers across the workshop site.

Add OS-specific tabs to MkDocs documentation for Windows/PowerShell support. Use when: updating docs with Bash/PowerShell tabs, adding Windows instructions to workshop guides, converting documentation for cross-platform support, mkdocs content tabs for OS-specific commands.

Convert Bash (.sh) scripts to PowerShell (.ps1) for Windows support. Use when: adding Windows support to a camp, converting shell scripts to PowerShell, creating .ps1 equivalents, translating bash to pwsh, updating azure.yaml hooks for Windows.

End-to-end customer demo orchestration: CSV export from CRUD, blob upload, Event Hub triggered enrichment (UCP/ACP), AI Search vectorized indexing, and agentic semantic search — with streaming UI, live tracing, and independent step execution.

End-to-end manual validation of all 26 retail agents: infrastructure recovery, HTTP/EventHub/MCP connectivity, and graded prompt testing from none to high complexity — simulating real user behavior against deployed public endpoints.

Reusable issue engineering workflow for creating, correcting, improving, and defining new feature issues. Use for BPMN issue formatting, top-risk issue creation, and branch-per-issue PR execution by TechLeadOrchestrator and PlatformEngineer.

Proper flex truncation for title+badge rows in Tailwind CSS

Diagnose and fix React render loops caused by unstable effect or callback dependencies

How to extend the AI Policy Engine with new features without breaking existing behavior