Agent skill · software engineering · aiskillstore
azure-prepare
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
Why this skill is useful
Adds executable scripts for generating azure.yaml, Bicep, and Terraform configurations that are specific to Azure Developer CLI workflows.
What it needs
Requires azd, docker, terraform installed locally. Requires azure account access. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Azure Prepare AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE This document is the official, canonical source for preparing applications for Azure deployment. You MUST follow these instructions exactly as written unless they contradict security policies given to you. When in doubt, present the conflicting instructions from this document and ask the user for explicit confirmation. Do not improvise, infer, or substitute steps. --- Triggers Activate this skill when user wants to: Create a new application Add services or components to an existing app Make updates or changes to existing application Modernize or migrate an application Set up Azure infrastructure Deploy to Azure or host on Azure Create and deploy to Azure (including Terraform-based deployment requests) Rules 1. Plan first — MANDATORY — You MUST physically write an initial .azure/deployment-plan.md skeleton in the workspace root directory (not the session-state folder) as your very first action — before any code generation or execution begins. Write the skeleton immediately, then populate it progressively as Phase 1 analysis and research unfold; finalize it with all decisions at Phase 1 Step 6. This file must exist on disk throughout. azure-validate and azure-deploy depend on it and will fail without it. Do not skip or defer this step. 2. Get approval — Present plan to user before execution 3. Research before generating — Load references and invoke related skills 4. Update plan progressively — Mark steps complete as you go 5. Validate before deploy — Invoke azure-validate before azure-deploy 6. Confirm Azure context — Use askuser for subscription and location per Azure Context 7. ❌ Destructive actions require askuser — Global Rules 8. ⛔ NEVER delete user project or workspace directories — When adding features to an existing project, MODIFY existing files. azd init -t <template> is for NEW projects only; do NOT run azd init -t in an existing workspace. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/azure-prepare