trainer-demo-deploy: Skill for Claude Code

Azure Deploy Skill

Deployment patterns and procedures for Azure infrastructure provisioned via Bicep templates and the Azure Developer CLI (azd). Covers the full deployment lifecycle: pre-flight checks, execution strategies, post-deployment validation, rollback, and cleanup.

[!CAUTION] MANDATORY DEPLOYMENT POLICY

1. Always attempt deployment: The Deploy agent MUST always attempt azd up. Tooling blockers (missing CLI, extension errors, auth issues) must be resolved or escalated to the user — never used as a reason to autonomously skip deployment.
2. User decides on failure: If deployment fails for any reason, present the full error to the user and ask for their decision. Never autonomously generate a "dry-run only" or "blocked" summary and move on.
3. Escalate, don’t absorb: If a pre-deployment gate fails and cannot be auto-fixed, ask the user. Do not silently document the failure and skip ahead.

---

1. Deployment Strategy Selection

Choose the deployment method based on available project artifacts:

Method	When to Use	Prerequisites
azd up (preferred)	azure.yaml exists in generated-scenarios/{project}/	Azure Developer CLI installed, az login completed

Decision Tree

azure.yaml exists?
├── YES → Use azd up
└── NO → Generate azure.yaml first, then use azd up

---

2. Azure Developer CLI (azd) Patterns

First-Time Setup

# Verify azd is installed
azd version

# Initialize environment (first time only)
cd generated-scenarios/{project}
azd init

# Set environment name
azd env new {project}-{env}
azd env set AZURE_LOCATION eastus2

azd up — Full Deployment

azd up provisions infrastructure AND deploys application code in one step: