AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--azure-prepare at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 164

references/global-rules.md

Global Rules

MANDATORY — These rules apply to ALL skills. Violations are unacceptable.

Rule 1: Destructive Actions Require User Confirmation

⛔ ALWAYS use ask_user before ANY destructive action.

What is Destructive?

| Category | Examples | |----------|----------| | Delete | az group delete, azd down, rm -rf, delete resource | | Overwrite | Replace existing files, overwrite config, reset settings | | Irreversible | Purge Key Vault, delete storage account, drop database | | Cost Impact | Provision expensive resources, scale up significantly | | Security | Expose secrets, change access policies, modify RBAC |

How to Confirm

ask_user(
  question: "This will permanently delete resource group 'rg-myapp'. Continue?",
  choices: ["Yes, delete it", "No, cancel"]
)

No Exceptions

  • Do NOT assume user wants to delete/overwrite
  • Do NOT proceed based on "the user asked to deploy" (deploy ≠ delete old)
  • Do NOT batch destructive actions without individual confirmation
  • ⛔ Do NOT delete user project or workspace directories (e.g., rm -rf <project-dir>) even when adding features, converting, or migrating — use MODIFY mode to edit existing files instead. File deletions within a project (e.g., removing build artifacts or temp files) are permitted when appropriate.
  • ⛔ azd init -t <template> (and any azd init command with a template argument) is for NEW projects only — run it only in an empty/new directory. If the user explicitly requests re-initialization of an existing project, create a separate new directory, run the template there, and then migrate changes into the existing project with user-confirmed edits. Never run azd init -t directly in a non-empty existing workspace. azd init without a template argument may be used in existing workspaces when appropriate.

Rule 2: Never Assume Subscription or Location

⛔ ALWAYS use ask_user to confirm:

  • Azure subscription (show actual name and ID)
  • Azure region/location